Replace null values of a Milestone Collector with simulation run end time

Question

question

Joe asked Feb 24 2025 at 2:51 PM Joe answered Feb 25 2025 at 1:07 PM

Replace null values of a Milestone Collector with simulation run end time

I was wondering if it is possible to replace 'null' values within a Milestone Collector via it's properties? I am collecting the time an operating room is occupied between 7:20AM and 3PM using milestones in my patient flow. If a patient is still in the operating room at 3PM, I would like the null value to read 3PM for the calculations I do on this milestone collector. Below are the screen shots from my Milestone Collector, its output, and the patient flow.

Software Version:

FlexSim 25.0.0

statistic collector milestone collector

1740405726620.png (156.9 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2025-02-25T07:31:59Z

Felix Möhlmann answered Feb 25 2025 at 7:31 AM Felix Möhlmann edited Feb 25 2025 at 12:50 PM

You could write code into a user event (or use other means to have it execute just before the stop time) that loops through the table and replaces any null values with the current model datetime.

fill-in-stats-collector-example.fsm

(Note that rows and columns are 0-indexed when accessing the table through the bundle commands.)

fill-in-stats-collector-example.fsm (38.4 KiB)

· 2

Joe commented · Feb 25 2025 at 12:09 PM

Hi Felix. Thank you for the response. When I added the user event I am seeing some interesting results. If I put in 600 as the 'First Time Event' I do not get any of the nulls filled in. If I change it to 559.99 most of the nulls are completed but not with the 3PM end time it replaces them with 2:19PM. Also the last null is not replaced. Is there an error in my code?

0 ·

1740485057662.png (128.7 KiB)

1740485264060.png (117.4 KiB)

Felix Möhlmann Joe commented · Feb 25 2025 at 12:33 PM

In the first case, the event only fires after the stop. In my model I actually used 3599.999 because of this, but the interface rounds this to 3600.

So you had the right idea. But I guess you were thinking in the hh:mm format when choosing the other value by accident (5:59 != 559). That is also why the last row is not filled in. It was created after the event fired. And .99 represents 59.4 seconds which will get rounded to 59 in the code.

If you use 599.999 it should work. Again the interface will display 600 but the original value is still there. If you want, you can increase the number of decimals displayed in the Model Settings.

0 ·

capture1.png (3.5 KiB)

Answer 2 · 2025-02-25T13:07:48Z

Joe answered Feb 25 2025 at 1:07 PM

Thank you so much! Working well!

question