-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
New events + callbacks doc page #891
base: master
Are you sure you want to change the base?
Conversation
|
||
Since continuous events (and callbacks) actively find the exact time point when they are triggered, supplying `tstops` is not required for these. | ||
|
||
## [Programmatic creation of models containing events](@ref events_programmatic) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now, I start with going through how events work with the DSL. Then, at the end I have a separate section describing the details one needs to change when using a programmatic workflow (here and most other cases it is straightforward, except for the base syntax the two approaches are really similar).
nothing # hide | ||
``` | ||
|
||
### [Callbacks during jump simulations](@id events_additional_considerations_jump_parameters) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is handled properly for events, right? Not that the user can do anything if it isn't, but still.
New doc page for events and callbacks. Goes through the various types, and how to declare and use them. Also describes some common pitfuls one can encounter while working with these.