Run process flow on model reset

Question

question

Axel Kohonen asked Apr 11 2017 at 7:01 AM Matt Long commented Apr 12 2017 at 1:55 PM

Run process flow on model reset

Hi,

I would like to initialize my model by running a Process flow on model reset. Is this possible somehow?

It works nicely when I run the process flow at time zero, but then the user cannot see what happens at reset until he runs the model.

I tried calling createtoken in the onModelReset trigger and it creates a token into the process flow. But immediately as the onModelReset code ends the token disappears. See the attached executeprocessflowonmodelreset-170.fsm model.

Any hints on how/if this can be achieved?

Thank you!

Kind regards,

Axel

Software Version:

FlexSim 17.0.3

process flow onmodelreset

executeprocessflowonmodelreset-170.fsm (15.5 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 · 2017-04-11T22:06:29Z

Matt Long answered Apr 11 2017 at 10:06 PM Matt Long commented Apr 12 2017 at 1:55 PM

Do not run Process Flow on reset.

We specifically removed the OnReset event from Event-Triggered Source as it can cause serious issues having tokens in your model at reset.

If you choose to do so, you do so at your own risk.

· 2

Axel Kohonen commented · Apr 12 2017 at 3:50 AM

Hi @Matt Long

Thank you for that information!

How is it then generally with creating operators/timetables after reset? Is it a bad idea? I previously created operators and timetables in the onModelReset code using custom coding and it worked nicely, but it would be easier and more clear to use process flow. At least one problem that I get when creating operators after reset is that I have to manually open the input of the operators or else they will not receive tasks. Also, when generating operators after reset their FlexScript nodes are not built either. I did not see any difference due to them not being built, but I build them just to make sure.

If it does not cause problems to create operators & timetables after reset at time zero then find the attached and simplified solution executeprocessflowonmodelreset-170-runmodelshortti.fsm to my problem where I use a normal process flow that starts at time zero to create a box. To make it look like the box is created at reset I add

//set stoptime
stoptime(0.01);
//start simulation
go();

to the end of the onModelReset trigger. So practically I run the model a little bit forward (the time can be made very short) from model reset. In some cases this might not be desirable, but in most models it is ok to do.

But is this a good approach?

Thank you!

Kind regards,

Axel

1 ·

executeprocessflowonmodelreset-170-runmodelshortti.fsm (15.4 KiB)

Matt Long Axel Kohonen commented · Apr 12 2017 at 1:55 PM

The issue really comes down to having tokens in your model at reset. I don't know if we ever discovered why it creates such problems, but it does. Haven't played around much with having a token be created at reset and destroyed before reset is finished (completing all of it's logic in one stack).

But the general rule would be to perform whatever logic and create whatever objects you need to at time 0. This can easily be accomplished by using a Scheduled Source that creates one token at time 0. You can use Create Object activities to create your Operators, or of course you can tie an Operator to a Resource and then up its resource count to copy the operator.

As for setting the stop time, that would definitely work as well. You could even make that number smaller if needed.

0 ·

Answer 2 · 2017-04-11T07:33:47Z

Mischa Spelt answered Apr 11 2017 at 7:33 AM

If your process flow is "instantaneous", _i.e._ doesn't have activities like Delay, you could try calling executesubflow from the Model Reset trigger. However this is probably not the intended use of executesubflows and a there are probably a thousand ways that this may break.

· 2

Axel Kohonen commented · Apr 11 2017 at 7:54 AM

Hi @Mischa Spelt,

I actually got it to work with executesubflow. The problem was that I had "Destroy Objects" activities in the process flow with the asynchronous setting on. This causes a zero second delay due to which the executesubflow did not work.

However, the solution is not perfect, as one cannot debug it with process flow. But I can of course debug it first with a normal Schedule source and when it works I can change it to run with executesubflow.

Is it even possible to run a process flow with delays on model reset? It seems that everything on reset has to happen in zero time for it to be on reset. Am I right?

And I am still curios about why the createtoken approach does not work. I would be happy if someone can answer that.

Thank you!

Axel

0 ·

Sam Stubbs ♦ Axel Kohonen commented · Apr 11 2017 at 3:27 PM

From what I understand, just creating a token will place the token in the Process Flow, but there is nothing telling the Process Flow to execute. Process Flow will run if the model is running, but if the model is stopped, the Process Flow is stopped as well. (That's why you can "step" through Process Flow Activities)

As Mischa showed, if you call the executesubflow command, that command specifically tells the Process Flow to execute.

1 ·

question