Time as a variable is odd

[philmorgan0382]

hi all, i hope someone will know this...

When using a "once per day" block. i learned you can set a double or int constant which is great. However...

Because the range of optimization is decimal, tests are performed at some silly times like 10.82 for example. So instead of testing the 1440 minutes of real day, we have to test 2400 (from 0000 to 2399)

This is fine in some circumstances since the result for 11.75 is the same as 12.15 (once we pass xx.59 the hour increases and the remaining 15 is added i suppose. But here is the odd thing...

A time input such as 11.20 will actually happen at 11.02 in realtime.
if we put 11.22 this will happen at 11.22 as expected.

any time before 10.00 is very strangely dealt with too..

01.01 to 01.99 all happen at 01.00 in realtime.

please can someone explain how to express a time like 01.20 in this strange decimal format? i want to optimize all 1440 unique and real minutes of each day.

many thanks in advance.

[l'andorrà]

@philmorgan0382 Can you please share the link to the project? Maybe we can find a specific solution depending on what you need.