Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out Block Execution #54

Open
SeanMcOwen opened this issue Jul 4, 2024 · 0 comments
Open

Figure out Block Execution #54

SeanMcOwen opened this issue Jul 4, 2024 · 0 comments

Comments

@SeanMcOwen
Copy link
Collaborator

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.

  1. 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.
  2. 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
  3. 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant