id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5860	Provide correct and efficient event handling in --daeMode	Francesco Casella	Andreas Heuermann	"AnHeuermann reports in ticket:5843#comment:1:

Let's start with a first class of problems:
 '''Verification failed'''
 See e.g. Modelica.Blocks.Examples.BooleanNetwork1.
This model has integer and boolean variables, which are not treated correctly. The values are not updated after events and remain constant.
Enabling tearing (minimal, cellier, omc) and looking at the tearing dumps shows that no discrete variables are moved to inner variables. That makes sense for ode case, since there are no loops. But for the dae mode we want to causalize the discrete variables.
 
And how should the dae mode handle discrete state variables?

Actually when looking at the discrete states we have for ode
{{{
* Number of discrete states: 12 (falling.not_u,rising.u,set1.y,changing.u,triggeredAdd.y,booleanTable.combiTimeTable.nextTimeEventScaled,onDelay.t_next,onDelay.delaySignal,$whenCondition3,$whenCondition2,booleanTable.combiTimeTable.nextTimeEvent,rSFlipFlop.pre.u)
}}}
and for dae the dump is not working(?):
{{{
 * Number of states: 0 ()
 * Number of discrete states: 0 ()
}}}

And why is `$whenCondition3` a state in the first case at all?
"	defect	assigned	blocker	2.0.0	Run-time				Karim Adbdelhak adrien.guironnet@…