Scheduled_down and Waiting_for_operator states

Hi there,

in the attached model, the source, Operator1 and both Processor1 and Processor2 belong to a 7 days and 8 hours timetable.

So I expect 66.7 % for the state 'Scheduled_down'.

This is the case for Processor2 and for Operator1, but not for Processor1.

Processor1 shows a lower percentage for 'Scheduled_down' than 66.7 % and also a high percentage for 'Waiting_for_Operator'.

But how can an object wait for an operator, when it's scheduled down?

So why is the percentage of Processor1 for 'Scheduled_down' lower than 66.7 %?

Please run the model fast until time = 604800 s, what is exactly 7 days.

Kind regards,

Markus Bans

It is because of the order of the stopobject() calls.

When you call stopobject() on an operator who is being utilized by a processor, that operator then in turn calls stopobject() on the processor to make it waiting_for_operator.

So what is happening is that you are stopping the processor, then stopping the operator, which in turn stops the processor again, so the processor is in waiting_for_operator state during its down time.

To fix this you could reorder the members of the time table, but this isn't really a good solution.

The better solution is to increase the priority on the stop request for the time table. In the time table's Down Function, change the priority value from 0 to 1. This way, when the operator calls stopobject() on the processor, that stop request's priority is 0, but the scheduled_down stop that it is currently in has a priority of 1 so it stays in the scheduled_down state.