Measure command time

[BlackJack]

Some of my macros are including some text reading and editing functions.
I want measure the time, a command needs to finish. The most obvious method would be to use the date tokens.
But I don't know how to calculate the time difference between date tokens and get a 'human readable' result like 0.5 sec .

Has someone experiences with such things? Thanks in advance.

[Pfeil]

Try this:

Code: [Select]

Set date [StopWatch] value to the current date/time
Set decimal [StopWatchEnd] value to the converted value of {EXP:({DATETICKS} - {DATETICKS:StopWatch}) / 10000000} (round to 2 decimal places)
Write '[Purple] StopWatch: {DEC:StopWatchEnd} Seconds' to log

I can't test it because of a bug(the report of which has apparently vanished), but it should work on most locales.

You could set a text value, rather than a decimal, but then it'll give you results like "StopWatch: 0,1600002 Seconds", as it won't be rounded down.


You don't have to use a date value if you don't have to modify the start time, so you could use:

Code: [Select]

Set decimal [StopWatch] value to the converted value of {DATETICKS}
Set decimal [StopWatch] value to the converted value of {EXP:({DATETICKS} - {DEC:StopWatch}) / 10000000} (round to 2 decimal places)
Write '[Purple] StopWatch: {DEC:StopWatch} Seconds' to log


[BlackJack]

Thanks Pfeil.

I'll try both and see what's better, when I'm at home again...

[Gary]

I can't test it because of a bug(the report of which has apparently vanished), but it should work on most locales.

http://voiceattack.com/SMF/index.php?topic=202.0

[Pfeil]

I can't test it because of a bug(the report of which has apparently vanished), but it should work on most locales.

http://voiceattack.com/SMF/index.php?topic=202.0

An Error Has Occurred!
The topic or board you are looking for appears to be either missing or off limits to you.

I knew I wasn't crazy! Well, just a little.

[Gary]

DOH!  I need to fix that.  It's in there, though

[BlackJack]

I can't test it because of a bug(the report of which has apparently vanished), but it should work on most locales.

I'm also affected by this (very old  ) bug. I can't round the value. But it was still very helpful. Thanks

[Pfeil]

I'm also affected by this (very old  ) bug. I can't round the value.

Aha. "Good" to know I'm not alone in this, in a weird way.

I do remember having a workaround:

Code: [Select]

Set date [StopWatch] value to the current date/time
Set decimal [StopWatchEnd] value to the converted value of {EXP:{DATETICKS} - {DATETICKS:StopWatch}}
Set decimal [StopWatchEnd] to [StopWatchEnd] divided by 10000000 (round to 2 decimal places)
Write '[Purple] StopWatch: {DEC:StopWatchEnd} Seconds' to log
As long as the input is an integer(which it will be in this case, as both tick values are), the conversion works fine, so you do the division after the fact.

Even if your input was non-integer, you could use

Code: [Select]

Set decimal [StopWatchEnd] value to the converted value of {EXP:(5 / 2) * 10000}
Set decimal [StopWatchEnd] to [StopWatchEnd] divided by 10000To shift the decimal point to make it integer, and then undo the shift once the value is set.

[BlackJack]

Thanks for all the options, that you have figured out.
I like it simple and clean. So, this is my favorite:

Code: [Select]

Set date [StopWatch] value to the current date/time
Write '[Purple] {EXP:({DATETICKS} - {DATETICKS:StopWatch}) / 10000000} sec' to log
I wasn't aware, that I only have to divide the Dateticks by 10000000 to get the value in seconds.

What I have found, is that VA [1.5.12] is getting incredibly slow after a reboot.
A special command needs more than a second (1.3) to finish. Everything feels very laggy overall.
What helps, is to reinstall VA and the same command needs only 0.2 seconds and VA feels much more responsive again.

Aha. "Good" to know I'm not alone in this, in a weird way.

Everyone, that uses a comma as decimal separator, should be affected.
But it seems, that the decimal tokens are not used very often.

[Gary]

What I have found, is that VA [1.5.12] is getting incredibly slow after a reboot.
A special command needs more than a second (1.3) to finish. Everything feels very laggy overall.
What helps, is to reinstall VA and the same command needs only 0.2 seconds and VA feels much more responsive again.

So, same VoiceAttack.dat and same user.config settings but a, 'fresh' .exe solved the speed problem?  If that's the case, something happened to your .exe as .exe's usually don't go stale as far as I can recall o_O

[BlackJack]

I'm not sure, if the VA.exe is the reason, but that's what I could observe...
And it is reproducible. The strange thing is, after a period of time the issue is gone by itself.
But reinstall VA helps immediately. I can install an earlier iteration and see if happens the same..