Opened 9 years ago
Last modified 4 years ago
#3986 new enhancement
Allow setting default simflags in FMUs
| Reported by: | Francesco Casella | Owned by: | Adeel Asghar |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | FMI | Version: | |
| Keywords: | Cc: |
Description
In some cases, the successful operation of FMUs might depend on low-level runtime options, such as -newtonFTol, -newtonXTol, -ls, etc.
It is essential that the person in charge of packaging the FMU (usually an expert) can fine-tune all these settings based on his knowledge, so as to guarantee the best possible performance of the FMU on the end-user side.
I would suggest to allow setting values for these flags different from the default ones by adding an input String simflags to the translateModelFMU and buildModelFMU API functions.
This could also serve as a makeshift way to get more logging info, while #3985 is implemented.
Change History (9)
comment:1 by , 9 years ago
comment:3 by , 9 years ago
| Milestone: | 1.11.0 → 1.12.0 |
|---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:4 by , 8 years ago
| Milestone: | 1.12.0 → 1.13.0 |
|---|
Milestone moved to 1.13.0 due to 1.12.0 already being released.
comment:6 by , 6 years ago
| Milestone: | 1.14.0 → 1.16.0 |
|---|
Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0
comment:8 by , 5 years ago
| Milestone: | 1.17.0 → 1.18.0 |
|---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
And/or to expose all these settings as FMI parameters that can be set during FMU instantiation.