question

Chris Ligetti avatar image
0 Likes"
Chris Ligetti asked Chris Ligetti answered

Clock Overflow when running Experimenter

I have a model that I regularly run the experimenter for multiple scenarios/replications. I noticed that the model runs were EXTREMELY slow, so I did a very short run just to be able to see the results (including console output). I noticed that each scenario I tried running had System Console output that looked like this:

time: 0.000000 exception: FlexSimClock overflow, run Stopped.

time: 2.070216 exception: FlexSimClock overflow, run Stopped.

time: 2.757870 exception: FlexSimClock overflow, run Stopped.

time: 3.796343 exception: FlexSimClock overflow, run Stopped.

I looked at previous post about this error, but they did not provide answers that were relevant to my model. Anybody have any ideas on what else I can look into? I am definitely NOT getting these system console errors when running the model normally through the UI.

FlexSim 18.0.7
system console error in experimenter runs
· 1
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Joshua S avatar image Joshua S commented ·

Would you be able to upload your model so we try to replicate the error and see how to solve it?

2 Likes 2 ·

1 Answer

Chris Ligetti avatar image
0 Likes"
Chris Ligetti answered

I am sorry. Figured it out. It was caused by a divide by 0 error on some MTBF logic that referenced an object label that inadvertently got set to 0 in the scenario setup. Thanks for offering to help.

5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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