Torkel Loman

Can this be considered solved by https://github.com/augustinas1/MomentClosure.jl? Possibly we could add a tutorial in Catalyst as well.

Got it, sounds good. We can keep this open until we've figured it out.

This is both really cool, I didn't know things were so far progressed! I think both your first example, and something like in the second (which I understand, if `trajectories=1`...

So, if I change ```julia if isempty(sivs) && (checks == true || (checks & MT.CheckUnits) > 0) nonrx_eqs = Equation[eq for eq in eqs if eq isa Equation] MT.all_dimensionless([states; ps;...

I have now replace ```julia ModelingToolkit.all_dimensionless(vars) ``` with ```julia all(u == 1.0 for u in ModelingToolkit.get_unit(vars)) ``` If this seems equivalent (which I think it is), I am happy to...

Yes, having these things be parameters (and not values) is useful because it means that they can be changed. However, since they are not added to the system, this is...

Sounds good. There are quite a few situations where one uses this outside of `@mtkmodel`. Especially if you have a lot statements like this, things become unreadable without `begin ......

Here, if you provide an initial guess for `X` (the variable that only appears in the algebraic equation) when attempting to solve the 2nd-order DAE, you get an error. However,...

Right, that makes sense. But why do I then not get the same problem for the first case? I.e. ```julia u0_1st_order_1 = [X => 1.0, Y => 2.0] oprob_1st_order_1 =...

The problem is that that function takes input in the form of `MTKParameters`. I.e. ```julia u = [X => 1.0, Y => 1.0] ps = [p => 1.0, k =>...