Sam Isaacson

Ahh yes, I always mix it up with the jump rate definition. I guess I was actually thinking of the latter (which is of the form `rate(u,p,t)`, i.e. doesn't take...

@ChrisRackauckas what do you think about using `SciMLBase.numargs` to add support for single argument `rate(integrator)` functions? (Basically, we create a wrapper if passed a `rate(u,p,t)` function which forwards the appropriate...

Ahh, I see that this won't work for variable rates since they have to support being called without integrators via the ODE derivative interface: https://github.com/SciML/JumpProcesses.jl/blob/fd47a8212711c85687e93b8bc9e90e82fb134d36/src/problem.jl#L272 That's unfortunate as this seemed...

What are the parameters you are choosing and number of simulations you are averaging over? For a birth dominated system this model will grow exponentially so I'd expect it to...

You can see what is going on here: https://github.com/SciML/JumpProcesses.jl/blob/c8ec2ba109a85db569540d050486e18035f0f334/src/problem.jl#L265 The ODE state variables are internally augmented with the integrated intensities, and the ODE derivative function is augmented to return the...

Closed by https://github.com/SciML/JumpProcesses.jl/issues/320

We are tracking this in https://github.com/SciML/Catalyst.jl/issues/952 now so I'm going to close (but unfortunately it still isn't fixed).

Thanks. We can add these with Catalyst 14, unfortunately merging now would lead to broken dev docs so this has to wait till that is merged to master.

Will `depwarn = true` cause tests to fail here even if the warnings are only coming from code called within a library we depend on? (i.e. we aren't directly calling...

@thazhemadam we've updated everything but docs and CI -- we are now frequently getting test failures due to codecov token limits. Is that fixed in the SciML wide versions of...