Pulse bad state
Generally when something in pulse gets into a bad state, it seems to correct it (e.g., if something goes negative it will often change it to 0). I recently did a very long run (>2 days of sim time), and the run ended with this error:
[ERROR] [198207(s)] SEScalar0To1 must be between [0,1]
Unfortunately, it doesn't indicate which scalar this happened to.
For this run I build from the latest on the integration branch (commit b4118c79) using the Soldier@0s.json
model with no injuries or anything. The only thing that happens is that every time the urine volume reaches 200 mL, the urinate action takes place. (We're trying to model dehydration.) I then let it run for a long time until it eventually stopped itself with the above error.
Long before that happens, these errors happen repeatedly, but don't cause the run to fail:
[WARN] [198207(s)] GeneralMath::CalculateConcentration: Volume is negative:-1223.6 mL. Setting it to 0.
[ERROR] [198207(s)] Compartment : SkinTissueExtracellular, Substance : Oxygen
[WARN] [198207(s)] GeneralMath::CalculateConcentration: Volume is negative:-1223.6 mL. Setting it to 0.
[ERROR] [198207(s)] Compartment : SkinTissueExtracellular, Substance : CarbonDioxide
[WARN] [198207(s)] GeneralMath::CalculateConcentration: Volume is negative:-1223.6 mL. Setting it to 0.
[ERROR] [198207(s)] Compartment : SkinTissueExtracellular, Substance : Nitrogen
Here's the complete log (compressed because uncompressed it's > 1 GB due to the above warnings/errors being repeated so much).
This is by no means blocking me or anything, it's just for you guys if you wanted to track down what was causing this.