Search the Community
Showing results for 'create a timer element'.
-
Entities in a buffer at the start of the simulation
gocken replied to Ondrej's topic in SI General Discussions
Try the logic included in this model. Note that you can use the same logic at any time over the simulation run. In this specific example the entities are created at the begining of the simulation run. If you need to create them at any time over the simulation run then you should define a seperate process then embed the same logic into that process. Then, all you need is to trigger that seperate process. For example, you can trigger by using timer element. Hope it helps?. CreateEntities.spfx -
I believe you can't create of vector of elements. Although, you can create a element reference state vector, which might be helpful. Your best bet would probably be modelling your process logic to trigger events through the Fire step, instead of using a timer. Or maybe adding a timer inside a object model, so every instance of that object has its own timer.
-
Run Length Reference Property Experiments
GFurtado replied to jrobinson's topic in SI General Discussions
Let me see if I understood correctly. You want something like this? Create a Timer Element and set its Time Offset to a referenced property: Then create a process that ends the run (through the EndRun step) when the timer triggers: -
As you have discovered (and I discussed in my post above), running an experiment puts Simio in its fastest run mode possible. And in this mode it will automatically distribute the replications and scenarios across all of your processors/cores. This alone can provide dramatic speedups. If you have Team Edition, you can actually extend that to use spare processing power in your work group. So if you have 4 quad-processor machines available on your local network, you can run up to 16 simultaneous replications or scenarios. In terms of modeling, the most dramatic improvement you could make is to build your model at a lower level. The model you described is simple to model entirely in a single process with steps: (begin) - Seize - Delay - Release - Tally - (end) with the process triggered by a Timer element and using TallyStatistics elements for any token-related statistics like Time In System. You would not even need to create any entities, it could all be done using tokens which are smaller and faster. The process approach should be many times faster.