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

Termination Signal #5

Open
matt4530 opened this issue Nov 20, 2021 · 1 comment
Open

Termination Signal #5

matt4530 opened this issue Nov 20, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@matt4530
Copy link
Member

Currently, simulation.run(..) runs until the events created by it, and only it, have all been responded to, success or failed.

In some circumstances, we want the simulation to run until a signal is received. For example, it is possible that an event may have created child events and the parent event completes before child events do. In such a case, the simulation needs to run for longer. In other cases, we want to terminate the simulation before all events have received a response.

A signal might be:

  • A time
  • A completion of all child events
  • A particular stage has reached a certain number of calls to workOn
@matt4530 matt4530 added the enhancement New feature or request label Nov 20, 2021
@matt4530 matt4530 added this to the v1.1.5 milestone Dec 14, 2021
@bjfoutz00
Copy link
Contributor

Use cases

  • Run for a number of events

  • Run for a length of time

  • Run until application stalls

  • Run until signal: subcases? a certain method has been called x times

  • Maybe even use signals for all cases.
    Run in a loop until certain criteria has been met

@matt4530 matt4530 removed this from the v1.1.5 milestone Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants