question

Tee Hiett avatar image
0 Likes"
Tee Hiett asked Tee Hiett edited

What is the preferred method for fast forwarding FlexSimHC?

In debugging models, I frequently need to fast-forward to a time just before a problem is introduced in the model, stop the model, reduce the Run Speed and examine the activities. There seems to be 2 ways to do this: one is to use the Simulation End Time on the Control Bar and the 2nd is to add the Set Model Stop Time in Minutes clock to the Toolbar and put the stop time in there. The first method is the simplest but I was wondering if there is any difference in these 2 methods?

Thanks,

Tee

FlexSim HC 5.3.4
healthcaredebuggingstop timemodel run timefast-forward
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.

1 Answer

Cliff King avatar image
2 Likes"
Cliff King answered Tee Hiett commented

I'm assuming the method 1 you are referring to is this:

and method 2 you are referring to is this:

which for those who don't know can be added to your toolbar using File > Global Preferences like this:

. If you know the time you want to stop in day:hour:minute format, then method 1 is quicker and more direct. By the way, you can use decimal minutes in this format if you want, so 03:09:31.56 is allowable and means day 3, 9th hour, and 31.56 minutes.

If you want to stop at a particular time reported by the System Console in minutes, then method 2 is the way to go because you can copy the time from the System Console directly into the Set Stop Time window and when you hit OK, it will convert it into dd:hh:mm format and fill out the "Clock time for end of simulation" field for you automatically. The two windows are tied together!

I like to copy all but the last couple of decimal places from the reported error time, paste it into the Set Stop Time window, hit OK, reset and run the model at Max speed up to the new stop time, then open the Debug > Event List window and look for the scheduled event that matches the reported error time exactly. It should be the next event or two to happen in the list, so it will be up at the top of the Event List window. Hopefully, there is some useful information associated with the troubling event that I can use to figure out the problem, or at least the object/patient in the model that the event will occur on.


2018-05-03-10-41-51.jpg (24.1 KiB)
2018-05-03-10-41-08.jpg (53.8 KiB)
2018-05-03-10-42-35.jpg (88.4 KiB)
· 2
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.

Cliff King avatar image Cliff King commented ·

Oh by the way, with the recent improvements to the Debug > Object Tracker window, it's my "go to" place for help in debugging a model. There's very useful information in there about the patients in your model. If you click on one of the patients listed, the 3D view will position the patient in the center of the view and select it. Then you can also click the "Patient Track" link at the top of the Object Tracker window to get even more information about the patient you clicked on!!

0 Likes 0 ·
Tee Hiett avatar image Tee Hiett Cliff King commented ·

Cliff,

Thanks for that very helpful information, especially the reference to the Object Tracker window.

I also wanted to mention that I frequently copy the time in the dd:hh:mm format from the Activity Table and paste it into the Clock Time for End of Simulation. This process for getting a stop time just before a problem helps me identify the problem.

Tee

0 Likes 0 ·