You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently updated dependencies for the first time in a while, and I am surprised to find that the solutions for pure jump process problems with all-Int64 initial states now contain Float64 elements.
using Catalyst
using JumpProcesses
model =@reaction_networkbegin
kB, S + E --> SE
kD, SE --> S + E
kP, SE --> P + E
end
tspan = (0., 200.)
ps = [:kB=>0.01, :kD=>0.1, :kP=>0.1]
u0_integers = [:S=>50, :E=>10, :SE=>0, :P=>0]
jinput =JumpInputs(model, u0_integers, tspan, ps)
jprob =JumpProblem(jinput)
jump_sol =solve(jprob)
I am unsure if this is a Catalyst, JumpProcesses or other issue, or if this is even desired behavior now and I need to reconfigure something to change it back. I haven't really found anything about this change in the documentations, issues or changelogs of Catalyst or JumpProcesses, or on Discourse. What am I missing?
Environment
Output of using Pkg; Pkg.status()
Status `/tmp/jl_jo6gO2/Project.toml`
[479239e8] Catalyst v14.4.1
[ccbc3e58] JumpProcesses v9.14.2
Output of using Pkg; Pkg.status(; mode = PKGMODE_MANIFEST)
Julia Version 1.11.3
Commit d63adeda50 (2025-01-21 19:42 UTC)
Build Info:
Note: This is an unofficial build, please report bugs to the project
responsible for this build and not to the Julia project unless you can
reproduce the issue using official builds available at https://julialang.org/downloads
Platform Info:
OS: Linux (x86_64-pc-linux-gnu)
CPU: 8 × Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
WORD_SIZE: 64
LLVM: libLLVM-16.0.6 (ORCJIT, icelake-client)
Threads: 1 default, 0 interactive, 1 GC (on 8 virtual cores)
The text was updated successfully, but these errors were encountered:
My guess (emphasis on guess) is that this is due to some ModelingToolkit update. I think there was a discussion about variable types a bit back and they could have funny types, which shouldn't be the case. A possibility is that ModelingToolkit (which Catalyst utilises) did something to enforce Float64 (which makes sense for e.g. ODEs). However, I know we pointed out at the time that this would not make sense for Jump simulations, which makes me think that it might be something else. However, when I get the chance, I will try this examples on various ModelingToolkit versions and see what happens (feel free to do so as well!).
(Catalyst v14.4.1, JumpProcesses v9.14.2)
I recently updated dependencies for the first time in a while, and I am surprised to find that the solutions for pure jump process problems with all-
Int64
initial states now containFloat64
elements.For example, running the first jump process example in the documentation
we get:
I am unsure if this is a Catalyst, JumpProcesses or other issue, or if this is even desired behavior now and I need to reconfigure something to change it back. I haven't really found anything about this change in the documentations, issues or changelogs of Catalyst or JumpProcesses, or on Discourse. What am I missing?
Environment
using Pkg; Pkg.status()
using Pkg; Pkg.status(; mode = PKGMODE_MANIFEST)
versioninfo()
The text was updated successfully, but these errors were encountered: