(cd run_OMSimulator && /home/hudson/saved_omc/OMSimulator/install/bin/OMSimulator  --stripRoot --tempDir=temp_Buildings_13_Buildings_Examples_VAVCO2_VAVSystemCTControl_fmu --startTime=0 --stopTime=172800 --stepSize=69.12 --mode=me --timeout=240 --tolerance=1e-06 ../Buildings_13_Buildings_Examples_VAVCO2_VAVSystemCTControl.fmu)
info: *** FMU Simulation Info ***
     - model     : Buildings.Examples.VAVCO2.VAVSystemCTControl (model exchange)
     - fmiVersion: 2.0
     - startTime : 0.000000
     - stopTime  : 172800.000000
     - tolerance : 1e-06
     - stepSize  : 69.12
warning: [fmi2Warning] VAVSystemCTControl/logStatusWarning: /home/hudson/saved_omc/libraries/.openmodelica/libraries/Buildings 13.0.2-maint.13.x/Fluid/Movers/BaseClasses/FlowMachineInterface.mo:311: The following assertion has been violated at time 0.000000
         ((fan32.eff.yMot >= 0.0), fan32.eff.yMot=-1.040406182499978e-24) --> "Variable violating min constraint: 0.0 <= fan32.eff.yMot, has value: -1.04041e-24"
warning: [fmi2Warning] VAVSystemCTControl/logStatusWarning: /home/hudson/saved_omc/libraries/.openmodelica/libraries/Buildings 13.0.2-maint.13.x/Fluid/Movers/BaseClasses/FlowMachineInterface.mo:311: The following assertion has been violated at time 0.000000
         ((fan56.eff.yMot >= 0.0), fan56.eff.yMot=-1.262681949552937e-24) --> "Variable violating min constraint: 0.0 <= fan56.eff.yMot, has value: -1.26268e-24"
info:    maximum step size for 'VAVSystemCTControl.root': 69.120000
info:    Result file: Buildings_13_Buildings_Examples_VAVCO2_VAVSystemCTControl_res.mat (bufferSize=10)
info:    Parameter VAVSystemCTControl.roo.occ.cla1.delimiter will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.cla1.fileName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.cla1.tableName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.cla2.delimiter will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.cla2.fileName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.cla2.tableName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.office1.delimiter will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.office1.fileName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.office1.tableName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.office2.delimiter will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.office2.fileName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.office2.tableName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.smaRoo1.delimiter will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.smaRoo1.fileName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.smaRoo1.tableName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.smaRoo2.delimiter will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.smaRoo2.fileName will not be stored in the result file, because the signal type is not supported
info:    Parameter VAVSystemCTControl.roo.occ.smaRoo2.tableName will not be stored in the result file, because the signal type is not supported
info:    Variable VAVSystemCTControl.roo.roo45.senCO2.substanceName will not be stored in the result file, because the signal type is not supported
info:    Variable VAVSystemCTControl.roo.roo46.senCO2.substanceName will not be stored in the result file, because the signal type is not supported
info:    Variable VAVSystemCTControl.roo.roo47.senCO2.substanceName will not be stored in the result file, because the signal type is not supported
info:    Variable VAVSystemCTControl.roo.roo48.senCO2.substanceName will not be stored in the result file, because the signal type is not supported
info:    Variable VAVSystemCTControl.roo.roo49.senCO2.substanceName will not be stored in the result file, because the signal type is not supported
info:    Variable VAVSystemCTControl.roo.roo50.senCO2.substanceName will not be stored in the result file, because the signal type is not supported
LOG_ASSERT        | debug   | Solving non-linear system 3682 failed at time=115230.057706313.
|                 | |       | For more information please use -lv LOG_NLS.
error:   [fmi2logger] [fmi2Error] VAVSystemCTControl/logFmi2Call: fmi2GetDerivatives: terminated by an assertion.
error:   [getDerivatives] fmi2_getDerivatives failed for FMU "VAVSystemCTControl.root.VAVSystemCTControl"
LOG_ASSERT        | debug   | Solving non-linear system 3682 failed at time=115230.057706313.
|                 | |       | For more information please use -lv LOG_NLS.
error:   [fmi2logger] [fmi2Error] VAVSystemCTControl/logFmi2Call: fmi2GetDerivatives: terminated by an assertion.
error:   [getDerivatives] fmi2_getDerivatives failed for FMU "VAVSystemCTControl.root.VAVSystemCTControl"
info:    Final Statistics for 'VAVSystemCTControl.root':
         NumSteps = 555 NumRhsEvals  = 853 NumLinSolvSetups = 89
         NumNonlinSolvIters = 852 NumNonlinSolvConvFails = 12 NumErrTestFails = 20
info:    2 warnings
info:    4 errors