Sam Isaacson

Sorry, I meant does the event code need to be updated to work with constants similar to the updates you made across the various system types?

Would this change mean that parameter tuples mixing floats and parameters get promoted to all `Float64` internally? That would be undesirable, and I think potentially break, some Catalyst models.

Or is the idea to convert mixed-type parameter vector/tuples into a tuple with the mixed types separated into vector components?

Would this just be applied to parameter vectors, or to mixed-type parameter tuples too?

You are right, this is a classic case of my typing `]up ModelingToolkit` earlier today and then not catching that it left me at 6.4.8... So it does indeed work...

ModelingToolkit currently can't auto detect parameters and variables that appear in events (unlike for the system's equations). Have you tried using the four-argument version of `ODESystem` where you pass the...

`structural_simplify` does not check if a variable is used in an event currently, so you either need to avoid it, or tag the variables to not be removed. I've never...

I haven't used them, but I believe periodic and preset time events require numerical values for the times and don't work with symbolic values. If you want symbolic values you...

Glad you got it working! There is definitely some work we need to do to cleanup the interaction between events and `structural_simplify`, and to make it easier to specify time-based...

You should always pass initial conditions and parameter values via mappings (as you do in the last example), or by specifying default values when you create the symbolic variable. You...