-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
Event trigger directionality #1715
Comments
|
@paulflang I can add that for you, but might not be till later in the week. |
@isaacsas : that would be great. But not urgent rn. |
I'm trying to finish off getting normal events into SDEs and jump processes first: #1714 |
Hi, is there any progress or a workaround for this issue yet? |
I have the same need for a directional callback. Currently using |
We were discussing this more recently in SciML/SBMLToolkit.jl#101. I close it there, let's continue discussing here. |
yes |
I am trying to introduce directionality in an event trigger (i.e. only fire as either up or downpass). IIUC this correctly it should be possible in principle with
affect_neg!=nothing
in the ContinuousVectorCallback .But in MTK, I am using a
Pair{Vector{Equation}, Vector{Equation}}[]
that is passed tocontinuous_events
in the ODESystem constructor. Is there a good way to introduce directionality in a trigger using the ODESystem constructor/continuous_events keyword? My current code is here. Perhaps rather than using~
in the trigger equation<
or>
could be used?The text was updated successfully, but these errors were encountered: