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

Question

question

Tee Hiett asked May 13 2017 at 6:56 PM Tee Hiett commented May 16 2017 at 3:02 PM

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)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

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

Matthew Gillespie answered May 15 2017 at 6:49 PM Tee Hiett commented May 16 2017 at 3:02 PM

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 7: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 7: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 3:02 PM

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

Tee

0 ·

question