Opened 11 years ago

Last modified 6 years ago

#2618 assigned defect

Reinitial in algorithm section also continuos relations

Reported by: Willi Braun Owned by: Karim Adbdelhak
Priority: high Milestone: Future
Component: Backend Version: trunk
Keywords: Cc: Lennart Ochel, Martin Sjölund

Description

In the following example, we introduce a memory in algorithms, since while the continuous integration relations are fixed. But they need to re-initialized for every execution.

model BreakFor
  //extends Icons.TestCase;
  Real x;
algorithm
  x := 1;
  for i in 1:10 loop
    x := x * 2;
    //print("loop= " +& intString(i) +&" x == " +& realString(x) +& "\n");
    if x > 25 then
      break;
    end if;
  end for;
  //print(" x == " +& realString(x) +& "\n");
  assert(x >= 32, "x was not set correctly.");
  annotation (
    __ModelicaAssociation(TestCase(shouldPass = true, section = {"11.2.4"})),
    experiment(StopTime = 0.01),
    Documentation(
      info = "<html>Tests the functionality of <pre>break</pre> inside a for-loop.</html>"));
end BreakFor;

Change History (13)

comment:1 by Willi Braun, 11 years ago

Cc: Lennart Ochel Martin Sjölund added

comment:2 by Willi Braun, 11 years ago

We need to handle relations in algorithm as literal, to avoid the memory effect for algorithm.

comment:3 by Willi Braun, 11 years ago

Owner: changed from probably noone to Willi Braun
Status: newaccepted

The main issue here is that we try to evaluate relations of algorithm as zeroCrossings without the algorithm, what is obvious wrong. We need to re-write that part completely, in the sense that all _all_ zero-crossing relations should trigger change while the execution of them and not in a separated evaluation.

comment:4 by Willi Braun, 11 years ago

It's also connect to #2433.

Version 0, edited 11 years ago by Willi Braun (next)

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

Milestone: 1.12.0Future

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.

comment:13 by Francesco Casella, 6 years ago

Owner: changed from Willi Braun to Karim Adbdelhak
Status: acceptedassigned
Note: See TracTickets for help on using tickets.