Make sure you stop model with the stop button before collecting state based statistics

For those who are unaware (like myself until today) the state based statistics will not take into account the most recent time spent in a given state (eg idle time after an operation has finished) unless the updatestates() command is called. This is called when you push the stop button, but NOT when you just slow the model time down to 0.

Regards
Paul

Paul,

The update states command is also not called when you hit the pause button. The reason for this is that it can take some time for a model to update states if the model is very large and we wanted to give the users a way to pause the model without having to incure the delay. This is the reason that slowing the model speed to zero and hitting pause do not update states.

Since updatestates() acts on all objects in the model, you may want to be more selective on where and how frequently you use it. Use updatestate() if you are interested in a single object or a select few.

The long way (for further understanding of the state tree)
The updated total idle time of a single object can be obtained with the code below without using updatestate(). I am assuming in this example that "operator" is a pointer to the object we are interested in. Note that in the state tree, the state_since node is a time stamp when the object changed into its current state (when the state profile was last updated).


double totalidletime = getnodenum(rank(state_profile(operator), STATE_IDLE));

if(getstatenum(operator)==STATE_IDLE)

totalidletime += time() - getnodenum(state_since(operator));