question

Gavin Douglas asked Jun 07 2017 at 6:44 PM Anna Lisa Dierking commented Aug 23 2017 at 12:52 PM

resource release?

I want six tokens to grab six resource and then get batched into one token. No problem so far. At some point in the model, the single token, needs to pass back six resources, not just one. I know its just one token now but can you release six resources based on one token? I have tried everything. Being able to track the number of resources that make up a batch and then release that number comes up in every model I write. I have hacked my around the problem and hope there is a clean way of doing this.

Software Version:

FlexSim 17.1.2

resource release

· 3

Kari Payton commented · Jun 07 2017 at 8:13 PM

Have you tried using synchronize and join tools instead of batching? @Gavin Douglas

0 ·

Matthew Gillespie ♦♦ commented · Jun 07 2017 at 9:02 PM

You can set the # of Tokens to release on the Batch to be equal to the Batch Quantity. That way the batch doesn't destroy any tokens and each token can release it's own resource.

0 ·

Gina Lasure Matthew Gillespie ♦♦ commented · Jun 16 2017 at 8:20 PM

I have some follow-up questions on this -

In my experience, releasing the batch quantity to retain resource information only works if you're releasing the same quantity that was collected in that specific activity.

I'd like to be able to have 10 items (each using 1 resource) be batched into a single token, run through several other activities as one token, and then be unbatched into 10 individual tokens again. It's easy to split the tokens back up, but I've never been able to correctly carry the resources through so they can be properly returned. 9 of them always go missing.

Is there a way to do this that I'm missing? Obviously you can get around it with code, but it would be easier if I didn't have to.

0 ·

Anna Lisa Dierking answered Aug 23 2017 at 8:59 AM Anna Lisa Dierking commented Aug 23 2017 at 12:52 PM

I had the same issue recently.

In the attached example model each token acquires one resource. After that four tokens get batched to one token. I used the Label Aggergation to store the resource information of each token onto the token that is going to leave the batch activity.

Then I used the "Release All" function to release all the resources now stored on that one token. But the problem is that only one resource gets released. Is the "Release All" function not the right one to make this happen?

release-all.png (12.4 KiB)

release-all.fsm (19.7 KiB)

· 2

Steven Hamoen commented · Aug 23 2017 at 10:25 AM

@Anna Lisa Dierking If you put a delay after the batch and step through your model you will see that when the 3 tokens are destroyed in the batch, the 3 resources are already released. So apparently destroying a token automatically releases the resource. You could release the batch amount and store all but one in a list. When the last one is ready to release you pull all the tokens from the list and releasing every resource that way.

0 ·

Anna Lisa Dierking Steven Hamoen commented · Aug 23 2017 at 12:52 PM

For some reason, I missed that. Thanks for pointing that out. Unfortunately, the resources seem to be released but can't be acquired again. If you step further you will see that only the fifth token can acquire a resource and the sixth token (and so on) can only send a request.

0 ·

______

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.