You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is required functionality for things like Stock Flow diagrams and Petri Nets with Rates to be used. It is the common language those user-friendly presentations get compiled down to. One plan for this is written here
It remains to be decided how the clock gets advanced.
If one draws that the next event is very far in the future, one may wish to integrate the ODE a bit and then resample all of the clocks that got affected by changed parameters.
The text was updated successfully, but these errors were encountered:
And to, for the near future, not support the combination of these.
The second kind of timer can be scheduled. We do not need to worry about how the world changing (while jumping to the next-to-fire event) affects the validity of that event happening then.
The first kind of timer must be continuously (i.e. for each small $\Delta t$) evaluated. But because it is memoryless this is simple: at each $\Delta t$, we check whether or not the event fires within the next $\Delta t$ given the current value of its constant hazard rate.
This suggests an implementation: we continue to schedule events and jump to the next-to-fire event. However, 'jumping' now involves the following procedure: we simulate the ODE (using some off-the-shelf ODE solver) and periodically (at some $\Delta t$) pause the simulation, check whether any of our stateful+memoryless rules will fire within the next $\Delta t$. Whenever that happens, the rewrite is fired, which can change the ODEs (via the method described in the blog post) as well as the scheduled events. We do this procedure up until the next scheduled event.
Here's the paper I mentioned on the call where I saw the method that augments the ODE system with an additional variable, and just integrates out to a unit exponentially distributed amount of time and checks what happens at that point in time https://arxiv.org/abs/1504.06873 May or may not be useful here
This is required functionality for things like Stock Flow diagrams and Petri Nets with Rates to be used. It is the common language those user-friendly presentations get compiled down to. One plan for this is written here
It remains to be decided how the clock gets advanced.
If one draws that the next event is very far in the future, one may wish to integrate the ODE a bit and then resample all of the clocks that got affected by changed parameters.
The text was updated successfully, but these errors were encountered: