How to pull 2 operators from a list, and reference operators in process flow?

Question

question

Connor M2 asked May 12 2021 at 4:57 PM Connor M2 commented May 25 2021 at 12:18 PM

How to pull 2 operators from a list, and reference operators in process flow?

I'm looking to utilize the custom processors with operators. In order to pull the operators, I'd prefer them to be pulled from a list which is parametrized. As currently set up, the token pulls two operators and stores them in an array. However, later in the process flow, the label on the token is being referenced by its first index only.

See: When the operators are pulled, only one of them travels to the processor.

Is it possible to reference task executers in a token array similar to the fashion I'm trying to currently?

Is there a better way to reference global operators that what I'm trying?

See attached.
Pulling2OperatorsFromList.fsm

Software Version:

FlexSim 21.1.2

operators flexsim 21.1.2 global list processors multiple operators

pulling2operatorsfromlist.fsm (164.7 KiB)

· 3

Joerg Vogel commented · May 12 2021 at 8:53 PM

If you need to split an array, you do it in sub flow by the array length. And if you want to keep the array you use as index “creationRank”. It is a declared variable in the source code of call sub flow. Otherwise you pop each element by the same named method.

1 ·

Connor M2 Joerg Vogel commented · May 13 2021 at 7:53 PM

Is there a way to view and edit the source code of the sub-flow? Can you explain the potential use case for the "pop" of an array?

0 ·

Ben Wilson ♦♦ commented · May 19 2021 at 2:25 AM

Hi @Connor M2, was Eric M's answer helpful? If so, please click the red "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

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.

Answer 1 · 2021-05-12T19:41:46Z

Eric M answered May 12 2021 at 7:41 PM Connor M2 commented May 25 2021 at 12:18 PM

Hi @Connor M2, the easiest way to do this is with the "synchronize" activity in process flow. You can see I've added this to the first part of your model (you may need to move the operators so they're apart before running it to see how it works). I also changed the acquire resources to only pull 1 operator and changed the resource to reference the group of operators instead of the list. You can use this same process for using two operators to move the boxes from the processor too.

There's also a great tutorial in the manual that might be nice to look at if you would like.

pulling2operatorsfromlist_EM.fsm

pulling2operatorsfromlist-em.fsm (168.5 KiB)

· 3

Connor M2 commented · May 13 2021 at 7:50 PM

Hi Eric! Thanks for the prompt response. This does indeed accomplish the use case for two operators working together. However, I'd like to be a little more flexible with my operator calling by task.

You see, I'm referencing an external excel file which is imported to a global table in my model. I'm then referencing that table to set operator requirements and task delay times. In the model you created, I don't see how it could be flexible in such a way. See attached for something that is a little closer to what I'm actually working with. Pulling2OperatorsFromListGlobalTable.fsm

Additionally, as I understand it, aren't "resource" shared assets treated as simplified lists on the back end? What is the difference between the settings I can control on lists vs. the ones that are already set and controlled on "resource" blocks?

I think if I could figure out a way to either reference multiple indices at the same time, or assign two labels to a token from one "pull from list", that would send me in the right direction.

0 ·

pulling2operatorsfromlistglobaltable.fsm (165.0 KiB)

Jason Lightfoot ♦♦ Connor M2 commented · May 14 2021 at 12:24 AM

You should use a subflow to assign the 'operator' label to each token it created based on the array size and then reference the operator in the task activities.

Model

Model attached.pulling2operatorsfromlistglobaltable_jl.fsm

1 ·

1620951847556.png (39.2 KiB)

pulling2operatorsfromlistglobaltable-jl.fsm (167.6 KiB)

Connor M2 Jason Lightfoot ♦♦ commented · May 25 2021 at 12:18 PM

This is a great solution! I've implemented it and it seems to be working quite well. I appreciate the prompt responses!

0 ·

question