Well, if you have the time, maybe you could help me unravel the 'puzzle' that in a way created some mess in my experimental results. Though I've managed to use another method to bypass this puzzling scenario, I'm still pondering over how this could occur.
Suppose you know a starting date for an event, the duration of the event, the time now (i.e. current time) and you wanted to find the remaining time for the event... I generated some messages during the execution of the codes and this is an extracted part which is puzzling...
Starting Date: S = 1/2/2006 7:24:12 AM
Time Now: T = 1/2/2006 8:20:30 AM
Duration: 66.10 mins = 66.10/(24.0*60.0) days
Remaining Time: 9.78 mins
The puzzle is: How do you get 9.78 mins?
------------
If you use Excel and plug in the formula:
remaining time = (Starting Date + Duration (in days) - Time Now) * 24.0 * 60.0 [mins]
You should get approx. 9.8 mins
However, ASAP gives me 9.78 mins instead. It may seem like a very small difference (oh, what's the big deal?), but it created a hell of a problem and messed up my results. TMD.
[I suspect truncation errors... but then, how to chk?]
Everyone is familiar with ASAP... but what about ASAP^2?
ASAP^2 = 'settle' AutoSched AP (ASAP) * As Soon As Possible (ASAP)...
Both ASAP are equally sickening...