Opened 10 years ago

Last modified 5 years ago

#2689 assigned defect

mapping of zero crossings to equations does not work properly

Reported by: lochel Owned by: Karim.Abdelhak
Priority: high Milestone: 2.0.0
Component: Backend Version: trunk
Keywords: Cc: sjoelund.se, wbraun

Description (last modified by lochel)

The mapping from zero crossings to equations does not work as soon as a model get split up into various equation systems (partitioning). The zero crossing contains only a equation index but no information about the appropriate equation system. The issue can be reproduced using the following model:

model test1
  Boolean a;
  Real b(start=0.7, fixed=true);
equation
  der(b) = if b > 0 then -1 else 1;
  a = time < 0.5 or time < 0.6;
end test1;

The debugger pinpoints a = time < 0.5 or time < 0.6 instead of der(b) = if b > 0 then -1 else 1. If both equations get reordered the debugger pinpoints the correct equation.

Change History (10)

comment:1 Changed 10 years ago by lochel

  • Description modified (diff)

comment:2 Changed 10 years ago by sjoelund.se

  • Milestone changed from 1.9.1 to 1.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:3 Changed 9 years ago by sjoelund.se

  • Milestone changed from 1.9.2 to 1.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:4 Changed 9 years ago by sjoelund.se

  • Milestone changed from 1.9.3 to 1.9.4

Moved to new milestone 1.9.4

comment:5 Changed 8 years ago by sjoelund.se

  • Milestone changed from 1.9.4 to 1.9.5

Milestone pushed to 1.9.5

comment:6 Changed 8 years ago by sjoelund.se

  • Milestone changed from 1.9.5 to 1.10.0

Milestone renamed

comment:7 Changed 7 years ago by sjoelund.se

  • Milestone changed from 1.10.0 to 1.11.0

Ticket retargeted after milestone closed

comment:8 Changed 7 years ago by sjoelund.se

  • Milestone changed from 1.11.0 to 1.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:9 Changed 6 years ago by casella

  • Milestone changed from 1.12.0 to Future

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:10 Changed 5 years ago by casella

  • Milestone changed from Future to 2.0.0
  • Owner changed from probably noone to Karim.Abdelhak
  • Status changed from new to assigned
Note: See TracTickets for help on using tickets.