Hi,
I am a new user of AnyLogic, and would appreciate some advice on modelling a simple system that has a small number of
states.
The model is of a very simplified disk controller, which has a queue of items to process (with a set time to process
each one). The system however can exist in a number of states - mainly sleep and active. The sleep state waits for the
queue to fill up to a certain threshold number, before kicking in to the active state and processing through them.
When the queue has lain idle for a set amount of time the system goes back to sleep. New items can arrive on the queue
at any time (indeed the arrival patterns is what I am seeking to experiment with).
Based on this simple model, do I need to build two separate Anylogic models - perhaps one simple Enterprise Library
model for the actual chain of consuming events, and a separate State Chart model to control the states? As you can see
the two are linked. Or is this all possible with a simple Enterprise Library model? Or am I even using the wrong
components, and should be looking at system dynamics modeling objects? I think I am right in using the discrete event
components here, but I'd appreciate some advice on what to use (I'm pretty sure I'm not after an Agent based
simulation).
Thanks for all your advice and help in getting me off the ground,
- Peter
Victor Gleim — 12.02.08
No, there is no need to create two models. AnyLogic allows to create very flexible models.
To simulate chain of events you could use the Enterprise Library with a simple flow-chart while control its state by
another flow-chart or using the Event and Statechart elements.