Basically there are three ways that could make sense.
Both would require a control action of "process queue" that pops the top event queue item and calls the appropriate wiring whether it be calling a ride or finishing a ride or something else. This block would be similar to a while loop so we need to figure out how execution ends.
One single call to the event queue processing function and having a preloaded list of X number of ride requests. Upon all requests being complete finish.
One single call to the event queue and a behavioral model of when requests happen and get added to the queue, would need something like a "finishing time" that says when to end the sim
Mock up days at a time and have N number of days and N calls to the event queue processing that takes care of all the rides in one given day. Could be either behavioral or loaded list of requests like one.
Basically there are three ways that could make sense.
Both would require a control action of "process queue" that pops the top event queue item and calls the appropriate wiring whether it be calling a ride or finishing a ride or something else. This block would be similar to a while loop so we need to figure out how execution ends.