Supress warnings

[robha67]

Some FMUs generate a large number of warning messages during execution. These are not always possible to supress with, the current OMSimulator API (setLogginLevel). This results in very large log files or clobbered concol output.

An expanded setLogginLevel, that can help to supress all warnings, would be valuable.

@lochel @arun3688 @danlo76

[lenaRB]

you would need to parse the logs to filter out messages
proposal : for a specific FMU skip regexp messages - possible effect on performance - output from FMU could be piped to a filtering program
counterproposal : redirect logs, maybe 1 file per FMU
other proposal : disabling warning

• redirecting output is supported by passing a command line argument --logFile="" - it will then go to the terminal, so it can already be passed to a filtering program if Axel/Robert wants to implement it

[danlo76]

If redirected using --logFile="" then in this particular case the resulting log file becomes so large that it causes the simulation to crash. I'm looking for a way to completely suppress warnings, even those originating in the fmu itself.

[lenaRB]

-- Robert : the information needs to be discarded completely, because it cannot be handled during or post simulation anyway

[lenaRB]

If redirected using --logFile="" then in this particular case the resulting log file becomes so large that it causes the simulation to crash. I'm looking for a way to completely suppress warnings, even those originating in the fmu itself.

this should not be creating a log file, so @arun3688 needs to check if it works properly

[lenaRB]

@arun3688 and @danlo76 should discuss an example to test with as the flag does not seem to be enough in this special case

[danlo76]

@arun3688, @robha67 I unfortunately do not have an example (fmu) with this issue that I am allowed to share. I will get back to you if this changes.