Opened 11 years ago

Last modified 7 years ago

#2547 new enhancement

No math parsing for experiment annotation

Reported by: Jan Kokert Owned by: probably noone
Priority: normal Milestone: Future
Component: Backend Version: trunk
Keywords: math parsing experiment annotation Cc:

Description

Hi!

Thanks to the great fix in r18715, it is now possible to use the experiment annotation with StartTime, StopTime and Interval.
But sadly no math evaluation is done to rewrite the numbers for better readability, as demonstrated beneath:
(stopTime will be 1 and NumberofIntervals will be 500, which are the standard values :-(

model Test
  Real x;
equation
  x = sin(3.141 * time / (3600 * 24));
  annotation(experiment(StopTime = 60 * 60 * 24, Interval = 2 * 5));
end Test;

A warning appears:

[:0:0-0:0] Warning: Ignoring unknown experiment annotation option: StopTime = 60 * 60 * 24

Change History (13)

comment:1 by Adrian Pop, 11 years ago

That's because the specification does not allow it. There should be numbers in there and not expressions.

17.4 Annotations for Simulation Experiments
experiment_annotation:
annotation"(" "experiment" "(" [experimentOption] {, experimentOption}] ")"
experimentOption:
StartTime "=" ["+" | "-"] UNSIGNED_NUMBER |
StopTime "=" ["+" | "-"] UNSIGNED_NUMBER |
Interval "=" UNSIGNED_NUMBER
Tolerance "=" UNSIGNED_NUMBER

However, we could probably support expressions also if that is desired.

comment:2 by Jan Kokert, 11 years ago

Hi Adrian!

Oh, ok I didn't know that. Initializing variables in Modelica with math expressions is possible, so I tought it's the same with these simulation parameters.

If it's not a big efford, this enhancement would help me a lot, because I will deal with large simualtion times (years) in my doctoral thesis.

Best Regards
Jan

comment:3 by Martin Sjölund, 11 years ago

We could probably support it and add a notification it is not standard Modelica (not reading parameters or stuff from the model though; but I guess you don't need that).

comment:4 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:5 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:6 by Martin Sjölund, 9 years ago

Milestone: 1.9.31.9.4

Moved to new milestone 1.9.4

comment:7 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:8 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:9 by Martin Sjölund, 8 years ago

Milestone: 1.10.01.11.0

Ticket retargeted after milestone closed

comment:10 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:11 by Jan Kokert, 8 years ago

Are there any thoughts about this enhancment? - I'm still working with large simualtion times (years) in my doctoral thesis...

comment:12 by Jan Kokert, 8 years ago

Priority: highnormal
Type: defectenhancement

comment:13 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.

Note: See TracTickets for help on using tickets.