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
{{ message }}
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.
Currently, stay allows a model to stay dormant for a while. The new code (issue #33) will integrate this functionality with an implementation that supports virtual time. This allows us to skip ahead to the next event, instead of waiting with Thread.sleep.
If we use this in a simulated environment, the environment also needs to be able to skip time. We therefore need to provide a custom sleep function in the model.
If virtual time is used, Model.sleep internally calls advance on the virtual timer instead of sleeping.
Later on, we can also support real time, where all calls to advance are replaced with Thread.sleep.
The text was updated successfully, but these errors were encountered:
Currently,
stay
allows a model to stay dormant for a while. The new code (issue #33) will integrate this functionality with an implementation that supports virtual time. This allows us to skip ahead to the next event, instead of waiting withThread.sleep
.If we use this in a simulated environment, the environment also needs to be able to skip time. We therefore need to provide a custom
sleep
function in the model.If virtual time is used,
Model.sleep
internally callsadvance
on the virtual timer instead of sleeping.Later on, we can also support real time, where all calls to
advance
are replaced withThread.sleep
.The text was updated successfully, but these errors were encountered: