Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define zero-crossing surfaces as varaiables #587

Open
masoud-najafi opened this issue Jun 30, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@masoud-najafi
Copy link
Collaborator

commented Jun 30, 2019

Instead of a using two APIs to retrieve zero-crossing surfaces and their number, individual zero-crossing surfaces can be defined as variables in FMI-3. Defining zero-crossing surfaces in this way presents several advantages:

  1. Get rid of fmi3Status fmi3GetEventIndicators(fmi3Component c, fmi3Float64 eventIndicators[], size_t ni);
  2. Get rid of fmi3Status fmi3GetNumberOfEventIndicators(fmi3Component c, size_t* nz);
  3. get rid of the "numberOfEventIndicators" attribute in the XML
  4. Each zero-crossing surface can have its own name and description which is useful in case of problem during the simulation, such as sliding model.
  5. Zero-crossing surfaces can be monitored individually, and may even be outputted at output ports of the FMU.

Designation of the variables that take part in the zero-crossing vector:
In the ModelStructure the subsection can be defined. This allows indicating the reference of variables that make the zero-crossing vector as well as the dependency of zero-crossing surfaces on other variables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.