Is `remake`ing an `ODEProblem` with a symbolic map of `u0` or `p` type-stable? about modelingtoolkit.jl HOT 5 CLOSED

See https://docs.sciml.ai/ModelingToolkit/stable/examples/remake/ and specifically https://docs.sciml.ai/ModelingToolkit/stable/examples/remake/#Re-creating-the-problem for ways in which updating parameters can be done in a tight loop.

There are also some type stability improvements in #2613

from modelingtoolkit.jl.

I'd recommend checking out SymbolicIndexingInterface.jl for that. You'd want to save getsyms=getu(prob, syms) outside of the loop and then use the function that it gives you inside (i.e. getsyms(sol)).

from modelingtoolkit.jl.

No, no symbolic map will be. That's just not possible. But setu and setp functions generate inferred things because it performs the symbolic parts in advance. remake is preserved as simple and high level

from modelingtoolkit.jl.

Thanks for answer Chris.

Could I ask as well if remake with symbolic maps are meant to be used in tight loops, like an optimization objective function?

Or would that call for a more performant but bespoke implementation?

More generally, is symbolic indexing in ModelingToolkit/SciMl intended for internal code and performance, or just for interactivity/flexibility (i.e plotting different ODESolution vars)?

from modelingtoolkit.jl.

Thanks for the pointers @SebastianM-C , I hadn't seen these docs before.

Final question: what is the idiomatic/performant way to access observed variables from an ODESolution?

In my loss function, I extract sol[:A] (where :A is an observed quantity), but have noticed that the return type of this indexing isn't inferred.

from modelingtoolkit.jl.