Francesco Casella

I then checked your original failing model with the debugger  This also seems correct to me, according to the shown execution flow, the dividir() function should get an input...

However, if I use the algorithmic debugger and put a breakpoint inside `dividir()`, when it is called, the input argument is zero.  So, there is something wrong in the...

Here is an MWE that reproduces your problem, without the crazy model structure 😄 ```modelica model TestInitialParameterInFunction parameter Real idivisor = F1(Datos); parameter Real Datos(fixed = false); Real inverse; Real...

@phannebohm, @kabdelhak we have the same problem with the new backend:  I guess there is some flaw in the excution order which is in common between the OB and...

@mpradovelasco thanks for the nice (and tough) test!

> It looks like the reports you are looking at are just exactly in the wrong order [@casella](https://github.com/casella). `-d=dumpSimCode` and the generated code show me this: > > ``` >...

> Oh the debugger orders ascending for the index? Are you kidding me, of course it does! The whole point of the debugger is to show the causalized sequence of...

> The base issue here is an old one. The event is exactly at the point of the singularity. Mathematically this is of course no issue, for event iteration this...

> Currently, there is no general symbolic routine to solve for an unknown of an equation in the NB. Ach so. > @phannebohm and I have also discussed this yesterday...

Adding @matteodepascali to the loop, so he's informed about the progress.