Timers are failing

Hi everyone

I have this problem that my timers somehow seem to stop working over time.

I have this definition which is used to generate cities based on a variety of feedback loops, so it has to run for given set of hours. Sometimes the timer stops refreshing the definition after multiple hours of work, other times it is simply failing to work after I paused the timer for a bit just to check if everything was going according to plan.

could this be a bug? or is it something with the memory of my comp?

It should be said that when this happens, grasshopper also fails to promt a message when I hower my mouse over an output/input.

I hope that this is an easy fix, because it is really annoying to reset your work after 4-5 hours because the timers seem to get lazy...

Looking foreward to hear what the solution to the problem is.

Sincerely

Jens

Replies to This Discussion

Permalink Reply by David Rutten on September 16, 2011 at 1:03am

Hi Jens,

I suppose the way timers work is fairly susceptible to failure. After every solution, they 'schedule' another solution N milliseconds in the future. Then, when the next solution happens, they check to see if it might be due to them and, if it is, they expire their targets. If the solution happened too quickly, they schedule another solution N-t milliseconds in the future (where t is the time between the previous schedule and the current solution).

From this it follows that if a timer manages to screw up even once, it will then stop running since the chain of schedules and solutions is broken.

It could well be due to a bug in the scheduling logic. I did change the way timers behave in the latest version. I'll have a look at the code, see if I can find anything spurious.

David Rutten

david@mcneel.com

Barcelona, Spain

RSS