Why doesn't the Stop Model Based on Condition work in the attached HC model

Question

question

Tee Hiett asked May 13, '17 Tee Hiett commented May 16, '17

Why doesn't the Stop Model Based on Condition work in the attached HC model

I have a Stop Model Based on Condition in the PatientExit1 object but the model still runs to the end of simulation time. The condition is:

int condition = /**/getthroughput(model) >= content(var(PatientArrivals1, VAR_ScheduledArrivals)).

It seems the getthroughput side of the equation is working properly.

Thanks,

Tee

Software Version:

FlexSim HC 5.1.0

healthcare condition

idbc-triage-room-05-09-17-c.fsm (907.2 KiB)

Answer 1 · 2017-05-15T18:49:09Z

Matthew Gillespie answered May 15, '17 Tee Hiett commented May 16, '17

This is because at the time you're checking (in the On Entry trigger of the Exit) the patient leaving the model is still in the model. That means getthroughput(model) will be one less than it will be as soon as this code fires and then the patient actually leaves the model. So when the last (41st) patient enters the Exit, this code fires and you end up checking:

if(40 >= 41)
	finishreplication();

So this condition is never satisfied, even on the last patient, so it runs the full time. You could change the condition to:

int condition = /**/getthroughput(model) + 1 >= content(var(PatientArrivals1, VAR_ScheduledArrivals))

· 3

Lou Keller commented · May 15, 2017 at 07:14 PM

Do you mean that whenever you use the standard condition, that you should add the "+1"?

0 ·

Matthew Gillespie ♦♦ Lou Keller commented · May 15, 2017 at 07:49 PM

The default condition just says:

getsimtime() > 480 && getcensus(model) <= 1

If you're using the getthrougput() command you should keep in mind that the On Entry trigger of the Exit object happens before the throughput of the model is updated. So, I would think that in most cases you'd want to say getthroughput(model) +1 or decrement the number on the right side by one to account for that.

1 ·

Tee Hiett Matthew Gillespie ♦♦ commented · May 16, 2017 at 03:02 PM

Thanks, Matthew. I suspected this was the case when there was no On Exit Trigger on the exit object.

Tee

0 ·

question