±∞ start values in FMI 3.0 model description are rejected

[yoerg]

If a FMI 3.0 FMU defines a parameter/input start value of INF or -INF, e.g.

<Float64 name="realInput" valueReference="1" causality="input" variability="continuous" start="INF" />

fmi3_import_parse_xml results in a parser error:

Error parsing XML: FMI3XML: min/max value boundary check for parsing Float64 failed
FMI3XML: XML element 'Float64': failed to parse attribute start='INF'

The same happens for Float32 variables with infinite start values.

This looks to be deliberate, but in my reading of Table 15. Type element and attribute details, infinite floating point start values should be allowed on IEEE 754 platforms:

If not defined, the minimum is the largest negative number that can be represented on the machine for that <TypeDefinition>.

The FMI 2.0 XML parser accepts infinite start values.