Environment - simulationEnvironment:
startTime=0
stopTime=172800
tolerance=1e-06
numberOfIntervals=2500
stepSize=69.12
Regular simulation: ./Buildings_1.6_Buildings.Examples.VAVCO2.VAVSystemCTControl  -abortSlowSimulation -alarm=480 -lv LOG_STATS
LOG_SUCCESS       | info    | The initialization finished successfully with 3 homotopy steps.
LOG_ASSERT        | info    | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/Buildings 1.6.0+build.1/Fluid/Movers/BaseClasses/FlowMachineInterface.mo:51:3-51:80:writable]
|                 | |       | The following assertion has been violated at time 0.008341
|                 | |       | ((fan32.r_N >= 0.0)) --> "Variable violating min constraint: 0.0 <= fan32.r_N, has value: -3.79259e-20"
LOG_ASSERT        | info    | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/Modelica 3.2.3+maint.om/Blocks/Interfaces.mo:329:5-330:56:writable]
|                 | |       | The following assertion has been violated at time 0.008341
|                 | |       | ((fan32.filter.y >= 0.0 and fan32.filter.y <= 1500.0)) --> "Variable violating min/max constraint: 0.0 <= fan32.filter.y <= 1500.0, has value: -5.68889e-17"
LOG_ASSERT        | info    | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/Buildings 1.6.0+build.1/Fluid/Movers/BaseClasses/FlowMachineInterface.mo:51:3-51:80:writable]
|                 | |       | The following assertion has been violated at time 0.008341
|                 | |       | ((fan56.r_N >= 0.0)) --> "Variable violating min constraint: 0.0 <= fan56.r_N, has value: -3.79259e-20"
LOG_ASSERT        | info    | [/home/hudson/saved_omc/libraries/.openmodelica/libraries/Modelica 3.2.3+maint.om/Blocks/Interfaces.mo:329:5-330:56:writable]
|                 | |       | The following assertion has been violated at time 0.008341
|                 | |       | ((fan56.filter.y >= 0.0 and fan56.filter.y <= 1500.0)) --> "Variable violating min/max constraint: 0.0 <= fan56.filter.y <= 1500.0, has value: -5.68889e-17"
LOG_STDOUT        | info    | Chattering detected around time 0.00834129016733..0.00922057203678 (100 state events in a row with a total time delta less than the step size 34.56). This can be a performance bottleneck. Use -lv LOG_EVENTS for more information. The zero-crossing was: res33.m_flow > 0.0
LOG_ASSERT        | debug   | Aborting simulation due to chattering being detected and the simulation flags requesting we do not continue further.