Sometimes a model isn't repeatable. This can be due to a variety of factors. See the article below:
https://answers.flexsim.com/articles/21666/model-repeatability-15.html
The debugging steps in that article are still valid for smaller models. This article applies to large (millions or billions of events) and made in 24.0 or later.
The first step is to run the model twice, changing the log file each time.
- Set the log file to FFLog.sqlite or similar. Enable logging, reset, and Fast Forward to the stop time. Close the Event Log window for better performance.
- Set the log file to DrawLog.sqlite or similar. Enable logging, reset, and run to the stop time. Be sure that the 3D view is open and drawing. Close the Event Log for better performance.
Normally, after running the model, you'd export the data to a CSV file and use a diff tool. For large event logs, this becomes impractical.
Instead, you can use the attached python script, which visits each row of both logs looking for a difference in time. If there is a difference, it reports the changed event and the previous five events for both logs. This is significantly faster than doing a full diff.
Once you know the time of the changed event, you can view the full event info in FlexSim. This is the first clue to why the model is not repeatable. The changed event is a symptom of some other issue. At this point, you need to discover why the event is different. For example, if an AGV arrives at a location at a different time, look at where the AGV was travelling, and see if you can see a reason that the time for the arrival would be different.
