Opened 11 years ago
Last modified 3 years ago
#2584 new discussion
How to handle bad used StateSelect.never attribute?
Reported by: | Lennart Ochel | Owned by: | probably noone |
---|---|---|---|
Priority: | high | Milestone: | Future |
Component: | Backend | Version: | trunk |
Keywords: | Cc: |
Description
Should the following model fail or not?
model Unnamed Real y(fixed=true, stateSelect=StateSelect.never); equation der(y) = time; end Unnamed;
This is what the specification says:
type StateSelect = enumeration( never "Do not use as state at all.", avoid "Use as state, if it cannot be avoided (but only if variable appears differentiated and no other potential state with Attribute default, prefer, or always can be selected).", default "Use as state if appropriate, but only if variable appears differentiated.", prefer "Prefer it as state over those having the default value (also variables can be selected, which do not appear differentiated). ", always "Do use it as a state." );
Currently, the variable y gets selected as state anyway. That is not what I would expect for StateSelect.never.
Change History (10)
comment:1 by , 11 years ago
comment:2 by , 10 years ago
Milestone: | 1.9.1 → 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 by , 10 years ago
Milestone: | 1.9.2 → 1.9.3 |
---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:8 by , 8 years ago
Milestone: | 1.11.0 → 1.12.0 |
---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:9 by , 7 years ago
Milestone: | 1.12.0 → 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 by , 3 years ago
Discussion continues on https://github.com/OpenModelica/OpenModelica/issues/2584
I think you should either report an error or at least a warning.