Todo:

Created by: CThuleHansen

Bulletins marked with italic are features being considered for implementation.

• Add errors. What sort of errors are necessary to model?
• Error: Invalid valuereferences are modelled as described on p.16 of STD
• Add topological sort - Necessary? A possible solution is a sequence of get/set variables, such that the user specify the order.
• Add set/get directional deritivates - Necessary?
• Add get/set state. The implementation of get/set state is up to the individual FMU. if getState is invoked, then the FMU must return a nat. This nat must map to a state internally in the FMU. It is the responsibility of the FMU to restore this state, if setState is invoked with this nat.
• Add GetMaxStepSize
• Set/get variables in initialization mode. Since it is a CML model and therefore requires separate configuration anyway, this functionality could be neglected by configuring the FMUs to start in the correct state. This would simplify the CML models of both the MA and the FMUs significantly.