Opened 8 years ago
Last modified 3 years ago
#3985 new enhancement
Implement debug logging features in FMUs
| Reported by: | Francesco Casella | Owned by: | Adeel Asghar |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | FMI | Version: | |
| Keywords: | Cc: |
Description
Debugging OMC-generated FMUs is currently very hard, because it is not possible to get additional logging info, e.g. about the nonlinear solver iterations.
The current OMC logging interface should be linked to the FMI logging function. I understand from an e-mail discussion that it is possible to do so without any overhead when logging is turned off, by using the functions:
fmi2Status
fmi2SetDebugLogging(fmi2Component c, fmi2Boolean loggingOn,
size_t nCategories, const fmi2String categories[]);
Change History (9)
comment:1 by , 8 years ago
comment:3 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:4 by , 7 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 , 5 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 , 4 years ago
| Milestone: | 1.17.0 → 1.18.0 |
|---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
Note:
See TracTickets
for help on using tickets.
Note that we would also need to call the callback logger function in the FMU, which I believe is not done either.