Problems with preemption

Question

question

Cetim C asked Jun 07 2022 at 10:27 AM Jason Lightfoot commented Jun 10 2022 at 2:48 PM

Problems with preemption

Hello,
I want that the operator travel to queue2 and have 40 second delay, but he will be interrupted every 10 seconds so he has to go to queue1 and come back. On return, I want the delay to be at the same point, and that is the proble, that every time he returns, the counter is reset. It is as if the save context is not running.
Attach the model.
Thanks in advance
InterruptionV2.fsm

Software Version:

FlexSim 22.1.2

preemption

interruptionv2.fsm (51.0 KiB)

· 1

______

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 · 2022-06-07T10:58:47Z

Jason Lightfoot answered Jun 07 2022 at 10:58 AM Jason Lightfoot commented Jun 07 2022 at 12:42 PM

You should not preempt tokens that are waiting for a task to complete - instead you should preempt the task executer by using a higher priority task sequence with prempt set to PREEMPT_ONLY. When that sequence is complete the task executer will resume the preempted task and fire the callback at the correct time. If you need to, insert milestone tasks in order that you repeat things like travel if needed.

· 6

Cetim C commented · Jun 07 2022 at 11:03 AM

Thank you for your reply but, sorry, I didn´t understand what you explained. I don´t understand what should I change

0 ·

Jason Lightfoot ♦♦ Cetim C commented · Jun 07 2022 at 11:24 AM

Here's the modified model.

Note that by using a milestone the preempting set of tasks doesn't need to know anything about which task is was interrupting - so does not include the travel task back to queue2. I added a small delay to indicate something is done at queue1.

Also note that the range of the milestone task is not 2, but 4 - this is to include the callback task for each task activity.

interruptionv2_jl.fsm

0 ·

interruptionv2-jl.fsm (50.6 KiB)

Cetim C Jason Lightfoot ♦♦ commented · Jun 07 2022 at 11:33 AM

Thanks for the clarification, but the problem still exists. It is like an infinite loop. Main delay progress has not been saved

0 ·

Show more comments

question