Different AVATAR specifications depending on how a model is designed using the GUI

When designing a model using the GUI, depending on the order in which transitions are added in a SMD, the generated avspec differs. The attached model illustrates this bug with two empty transitions originating from a state called "incrementingN." emptyTransitions.xml

added AVATAR label

assigned to @ludovic.apvrille

changed the description

Problem since to be linked to the introduction of optimizations by the model-checker, maybe this bug cannot be solved? ;-)

This problem occurs either from the faulty design, or from the non faulty one, cong of tranformationg!

Actually, the generated avatar spec seems good, so the bug is probably in the drawing functiong, still to be investigated!

Good news: the bug was in fact only in the compact dependency graph generation.

I have produced a fix pushed in [master 70ea8891]

Hopefully it resolves the bug without impacting other systems.

Tests shall be added for this once the import from SysML v2 text works.

closed