How do I summarize the time in a .log file?

[DannyJ]

Hello forum

2019-08-15 13:50:16 : Close
2019-08-15 13:50:33 : Open
2019-08-15 13:50:40 : Close
2019-08-15 13:51:00 : Open
2019-08-15 13:51:49 : Close
2019-08-15 13:51:52 : Open
2019-08-15 13:51:59 : Close
2019-08-15 13:52:20 : Open
2019-08-15 13:52:26 : Close
2019-08-15 13:52:30 : Open
2019-08-15 13:52:38 : Close

I have .log file see above. Made with _FileWriteLog function.

So my question is how that I want to summarize the overall usage of the program using this .log file.

#include <File.au3>

 Local $aRetArray, $sFilePath = @ScriptDir & "\Log.log"
    ; Re-read it - with count
    _FileReadToArray($sFilePath, $aRetArray)
    _ArrayDisplay($aRetArray, "1D array - count", Default, 😎
    

Dim s=0 
For $i = 0 To Ubound($aRetArray)

 s+=$Date

Next

 

[Xenobiologist]

Get the first and the last time and then use e.g. _DateDiff to get the seconds between those time.

You could use a _TimeDiff directly in your script.

Edited August 16, 2019 by Xenobiologist

[water]

Use _DateDiff to get the difference between two dates in seconds, sum them up then calculate the duration.

[water]

#include <File.au3>

Global $aLogArray, $sFilePath = @ScriptDir & "\Log.log", $iDuration = 0, $sOpenDate = ""
_FileReadToArray($sFilePath, $aLogArray, $FRTA_NOCOUNT)
For $i = 0 To UBound($aLogArray) - 1
    $aTemp = StringSplit($aLogArray[$i], " ", $STR_NOCOUNT)
    $aTemp[0] = StringReplace($aTemp[0], "-", "/")
    If $aTemp[3] = "Close" Then
        $iDuration = $iDuration + _DateDiff("s", $sOpenDate, $aTemp[0] & " " & $aTemp[1])
    Else
        $sOpenDate = $aTemp[0] & " " & $aTemp[1]
    EndIf
Next
MsgBox(0, "Runtime", "Run time in seconds: " & $iDuration)

I assume that there is always an Open/Close pair of records and there is only "Open" or "Close" in the log record.

Edited August 20, 2019 by water

[DannyJ]

Thank you very much your assistance 😀😍

[Skysnake]

What happens in the case of a malfunction and CLOSE is never written? And you have two consecutive OPEN entries?

 

[water]

To make it 100% fool-proof I would add a GUID to the OPEN and CLOSE token. So the script would be able to identify the correct pair.
I would then use a dictionary to store the OPEN/CLOSE information and the overall usage. On success I would remove the OPEN/CLOSE info from the dictionary.
At the end the problems you describe would be solved.

Example:

2019-08-15 13:50:33 : Open {0335E874-FBD1-4CBF-A354-8B9D536B40A7}
2019-08-15 13:51:16 : Close {0335E874-FBD1-4CBF-A354-8B9D536B40A7}

 

Instead of a GUID you could store the time including milliseconds. I would then add this exact start time to the CLOSE token. Rest as described above.

Example:

2019-08-15 13:49:38.102 : Open
2019-08-15 13:51:16.582 : Close 13:49:38.102

 

Edited August 20, 2019 by water