about stop time and statistic

Hi, in the attached is a very simple model to test statistic.

I set stop time to 4, but the model stop at time 3. I think maybe it is because there's no event after 3. But I want to compute the average queue length based on run time 4. The queue's statistic and the recorder's statistic are based on run time 3. How to resolve this problem?

I tried to put another source into the model and let it generate an item at time 4, then the recorder can give correct average queue length but the queue still cannot. Is there a better solution?

I tested the flexsim model, and find that eventhough you set the stop time in the experimenter, the model may stop before that time because there is no event left.

But in my model, some performance metrics are based on stop time, for example, queue average length. Can someone help me resolve this problem?

thanks

Hello,

create a user event at runtime 4. The code can be anything ,e.g. print the current time in the output console.

The function is in Tools > User Events

Jörg

Originally Posted by Jörg Vogel

Hello,

create a user event at runtime 4. The code can be anything ,e.g. print the current time in the output console.

The function is in Tools > User Events

Jörg

Dear Jorg, thank you. But the queue still cannot report correct average queue length. Correct value should be 2.5, while it reports 2 based on run time 4.

The stats updates only if an item enters over leaves the object (p.e.: You can see this if you take a look into the stats "State" of a processor during simulation.)

If you want to update the stats at a specific moment, you can add "updatestates()" in your user event. This command is also called if you push the stop button.

Greetings

Carsten

Dear, Carsten, Thank for your help.
I build a user event to update stats, but the queue object still cannot report correct avg length, the record can report correct value. I am confused.
Please see the attachment. Please set the stop time to 4.01.

The objects update their content stats when items enter or leave.

For 6.0.2, we have added functionality so that content stats are also updated when you stop the model or call updatestates().

We plan to release 6.0.2 tomorrow if all goes well. We're doing some final testing on the install before we release.