Maplesoft FMI

The projection method also has advantages from an FMU implementation standpoint. Unlike the dummy derivative method, a partitioning of the constraint set into any number of well conditioned sub-problems is...

A rough outline of how this could be made backward compatible as follows: 1) Add an attribute to the model description: applyProjection with default value "completedStep" which tells when projection...

I have only proposed exposure of the fmi3Projection interface for 3.1 to allow importers finer control over the fmu behavior. For example, for a well behaved system it may not...

As for the existing mechanism, in section 3.2.1 of the FMI3 specification the fmi3CompletedIntegratorStep function is described in detail. A couple examples of its usage are provided. I would suggest...

We're fine with using aarch64-darwin for ARM64 Macs (and darwin64 for Intel Macs) for now but the proposal to support both naming schemes is a bit messy. Are we going...

@klausschuch There already is a function for getting nominals at least for the states (fmi3GetNominalsOfContinuousStates). Since we already added a clarification to 3.0.1 that all array elements will get scaled...

@binghe Yes you can, notice that nValues does NOT have to equal nValueReferences. So you can have valueReferences = [5] and values = [1.0, 2.0, 3.0, 4.0] to set a...

Yes, your FMU will have to know that value reference 5 represents an array and assign the appropriate number of values from the 'values' array.

It might be helpful be to point out the change in the FMI2 capability flag completedIntegratorStepNotNeeded (default=false). In FMI3 the equivalent is needsCompletedIntegratorStep but to maintain the functionality of FMI2...