BT 0.87

[Pepo]

Interestingly a Collatz task (around 1d2h) and PrimeGrid task (3 1/2 days) are everywhere displayed correctly, also in Properties.

OK, to be even more fair to the CPDN task, I can now see also the PrimeGrid task waiting with highlighted [0] 03d,16:30:02 in Checkpoint column, following (apparently correct?) could be seen in the Properties:

Code Select Expand

CPU time at last checkpoint 03d,16:30:02
CPU time 03d,13:06:42
Elapsed time 03d,18:24:29
Estimated time remaining 01d,18:55:47
Fraction done 75.260 %

No idea what the cause could be.

But as you can see the CPU time at last checkpoint is higher than the CPU time.
This should be impossible, as the checkpoint is always in the past. The value should be the last check point CPU time, this can never be more than the CPU time.
The value shown in this case is the Checkpoint time.

I've noticed it. So, to to compare apples to apples, I've switched to hhh:mm:ss notation and here are the task's Properties from BT:

Code Select Expand

CPU time at last checkpoint 88:30:02
CPU time 85:06:42 <=-
Elapsed time 90:24:29 <=-
Estimated time remaining 42:55:47
Fraction done 75.260 %

and from BM:

Code Select Expand

CPU time for last checkpoint 88:30:02
CPU time 88:42:43
Elapsed time 94:03:36
Estimated time remaining 42:55:47
Fraction done 75.260 %


Immediately after forcing the task to run and 5-6 seconds later on next display refresh, BT's Elapsed time column value will immediately change from "90:24:29 (85:06:42)" to "94:03:42 (88:42:48)" and Checkpoint column to "[0] 00:12:45".

Therefore I believe that something in BT's internals gets vice-versa when displaying the elapsed+cpu times and thus also the checkpoint difference gets wrong.

[fred]

Immediately after forcing the task to run and 5-6 seconds later on next display refresh, BT's Elapsed time column value will immediately change from "90:24:29 (85:06:42)" to "94:03:42 (88:42:48)" and Checkpoint column to "[0] 00:12:45".

Therefore I believe that something in BT's internals gets vice-versa when displaying the elapsed+cpu times and thus also the checkpoint difference gets wrong.

I found one problem, the time in task properties wasn't always correct, sometimes it was way to high.
The value for the warning calculations was correct.

And I found another one, when not running, the elapsed time may be incorrect. And the checkpoint may be incorrect as well.

[Corsair]

No dump file at all?

Nope, nothing at all, crash folder empty.

[Beyond]

The xml values will override the default settings.
The xml is read sequentially, so the LAST command in the list that matches will be the one used.

So don't place global expressions at the end, but at the beginning. See example: http://www.efmer.eu/forum_tt/index.php?topic=503.0

By golly it worked.  Thanks!