Opened 5 years ago

Last modified 3 years ago

#5922 assigned defect

Alias variables do not display in Transformational Debugger

Reported by: pierre.haessig@… Owned by: Martin Sjölund
Priority: normal Milestone:
Component: Debugger Version: v.1.15.0-dev
Keywords: Cc: Francesco Casella

Description

Dear OM developpers,

I'm creating an new issue for something that already mentioned as a comment by @casella (https://trac.openmodelica.org/OpenModelica/ticket/4712#comment:2): Alias variables and equation do not display in the Transformational Debugger. A related issue is that many model variables are absent in the Variables Brower of the debugger (the variables that got aliased I guess). This makes equation debugging harder.

Best,
Pierre

Attachments (1)

Alias_debug.mo (241 bytes ) - added by pierre.haessig@… 5 years ago.
test model to see that y variable is not displayed in Transformational Debugger

Download all attachments as: .zip

Change History (8)

comment:1 by Francesco Casella, 5 years ago

Could you provide a minimal working example? If we can't reproduce the issue it is hard to fix it. Thanks!

comment:2 by Francesco Casella, 5 years ago

Component: *unknown*Debugger
Owner: changed from somebody to Martin Sjölund
Status: newassigned

comment:3 by Francesco Casella, 5 years ago

Milestone: Future1.16.0

by pierre.haessig@…, 5 years ago

Attachment: Alias_debug.mo added

test model to see that y variable is not displayed in Transformational Debugger

comment:4 by pierre.haessig@…, 5 years ago

Ok, I've added a simple first order model, but with an extraneous variable y=x. As of OM 1.15 dev, the only two variables showing up in the Transformational Debugger are x and der(x). y is invisible, but there is an (alias) 3 initial equation which is probably y=x.
Ideally, something more explicit than "alias 3" should be displayed.

comment:5 by Francesco Casella, 4 years ago

Milestone: 1.16.01.17.0

Retargeted to 1.17.0 after 1.16.0 release

comment:6 by Francesco Casella, 4 years ago

Milestone: 1.17.01.18.0

Retargeted to 1.18.0 because of 1.17.0 timed release.

comment:7 by Francesco Casella, 3 years ago

Milestone: 1.18.0

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.