The input-output counts of the doors don't count correctly.

Question

question

Patrick Cloutier asked Jan 08 2019 at 9:09 PM Jordan Johnson commented Jan 10 2019 at 7:52 PM

The input-output counts of the doors don't count correctly.

Look at attached model, click on a door and look at the stats as people go through the doors.

When someone goes out, the input goes up by 1. But when someone goes in the input and output go up by 1.

error-with-input-output-of-doors.fsm

Software Version:

FlexSim 18.2.2

people module door stats

error-with-input-output-of-doors.fsm (240.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 · 2019-01-08T21:43:58Z

Joshua S answered Jan 08 2019 at 9:43 PM Jordan Johnson commented Jan 10 2019 at 7:52 PM

Anytime a person is created at a door, it will always register as an input and output, because a person is created at that object and will be assigned a subnode of that object which registers as an input. Then when it releases the person to go to the other door, then it registers that as an output. It's the same if you created an object in a processor through process flow.

· 2

Patrick Cloutier commented · Jan 09 2019 at 7:07 PM

This is not very logical. It is an unusable stat. Is there any way to measure in-out without counting what is created in the door? What else would a door be used for besides creating and deleting people?

And why doesn't it count the destroyobject when they exit as an output?

0 ·

Jordan Johnson ♦♦ Patrick Cloutier commented · Jan 10 2019 at 7:52 PM

A door is a Location, just like an exam table or a waiting room. If you create an object in any Location, the Input of that location increments. Fixed Resources also have this behavior.

Because it's just a location, it can be used in many more contexts than just as a source or a sink. You can use it as a travel destination at any point in the process. Perhaps people travel to a certain door, and when they arrive, decide where to go next. The door in that case is neither a source nor a sink, but just a destination.

None of the objects in FlexSim count an object's destruction as an Output. Sinks, for example, do not increment their output variable when they destroy flowitems or tokens. The item simply vanishes.

If you want, you can use a different door as the exit. Then the 3D object statistics will happen to reflect your model statistics.

The more correct way gather model statistics is to use the Statistics Collector. You can listen to the OnExit of the Create Person activity, and listen to the OnEntry of the Destroy Object, and then increment and decrement a number based on those events. Then it won't matter if there are 0, 1, 2, or 1000 doors in your model, or if any of those doors are actually entrances, exits, or just travel destinations. If you listen to objects by requirement, you can listen to all CreatePerson and RemovePerson activities, which means it won't matter how many CreatePerson or RemovePerson activities you have in the model either.

The goal for People Module is to include many statistics collectors that collect data this way by default. For now, however, you will have to create those kind of collectors on your own.

1 ·

question