Environment - simulationEnvironment: startTime=0 stopTime=86400 tolerance=1e-06 numberOfIntervals=2500 stepSize=34.56 Regular simulation: ./Buildings_10_Buildings.Applications.DataCenters.ChillerCooled.Examples.NonIntegratedPrimarySecondaryEconomizer -abortSlowSimulation -alarm=400 -emit_protected -lv LOG_STATS assert | warning | The following assertion has been violated at time 0.000000 | | | | ahu.fan.etaHyd >= 0.0 assert | warning | Variable violating min constraint: 0.0 <= ahu.fan.etaHyd, has value: -4.59545e-21 LOG_SUCCESS | info | The initialization finished successfully with 3 homotopy steps. assert | info | The following assertion has been violated at time 60.000000 | | | | cooTow[1].FRWat >= 0.0 and cooTow[1].FRWat <= 1.0 assert | info | Variable violating min/max constraint: 0.0 <= cooTow[1].FRWat <= 1.0, has value: 1.00038 assert | info | The following assertion has been violated at time 69.120000 | | | | cooTow[2].TAppCor >= 0.0 assert | info | Variable violating min constraint: 0.0 <= cooTow[2].TAppCor, has value: -6.42457 assert | info | The following assertion has been violated at time 120.000000 | | | | cooTow[2].FRWat >= 0.0 and cooTow[2].FRWat <= 1.0 assert | info | Variable violating min/max constraint: 0.0 <= cooTow[2].FRWat <= 1.0, has value: 1.00039 assert | info | The following assertion has been violated at time 1200.000000 | | | | chiWSE.chiPar.chi[2].vol2.p >= 0.0 and chiWSE.chiPar.chi[2].vol2.p <= 100000000.0 assert | info | Variable violating min/max constraint: 0.0 <= chiWSE.chiPar.chi[2].vol2.p <= 100000000.0, has value: 1.55474e+11 assert | info | The following assertion has been violated at time 1200.000000 | | | | priPum.pum[1].port_b.p >= 0.0 and priPum.pum[1].port_b.p <= 100000000.0 assert | info | Variable violating min/max constraint: 0.0 <= priPum.pum[1].port_b.p <= 100000000.0, has value: 1.55474e+11 assert | info | The following assertion has been violated at time 1200.000000 | | | | priPum.pum[2].port_b.p >= 0.0 and priPum.pum[2].port_b.p <= 100000000.0 assert | info | Variable violating min/max constraint: 0.0 <= priPum.pum[2].port_b.p <= 100000000.0, has value: 1.55474e+11 assert | info | The following assertion has been violated at time 1203.902280 | | | | secPum.pum[2].etaHyd >= 0.0 assert | info | Variable violating min constraint: 0.0 <= secPum.pum[2].etaHyd, has value: -7.06581e-14 assert | info | The following assertion has been violated at time 1209.600000 | | | | pumCW[1].eff.yMot >= 0.0 assert | info | Variable violating min constraint: 0.0 <= pumCW[1].eff.yMot, has value: -9.14274e-30 assert | info | The following assertion has been violated at time 1209.600000 | | | | pumCW[2].eff.yMot >= 0.0 assert | info | Variable violating min constraint: 0.0 <= pumCW[2].eff.yMot, has value: -9.14274e-30 assert | info | The following assertion has been violated at time 1261.440000 | | | | secPum.pum[2].eff.yMot >= 0.0 assert | info | Variable violating min constraint: 0.0 <= secPum.pum[2].eff.yMot, has value: -1.24071e-66 assert | info | The following assertion has been violated at time 1641.600000 | | | | priPum.pum[2].etaHyd >= 0.0 assert | info | Variable violating min constraint: 0.0 <= priPum.pum[2].etaHyd, has value: -5.14239e-18 LOG_STATS | info | ### STATISTICS ### | | | | | timer | | | | | | 0.118913s reading init.xml | | | | | | 0.0108136s reading info.xml | | | | | | 0.0033252s [ 0.2%] pre-initialization | | | | | | 0.0346799s [ 2.4%] initialization | | | | | | 7.8878e-05s [ 0.0%] steps | | | | | | 0.0419805s [ 2.9%] solver (excl. callbacks) | | | | | | 0.0229996s [ 1.6%] creating output-file | | | | | | 0.265548s [ 18.3%] event-handling | | | | | | 0.0657536s [ 4.5%] overhead | | | | | | 1.01709s [ 70.1%] simulation | | | | | | 1.45146s [100.0%] total | | | | | events | | | | | | 29 state events | | | | | | 0 time events | | | | | solver: dassl | | | | | | 3345 steps taken | | | | | | 4821 calls of functionODE | | | | | | 821 evaluations of jacobian | | | | | | 214 error test failures | | | | | | 3 convergence test failures | | | | | | 0.609503s time of jacobian evaluation LOG_SUCCESS | info | The simulation finished successfully.