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
@ismailsenoz often works with ODE-based models in RxInfer and suggested an interesting idea: natively supporting ODE-like statements in the @model macro, so that users wouldn’t need to manually discretize state transition functions. I think this could be quite elegant and useful.
In principle, we could automatically handle discretization using libraries like SeeToDee.jl. One idea is to introduce a nested macro, e.g.:
However, I’m unsure whether this is the right direction — macros don’t always compose nicely, and this could complicate implementation internally.
An alternative might be introducing a special symbol for such expressions, like:
@modelfunctionmy_model()
x_next ≛f(x, u)dt
end
(or something similar).
@ismailsenoz — could you write down a few examples of how you’d ideally like to use this, based on your current ODE workflows? What variables should it involve? How to handle dt? Do we want to automatically support logdt, etc? More examples - better. Then we can brainstorm implementation strategies together with @wouterwln, potentially for GraphPPL and RxInfer.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
@ismailsenoz often works with ODE-based models in RxInfer and suggested an interesting idea: natively supporting ODE-like statements in the @model macro, so that users wouldn’t need to manually discretize state transition functions. I think this could be quite elegant and useful.
In principle, we could automatically handle discretization using libraries like SeeToDee.jl. One idea is to introduce a nested macro, e.g.:
However, I’m unsure whether this is the right direction — macros don’t always compose nicely, and this could complicate implementation internally.
An alternative might be introducing a special symbol for such expressions, like:
(or something similar).
@ismailsenoz — could you write down a few examples of how you’d ideally like to use this, based on your current ODE workflows? What variables should it involve? How to handle
dt
? Do we want to automatically supportlogdt
, etc? More examples - better. Then we can brainstorm implementation strategies together with @wouterwln, potentially for GraphPPL and RxInfer.Beta Was this translation helpful? Give feedback.
All reactions