Label assignment/match value problem

Question

question

shanice.c asked Oct 31 2021 at 2:56 AM Felix Möhlmann commented Nov 01 2021 at 7:19 AM

Label assignment/match value problem

In "match", token will keep going through following activity only when the value of token label is same as the text in yellow area. What filled in yellow field is the parameter that is being reference.

In "assign", it will assign the involved parameter value to the token's label value. Ex: when on entry a Queue, the token is assigned the flow item's label value. So my understand is the "involved parameter value" is also what filled in yellow area.

I have used above two operations before, But in "match value" description, it says it will match the "involved parameter value" to "the value in the Label Name or Value column". Until here, I'm confused if I misunderstand the description literally means, and found less example model that use match value operation in this forum. May I ask what's "involved parameter value" means? When is the occasion to use "match value"? Thank you!

Software Version:

FlexSim 21.2.0

match value

1635647542626.png (117.5 KiB)

1635647833139.png (18.4 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 · 2021-10-31T10:22:46Z

Joerg Vogel answered Oct 31 2021 at 10:22 AM Felix Möhlmann commented Nov 01 2021 at 7:19 AM

An item object is entering a queue. For a better understanding I call it now iObj and any other items, which can possibly entering, are called part.

iObj is a reference to itself.
token.item is a label with a value as reference to on existing item in the scope of your model.
If the references of iObj and token.item matches the token will leave the activity, otherwise it will stay until a part is entering the queue. The involved parameter is item as the name of the label of token.item. It is here just the name and you may have called it differently. So you would compare your name of your label with iObj.

If there is a match, then you need not to assign iObj to for example token.item, because it exists already.

· 2

Joerg Vogel commented · Oct 31 2021 at 11:05 AM

In cases when there is a difference to the meaning of “item” as a direct pointer name or label name and a reference to the object flowitem, it would have been nice to call the label at tokens in process flow tutorials and templates differently like “part”.

It is very confusing, if you assign item to token.item. The value you assign labels to is evaluating a source code snippet template in the background. This source code snippet has got a header with a declaration of some variables. Those are often current and item. It looks like they are functions or commands, but in fact they are just names for declared variables. And in edit fields you parse the declared variable name into the label you want assign a value for.
Most confusing is today, there had been a command in the past of FlexSim which was named item.

Sometimes it is not clever to overload names with different meanings, if someone want to learn a new scripting language.

0 ·

Felix Möhlmann Joerg Vogel commented · Nov 01 2021 at 7:19 AM

To add to the answer:

"match" compares the event data (Entering Item or Input Port) to the value of the given label on the token and only reacts if the values match.

"match value" on the other hand compares it directly to the value you entered in the "Label Name or Value" field. It's used if the value you want to match is static.

Let's take the example of a queue with multiple inputs. An activity should only react to an item entering through a specific input. In that case, you'd choose "match value" and write the rank of that input port in the "Input Port" field. So, if you enter "1", the activity would only react to items entering through the first port.

0 ·

question