-
-
Notifications
You must be signed in to change notification settings - Fork 224
add ismassaction and get rid of some temp arrays #369
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
Conversation
@ChrisRackauckas I think with this we are done with |
but let me know if you see anything we've missed. |
Looks good. Could a follow up PR flesh out the docs for JumpSystem and ReactionSystem? We need to think about how we want to do the conversions there to regular jump problems. I think |
Yup, doc updates are on the TODO list next over here. I didn't want to advertise all this stuff till we had it working / somewhat finalized, but we are there now. Hybrid systems will need a bit of thought, but I can go ahead with the basic RegularJumpSystem to start at least. If we later allow RegularJumpSystems to be hybrids instead of making a separate HybridJumpSystem we can update over here as necessary. |
Should hybrid be working at the DiffEqJump / StochasticDiffEq level already? |
Yes, you just can't mix that hybrid with actual SDEs/ODEs yet, which is my next goal.
It would be good to keep hybrid separate for SimpleTauLeaping. One thing that would be interesting too would be a static splitting, but it might be difficult to choose which jumps go where. Then dynamic would be a bigger goal down the line, which is possible by making every jump part of both and adding parameters, but we'd need solvers to "know about it" in a sensible way. |
https://travis-ci.org/github/SciML/ModelingToolkit.jl/builds/688124601#L570 That tolerance should be made higher since it seems reliant on compiler optimization levels. |
I'm away from my computer the next few hours, but will bump that up (and double check the generated code) later tonight. |
Good stuff. |
@TorkelE Mind taking a look that this looks ok to you?
ismassaction
is so useful I've found that I wanted a separate routine for it; we can drop it from DEBio now. This also re-arranges a bit so that the ratelaw calculation is only called for non-mass action jumps. On a big system that should help system construction time.