Ensure consistency between start values defined in modelDescription and in fmus

[Daniella1]

[clagms]

Hi @Daniella1 do you have a plan on how this can be achieved without violating the FMI standard? In particular the code should not read nor write to the model description file when the FMU is loaded (This would likely trigger antivirus warnings all over the place). The only way I see this done is via the command line when the fmu is initially generated... Such command could receive a specification of a model description and generate an FMU that matches it... This however seems like more work than what we can dispense at the moment...