Francesco Casella

Original issue: https://trac.openmodelica.org/OpenModelica/ticket/2152. As I understand, we currently have proper time events implemented for `sample()`, but not for events such as `if time < t0 then exp1 else exp2`, where...

> I think in the NB we transform `time > t0` to `sample(t0, 'inf')` so it should already be handled efficiently. Of course it would be great to have proper...

> Yes, currently `t0` needs to be a parameter or constant. In fact we should be able to handle any linear relation of time, e.g., `2*time + t0 > sin(t1...

@arun3688 the problem is that when one runs a simulation in OMEdit those flags are somehow taken as default choices - probably OMEdit sets them silently when before calling the...

Further piece of information. If you try this MWE ```modelica model TestExponential Real x(start = 1, fixed = true); Real x_check; equation der(x) = -x; x_check = exp(-time); assert(abs(x -...

_Model_ parameters and _simulation_ parameters are two different namespaces, used by different API functions, `setParameters()` and `setSimulationOptions()`. Of course if you call them both stopTime in your Python program there...

@henrikt-ma what do you think?

There is one crucial point I missed in my previous post. As I understand, the way we currently handle events is such that integration is carried out _without changing the...

Regarding interpolation, you wrote in your Slack post: > I'm not sure if we need that for event search though. As I understand we currently interpolate all states anyway during...

BTW, there is another optimization we may consider. In some cases (@albertoleva has some very nice use cases about event-based controllers) you may have digital control algorithms that are invoked...