(cd run_OMSimulator-cs-cvode && /home/hudson/saved_omc/OMSimulator/install/bin/OMSimulator --stripRoot --tempDir=temp_Buildings_13_Buildings_Examples_VAVCO2_VAVSystemCTControl_OMSimulator-cs-cvode_fmu --startTime=0 --stopTime=172800 --stepSize=69.12 --mode=cs --timeout=240 --tolerance=1e-06 ../Buildings_13_Buildings_Examples_VAVCO2_VAVSystemCTControl_OMSimulator-cs-cvode.fmu) LOG_SOLVER | info | CVODE linear multistep method CV_BDF LOG_SOLVER | info | CVODE maximum integration order CV_ITER_NEWTON LOG_SOLVER | info | CVODE use equidistant time grid YES LOG_SOLVER | info | CVODE Using relative error tolerance 1.000000e-06 LOG_SOLVER | info | CVODE Using sparse linear solver SUNLinSol_KLU. LOG_SOLVER | info | CVODE Use sparse Jacobian method coloredNumerical LOG_SOLVER | info | CVODE uses internal root finding method YES LOG_SOLVER | info | CVODE maximum absolut step size 0 LOG_SOLVER | info | CVODE initial step size is set automatically LOG_SOLVER | info | CVODE maximum integration order 5 LOG_SOLVER | info | CVODE maximum number of nonlinear convergence failures permitted during one step 10 LOG_SOLVER | info | CVODE BDF stability limit detection algorithm ON info: *** FMU Simulation Info *** - model : Buildings.Examples.VAVCO2.VAVSystemCTControl (co-simulation) - 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: Result file: Buildings_13_Buildings_Examples_VAVCO2_VAVSystemCTControl_OMSimulator-cs-cvode_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 info: 2 warnings info: 0 errors