Describe the bug
Concrete Simulator shows wrong clock values as if different clocks are being reset.
For example, in this simple model globalTime and extra are not used, only x is used, but the simulator shows that globalTime is being reset, x is not touched and extra does not even show any value.
Workaround: reload the engine (press F5) and observe the expected behavior:
To Reproduce
Steps to reproduce the behavior:
- Load the model: bug-in-concrete-simulator-clock-values.xml
- Switch to Concrete Simulator
- Press
Random to generate a trace
- Observe clock
x grow, while globalTime is being reset.
Expected behavior
Clock x should be reset and extra clock should grow together with globalTime.
Version(s) of UPPAAL tested
UPPAAL-5.1.0-beta5
UPPAAL-5.0.0
Desktop (please complete the following information):
Describe the bug
Concrete Simulator shows wrong clock values as if different clocks are being reset.
For example, in this simple model
globalTimeandextraare not used, onlyxis used, but the simulator shows thatglobalTimeis being reset,xis not touched andextradoes not even show any value.Workaround: reload the engine (press F5) and observe the expected behavior:
To Reproduce
Steps to reproduce the behavior:
Randomto generate a tracexgrow, whileglobalTimeis being reset.Expected behavior
Clock
xshould be reset andextraclock should grow together withglobalTime.Version(s) of UPPAAL tested
UPPAAL-5.1.0-beta5
UPPAAL-5.0.0
Desktop (please complete the following information):