Is Experimenter facing a problem in v2016?

Question

question

Lucas Antonio Risso asked Jun 16 2016 at 12:43 PM Lucas Antonio Risso edited Jun 24 2016 at 8:15 PM

Is Experimenter facing a problem in v2016?

I am running the Experimenter with 100 replications for 48 performance indicators, and the results are not being showed after the running, like showed in the image below. However, if I reduce the number of KPI's or the number of replications, it runs normally.

Has anyone already faced a similar situation? By any chance, is there a limit for the settings?

Please, I appreciate if you could check my model. experimenter-blank-results.fsm

Thank you for your help.

Software Version:

FlexSim 16.0.1

experimenter replications

experimenter.jpg (40.0 KiB)

experimenter-blank-results.fsm (534.3 KiB)

· 6

Marco Baccalaro commented · Jun 16 2016 at 1:22 PM

Maybe you could have some error on KPIs code like a division by zero.

1 ·

Lucas Antonio Risso Marco Baccalaro commented · Jun 16 2016 at 1:29 PM

I don't think so, because they are all standard measures, and when I set 25 replications, it runs perfectly.

0 ·

Marco Baccalaro Lucas Antonio Risso commented · Jun 16 2016 at 1:41 PM

Right. Another idea: it happened to me that the system console was growing up too much and so I had problems on big experimenters. Maybe take a look at it.

0 ·

Show more comments

Jordan Johnson ♦♦ commented · Jun 16 2016 at 8:48 PM

We have seen a similar issue that happens when you save the model with the experimenter window open. Does that sound like it applies to you?

0 ·

Lucas Antonio Risso Jordan Johnson ♦♦ commented · Jun 17 2016 at 11:38 AM

Yes, it can be the case. Maybe I have saved the model with the window open. So how do I fix this? What did you do? Thanks.

0 ·

______

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 · 2016-06-24T16:50:39Z

Phil BoBo answered Jun 24 2016 at 4:50 PM Lucas Antonio Risso edited Jun 24 2016 at 8:15 PM

Replication 35 of KPI "Products lead time - LT - CartonPACK (8) Average" has an invalid return value.

Replication 92 of KPI "Products lead time - LT - LILA (7) Average" also has an invalid value.

· 9

Lucas Antonio Risso commented · Jun 24 2016 at 5:01 PM

Thanks @michael.machado, and @phil.bobo... Phil, can you tell me how to fix the mistake that is causing the return of an invalid value?

0 ·

Phil BoBo ♦♦ Lucas Antonio Risso commented · Jun 24 2016 at 5:03 PM

I'll look into it further and let you know.

1 ·

Lucas Antonio Risso commented · Jun 24 2016 at 5:14 PM

Thank you so much... The idea for this KPI is to measure the average staytime of all the flowitems that pass by the correspondent queue, but "excluding" the staytime of the last ones that didn't leave the queue by the end of the run time... So, I used a tracked variable. If there is another way to accomplish it that is easier than fixing this logic, I would appreciate to learn. Once again thank you so much.

0 ·

Phil BoBo ♦♦ Lucas Antonio Risso commented · Jun 24 2016 at 5:30 PM

The problem is that nothing has left the queue so the tracked variable has never been set.

On the Advanced tab of the Experimenter, you can set it to repeat the random streams of a certain replication. If you set that to 35 and then reset and run your model, you will see that nothing has exited the LT Eight queue and so the LT (8) tracked variable has never been set.

You have the same problem on LT Seven in replication 92.

1 ·

Lucas Antonio Risso commented · Jun 24 2016 at 5:52 PM

If nothing leave the queue, the KPI should assume the value 0, how can I set this option? Would an "if" condition on the Trigger work?

Thank you for showing this gap.

0 ·

Phil BoBo ♦♦ Lucas Antonio Risso commented · Jun 24 2016 at 5:54 PM

Set the tracked variables to 0 in a reset trigger.

1 ·

Lucas Antonio Risso commented · Jun 24 2016 at 6:26 PM

I set the tracked variables to 0 on a reset trigger, but it is still not working.

Maybe it is needed a way to attend to the possibility of the item not leave the queue.

0 ·

Phil BoBo ♦♦ Lucas Antonio Risso commented · Jun 24 2016 at 6:38 PM

Seemed to fix it for me: 914-experimenter-blank-results-pb1.fsm

Note: I only changed LT 7 and 8 because those ones were showing issues. You should probably fix all of them.

1 ·

914-experimenter-blank-results-pb1.fsm (533.7 KiB)

Lucas Antonio Risso Phil BoBo ♦♦ commented · Jun 24 2016 at 8:15 PM

It worked. Thank you for the attention. Your answers helped me a lot.

0 ·

Answer 2 · 2016-06-16T13:30:41Z

Michael Machado answered Jun 16 2016 at 1:30 PM Ben Wilson commented Jun 24 2016 at 5:12 PM

Lucas, try with a general or demo model and see if you will still face the same problem. If so, share the demo model with us here. Thanks,

· 3

Lucas Antonio Risso commented · Jun 22 2016 at 1:14 PM

Hello everyone, this model is presenting the problem that I described above . Thank you for any help. experimenter-blank-results.fsm

0 ·

experimenter-blank-results.fsm (534.3 KiB)

Matt Long Lucas Antonio Risso commented · Jun 22 2016 at 9:03 PM

Looks like it's being finicky, though I'm not sure why. The first time I ran the experiment the results didn't display. The next time I did it seemed to work just fine. Try running the experiment and hit the View Results while the experiment is still running (and only a few replications have finished). Seems like when I did that and results displayed, the continued displaying even after I hit 100 replications.

1 ·

Michael Machado Lucas Antonio Risso commented · Jun 24 2016 at 1:38 AM

Please, @phil.bobo May you look into @Lucas Antonio Risso's model to see if that is a problem in the Experimenter? We've never saw something like that here. Thanks,

0 ·

Answer 3 · 2016-06-17T16:42:14Z

Jordan Johnson answered Jun 17 2016 at 4:42 PM

You can try closing and reopening the results window, along with the experimenter window. The results from each experiment are stored in the tree, even after you hit the "Reset Experiment" button. If you run a new experiment, those results will be replaced with results from the current experiment.

That means that you should be able to open the results window (using the "View Results" button) any time after the experiment has been run. If that still doesn't work, consider inspecting the experimenter tree (MODEL:/Tools/Experimenter), looking for anything out of the ordinary. Without a model, though, it is difficult to understand the real issue.

question