(cd run_OMSimulator-cs-cvode && /home/hudson/saved_omc/OMSimulator/install/bin/OMSimulator --resultFile=../ThermofluidStream_dev_ThermofluidStream.Idealized.Tests.Boundaries.Sink_free.Setpoints_OMSimulator-cs-cvode_res.mat --stripRoot --tempDir=temp_ThermofluidStream_dev_ThermofluidStream_Idealized_Tests_Boundaries_Sink_free_Setpoints_OMSimulator-cs-cvode_fmu --startTime=0 --stopTime=1 --stepSize=0.01 --mode=cs --timeout=240 --tolerance=1e-06 ../ThermofluidStream_dev_ThermofluidStream_Idealized_Tests_Boundaries_Sink_free_Setpoints_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 dense internal linear solver SUNLinSol_Dense. LOG_SOLVER | info | CVODE Use internal dense numeric jacobian method. LOG_SOLVER | info | CVODE uses internal root finding method NO 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 OFF info: *** FMU Simulation Info *** - model : ThermofluidStream.Idealized.Tests.Boundaries.Sink_free.Setpoints (co-simulation) - fmiVersion: 2.0 - startTime : 0.000000 - stopTime : 1.000000 - tolerance : 1e-06 - stepSize : 0.01 LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate9.p_min >= 611.657 and massFlowRate9.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate9.p_min <= 1e8, has value: 100" LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate8.p_min >= 611.657 and massFlowRate8.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate8.p_min <= 1e8, has value: 100" LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate7.p_min >= 611.657 and massFlowRate7.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate7.p_min <= 1e8, has value: 100" LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate6.p_min >= 611.657 and massFlowRate6.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate6.p_min <= 1e8, has value: 100" LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate5.p_min >= 611.657 and massFlowRate5.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate5.p_min <= 1e8, has value: 100" LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate4.p_min >= 611.657 and massFlowRate4.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate4.p_min <= 1e8, has value: 100" LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate3.p_min >= 611.657 and massFlowRate3.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate3.p_min <= 1e8, has value: 100" LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate2.p_min >= 611.657 and massFlowRate2.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate2.p_min <= 1e8, has value: 100" LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate1.p_min >= 611.657 and massFlowRate1.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate1.p_min <= 1e8, has value: 100" LOG_ASSERT | warning | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/ThermofluidStream 1.4.1-main/Interfaces/SISOFlow.mo:27:3-28:58:writable] | | | | The following assertion has been violated at time 0.000000 | | | | ((massFlowRate.p_min >= 611.657 and massFlowRate.p_min <= 1e8)) --> "Variable violating min/max constraint: 611.657 <= massFlowRate.p_min <= 1e8, has value: 100" info: Result file: ../ThermofluidStream_dev_ThermofluidStream.Idealized.Tests.Boundaries.Sink_free.Setpoints_OMSimulator-cs-cvode_res.mat (bufferSize=10) info: Variable Setpoints.massFlowRate.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.massFlowRate1.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.massFlowRate2.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.massFlowRate3.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.massFlowRate4.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.massFlowRate5.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.massFlowRate6.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.massFlowRate7.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.massFlowRate8.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.massFlowRate9.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink1.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink2.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink3.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink4.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink5.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink6.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink7.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink8.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.sink9.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source1.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source1.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source1.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source1.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source1.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source2.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source2.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source2.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source2.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source2.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source3.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source3.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source3.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source3.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source3.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source4.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source4.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source4.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source4.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source4.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source5.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source5.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source5.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source5.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source5.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source6.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source6.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source6.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source6.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source6.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source7.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source7.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source7.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source7.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source7.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source8.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source8.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source8.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source8.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source8.instanceName will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source9.displayPos1 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source9.displayPos2 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source9.displayPos3 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source9.displayPos4 will not be stored in the result file, because the signal type is not supported info: Variable Setpoints.source9.instanceName will not be stored in the result file, because the signal type is not supported