Timer
|
|
The timer synchronizes actions to the system clock, correct?
For: M EndTime = 60.0 M TimeStep = 1.0 Timer Interval (milliseconds) = 1000 Timer Action = Step = 1 the simulation should last 60 real seconds, one TimeStep per second, correct? (That is the result I get.) However, changing the Interval in milliseconds does not appear to change the real time the simulation takes. I would expect: M EndTime = 60.0 M TimeStep = 1.0 Timer Interval (milliseconds) = 500 Timer Action = Step = 1 to cause the 60 TimeSteps to occur in 30 real seconds (or two TimeSteps per real second). The result however is the same - it takes 60 real seconds for the simulation to run. I searched documentation and Support messages without finding anything that addresses this. Bill Follow-on: For: M EndTime = 60.0 M TimeStep = 1.0 Timer Interval (milliseconds) = 5000 Timer Action = Step = 1 the simulation advances 1 TimeStep for every five real seconds, as expected. It seems to be values under 1000 that do not have the effect of more than one TimeStep per real second, proportional to 1000/X, where X is the Interval in milliseconds. See /bbsim/fire/. |
|
|
Hi Bill,
The timer will not start the next tick until the actions for the previous tick have been completed. This means you are then limited by both the interval and how long it takes to perform the actions you have added to the timer. Billy |
|
|
Just to confirm I get it...
If the [real] time required for the simulation to move 1 TimeStep is greater than the number of milliseconds allotted in the Timer Interval property, the simulation time requirement prevails. So I had set the Interval milliseconds to 500, the same as one-half second. If the simulation itself takes three-quarters of a second for one TimeStep to process, there is no way two TimeSteps will fit into a real second. |
|
|
Hi Bill
That is correct. Billy |
Please log in to reply to topics.