Clarification re: Model Repeatability - updatelocations()

I'm having some repeatability issues with my model that just recently started appearing, and I **think** I have isolated the potential cause to the issue described in the "Item Locations" section of the model repeatability page. I am recording times of exceptions thrown during the fast run, but I can't reproduce the same times during the slow run to troubleshoot the issues.

I wanted to get some clarity on the definition of "query to an item's location." For example, I don't necessarily ask for object.location, but I may sometimes set the destination of a walk activity to an acquired resource (or something similar) - and I feel like that could be the sort of thing I'm looking for.

What are some common places where this issue might appear?

https://docs.flexsim.com/en/23.2/BestPractices/ModelRepeatability/ModelRepeatability.html

Software Version:

FlexSim 23.2.1

· 6

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Felix Möhlmann commented · Jan 22 at 07:36 AM

In my experience this is mostly a problem when you move to objects that are currently moving themselves. Task Executers only update their location when they end (and maybe also start?) a travel task. Though that shouldn't lead to exceptions.

Do the exceptions occur in a "slow" run when you do not have the 3d model view open? And could you maybe post those exceptions (if you can't post the actual or an example model)?. It will help identifying the issue.

1 ·

Jason Lightfoot ♦♦ Felix Möhlmann commented · Jan 22 at 12:46 PM

Also the documentation in that link doesn't appear to state that custom draw code should not perform any function that the model needs in order to operate - decisions or actions - since it will not fire at all in an experiment and with a variable rate interactively (frame refresh rate).

1 ·

Chandler Jason Lightfoot ♦♦ commented · Jan 25 at 03:11 PM

Jason I think you're right. I don't think custom draw code is the issue in the experiment, but when I run trouble scenarios individually in order to try to locate where I've done something I need to revise.

0 ·

Show more comments

Chandler Felix Möhlmann commented · Jan 25 at 03:04 PM

I will try to isolate the issue and run a slow run without the model view open. I've been working on a different project for the last week so I am just getting back to this today.

Thanks for your reply.

0 ·

Jeanette F ♦♦ commented · Feb 07 at 03:15 AM

Hi @Chandler,

We haven't heard back from you. Were you able to solve your problem? If so, please add and accept an answer to let others know the solution. Or please respond to the previous comment so that we can continue to help you.

If we don't hear back in the next 3 business days, we'll assume you were able to solve your problem and we'll close this case in our tracker. You can always comment back at any time to reopen your question, or you can contact your local FlexSim distributor for phone or email help.

0 ·