Opened 10 years ago

Closed 10 years ago

#2903 closed enhancement (fixed)

Output protected variables in OMEdit simulations

Reported by: Francesco Casella Owned by: Adeel Asghar
Priority: high Milestone: 1.9.1
Component: OMEdit Version: trunk
Keywords: Cc:

Description

the -emit_protected flag applied to the simulation executable outputs the protected variables.

A flag should be added in the Simulation setup | Output tab to set this flag.

Change History (3)

comment:1 by Adeel Asghar, 10 years ago

The simulation flags are in Simulation Flags tab and not in Output tab.

I can add GUI for setting -emit_protected flag. But,
There are several simulation flags and new ones keep on coming so I have created a GUI option Additional Simulation Flags (Optional):, you can find it at the bottom of Simulation Flags tab.
You can add -emit_protected there and it will be passed to the simulation executable.

in reply to:  1 comment:2 by Francesco Casella, 10 years ago

Replying to adeas31:

The simulation flags are in Simulation Flags tab and not in Output tab.

True, but from a conceptual point of view, deciding whether the protected variables should be written or not is on the same level as "Variable filter" or "Number of intervals", right?

I can add GUI for setting -emit_protected flag. But,
There are several simulation flags and new ones keep on coming so I have created a GUI
option Additional Simulation Flags (Optional):, you can find it at the bottom of
Simulation Flags tab.
You can add -emit_protected there and it will be passed to the simulation executable.

I don't think this is a good idea. The whole point of a GUI is to avoid that people need to read manuals and use clumsy and obscure flags. If there are many options we should try to organize them in a logical way, rather then having 50 of them on the same window, but I don't see any reason why they shouldn't be all handled by the GUI.

In other words, when my colleague Andrea Bartolini asked me how to include those variables in the output, I asked Lennart, and I got the answer in 10 minutes, but this is not a sustainable process if OMC is going to be used by a large number of people.

Last, but not least, a similar flag has been in Dymola for ages, and for good reasons. Why should people need to study the documentation (that, incidentally, does not mention this flag at all, see #2904) to get it in OMC?

comment:3 by Adeel Asghar, 10 years ago

Resolution: fixed
Status: newclosed

Done in r22823.

Note: See TracTickets for help on using tickets.