Is it necessary to work on system console exceptions to get right results?

Question

question

Ankur A3 asked Oct 6, '23 Jason Lightfoot edited Oct 13, '23

Is it necessary to work on system console exceptions to get right results?

Hi team,

I am getting some exception in system console window and I know the reasons. My question is if we don't work on it, can we rely on model results:

Exceptions:

1. I am collecting results from global table using calculated tables to be shown while running optimizer.

Calaculated tables are updated at interval of 60 min but also while reset by default. Since global table is not having any row at t=0, it is throwing exception as below:

time: 0.000000 exception: Exception caught in Executive::processeventinlist()

2. Another one is related to negative sample value from distribution

createvent: event time is in past: event time changed to present. Object: Processor advancetime: -0.088730, time: 0.546016 line1

Thank you!

Software Version:

FlexSim 23.1.0

exception system console

· 2

Claire Krupp commented · Oct 06, 2023 at 07:23 PM

@Ankur A3 @Jason Lightfoot the negative sample value has been happening to me too recently in a model that I'm SURE does not have any negative samples. (Uniform(8,10)). This MTTR/MTBF table has been in the model for at least 2 months and did not throw any exceptions until recently. Probably when we upgraded to 23.1.3.

I'll post a question on it the next time I see it occur. (seems to be intermittent.)

0 ·

Jason Lightfoot ♦ Claire Krupp commented · Oct 07, 2023 at 12:38 PM

As you know Claire this should be impossible - we'd be very interested to understand what is going on with that case.

0 ·

Answer 1 · 2023-10-06T13:03:12Z

Jason Lightfoot answered Oct 6, '23 Jason Lightfoot edited Oct 13, '23

I'm sure not all exception messages are of equal importance. However they are equally important in how they are perceived - if you don't rectify them all , then users get in the habit of ignoring exception messages and can often then miss ones that are then critical/important to having valid results. Also it's an indication that a user is not paying attention to the way that the model and FlexSim work and/or that they understand valid parameter values. Neither of these things are hard to fix, so the benefit in doing so easily outweighs the time it takes to make the correction.

If you have a model full of exceptions and then need support on that model, we will always try to clear the exceptions first so that we have a clear vision of the remaining issue if it's generating exceptions (or have you fix them), which may delay getting to the issues about which you are posting.

I recommend you fix all of them all of the time.

· 2

Jason Lightfoot ♦ commented · Oct 07, 2023 at 12:36 PM

Additional note: We sometimes see models where the window system has failed to display/open/bring to the front, the system console when exceptions occur, which means it is possible to miss problems in models.

Because of this I'd recommend as a habit always working with the system console open and always checking it is empty. With that habit you're more likely to notice if it is missing. If the console is then missing and not opening from the debug menu, reload the default workspace which will usually allow it to then open.

0 ·

Ankur A3 Jason Lightfoot ♦ commented · Oct 13, 2023 at 01:04 PM

Thank you @Jason Lightfoot

Got your point.

0 ·

question