Skip to content
This repository has been archived by the owner on Oct 17, 2023. It is now read-only.

FMU Checker does not terminate for fmi2Status fmi2Fatal #37

Open
AnHeuermann opened this issue Nov 12, 2018 · 0 comments
Open

FMU Checker does not terminate for fmi2Status fmi2Fatal #37

AnHeuermann opened this issue Nov 12, 2018 · 0 comments
Labels

Comments

@AnHeuermann
Copy link

When returning a fatal error in function fmi2NewDiscreteStates the FMUComplianceChecker does not terminate model simulation but tries to call function fmi2NewDiscreteStates again.

So setting
FMI2_Export fmi2Status fmi2NewDiscreteStates(fmi2Component c, fmi2EventInfo* fmiEventInfo) { return fmi2Fatal; }
yields to an infinite loop.

The FMI specification 2.0 page 17 states:

fmi2Fatal – the model computations are irreparably corrupted for all FMU instances. [For example,
due to a run-time exception such as access violation or integer division by zero during the execution
of an fmi function]. Function “logger” was called in the FMU (see below) and it is expected that this
function has shown the prepared information message to the user. It is not possible to call any other
function for any of the FMU instances.

I get this behavior with pre-build executable version 2.0.4 on 64Bit Windows 10 and build of commit dcc15abc94038a7afb8d4828d2bf3ea359de6c09 on 64Bit Unix system.
Can someone reproduce this problem?

AnHeuermann pushed a commit to niklwors/OMCompiler that referenced this issue Nov 13, 2018
@beutlich beutlich added the bug label Mar 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants