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

Question

question

Patrick Cloutier asked Jan 8, '19 Jordan Johnson commented Jan 10, '19

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)

Answer 1 · 2019-01-08T21:43:58Z

Joshua S answered Jan 8, '19 Jordan Johnson commented Jan 10, '19

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 07: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 07: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