val return different result on windows an linux on event point

[jfrenkel]

The model simulation_modelica_others.sample3.mos returns for the values on windows and linux different values. The problem is that at the timepoint 0.5 an event occures and on linux val return the value before the event and on windows val return the value behind the event.

"i1.el.val"

2.0

-7.0
+6.0

12.0
"i2.el.val"
41.0

-46.0
+45.0

51.0
"i3.el.val"
3.0

-503.0
+502.0

1002.0

[adrpo]

Anybody has a 32 bit Linux to test if it behaves like Windows?
At least we can find out if this a a 64 vs. 32 bit problem or a Windows vs. Linux one.

[adrpo]

It seems that since revision r14297 this model has the same results in Linux as in Windows:
​https://test.openmodelica.org/hudson/job/OpenModelica_TEST_CLANG/2676/testReport/(root)/simulation_modelica_others/sample3_mos/
Which one is correct?

[sjoelund.se]

Aha! Found it.... Sent an email about this yesterday:

32-bit linux:

build@build:~/tmp/build/openmodelica-14323/testsuite/simulation/modelica/others
omc sample3.mos
...
"i1.el.val"
2.0
6.0
11.0
"i2.el.val"
41.0
45.0
50.0
"i3.el.val"
3.0
502.0
1002.0

64-bit linux:
"i1.el.val"
2.0
7.0
12.0
"i2.el.val"
41.0
46.0
51.0
"i3.el.val"
3.0
503.0
1002.0

And reading the ticket... I would say the testcase is wrong. You do not use val() on the exact time of an event. Use a time after the event, like 0.501 instead of 0.500 in order to assure you get the value after the event.

[sjoelund.se]

Postponed until 1.9.1

[sjoelund.se]

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

[sjoelund.se]

Milestone changed to 1.9.3 since 1.9.2 was released.

[sjoelund.se]

Moved to new milestone 1.9.4

[sjoelund.se]

Milestone pushed to 1.9.5

[sjoelund.se]

Milestone renamed

[sjoelund.se]

Ticket retargeted after milestone closed

[sjoelund.se]

Milestone moved to 1.12.0 due to 1.11.0 already being released.