Sam Isaacson

And the DiffEqCallbacks needs updates.

Fixing this is a bit more complicated as it seems DiffEqCallbacks currently relies on `tstops` being a specific binary heap implementation (which we don't use in JumpProcesses): https://github.com/SciML/DiffEqCallbacks.jl/blob/1a02294bff7debdf8ecdca62b6a4cbfd52c10903/src/iterative_and_periodic.jl#L47 So it...

In fact, both OrdinaryDiffEq and DiffEqCallbacks seems to rely on that internal field from DataStructures.jl's heap implementation, which seems like a not so great idea in general.

This looks like a very nice project! We're actually switching DiffEqBiological over to sit on top of ModelingToolkit currently, and as part of that we've added a `ReactionSystem` component, [here](https://github.com/SciML/ModelingToolkit.jl/blob/master/src/systems/reaction/reactionsystem.jl),...

Do you mean something like ```julia @variables x[1:10] ``` This now works in MT and you can access the variables by index, e.q. `x[2]`.

Note that with MTK9, and hence Catalyst 14, using named mappings is a requirement as under the hood parameter and species orders can now change.

And a different parameter object is now generated for use in solvers: https://docs.sciml.ai/ModelingToolkit/stable/basics/FAQ/#Why-are-my-parameters-some-obscure-object? (wrong link initially)

@ChrisRackauckas how should we set them up here to work with SciML.ai?

Given that a column width is being enforced, it shouldn’t be hard to see the closing parenthesis if it is on the same line as arguments. There is something to...

It also (to my eyes), breaks the convention that the indentation can be quickly scanned to see where a function ends. Now one has to actively ignore parentheses that arise...