06 - Copy.fsmI am not able to simulate this model for 3-4 weeks.
Model simulation run slow on max runtime and hangs
FlexSim 20.2.3
Hi @AMIT KUMAR, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.
If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.
You have a lot of instances where you needlessly send tokens around a loop up to a hundred times a second.
One example is the subflow for the operator breaks. As long as nothing can be acquired, the tokens loop around constantly due to the Max Wait Time setting.
That setting is meant for cases where you want to have logic in the form of (Try to acquire X, if unsuccessful, do something else). There is no "do something else" here, the token can only continue to the activities below "Breaks Logic" once it acquired an operator. So using a Max Wait Time doesn't make sense in this case. You can just use a single activity and have the token wait until it acquired an operator.
As I said there are multiple instances of this in your model, some with Acquires/Resource and some with Pull from Lists/Lists. Example for a case with a list is shown below.
A similar thing happens at different points where the tokens constantly checks a value in a global table. Instead you should do the check and if the value is not "correct" yet, have the token wait until an event that (possibly) changes this value happens. Depending on where this value is set, this could a token exiting a certain activity or an item in the 3d model being moved in/out of a certain object.
14 People are following this question.
