Opened 12 years ago

Closed 7 years ago

#1976 closed defect (invalid)

val return different result on windows an linux on event point

Reported by: Jens Frenkel Owned by: Adrian Pop
Priority: high Milestone: 1.12.0
Component: Backend Version: trunk
Keywords: Cc: Willi Braun, Lennart Ochel

Description

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

Change History (12)

comment:1 by Adrian Pop, 12 years ago

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.

comment:2 by Adrian Pop, 12 years ago

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?

comment:3 by Martin Sjölund, 12 years ago

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.

Last edited 12 years ago by Martin Sjölund (previous) (diff)

comment:4 by Martin Sjölund, 11 years ago

Milestone: 1.9.01.9.1

Postponed until 1.9.1

comment:5 by Martin Sjölund, 10 years ago

Milestone: 1.9.11.9.2

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).

comment:6 by Martin Sjölund, 10 years ago

Milestone: 1.9.21.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:7 by Martin Sjölund, 9 years ago

Milestone: 1.9.31.9.4

Moved to new milestone 1.9.4

comment:8 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:9 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:10 by Martin Sjölund, 8 years ago

Milestone: 1.10.01.11.0

Ticket retargeted after milestone closed

comment:11 by Martin Sjölund, 8 years ago

Milestone: 1.11.01.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:12 by Francesco Casella, 7 years ago

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.