How to use statistics collector to record token label value in onEntry activity?

Question

question

shanice.c asked Nov 07 2021 at 3:16 PM Connor A commented Nov 12 2021 at 7:16 PM

How to use statistics collector to record token label value in onEntry activity?

I have written model.time to two different token labels, and I hope I could write down the token label value when token on entry each activity, at the same time calculate the time between start and ends in third column. I test another example from this forum, I found that there's no problem if the value I'm recording in statistics collector is a label value. Now I try to record the time information, then there's red triangle on left top of a cell, may I ask what this means?

test collect token time.fsm

Software Version:

FlexSim 21.2.0

statistics collector

test-collect-token-time.fsm (595.5 KiB)

· 2

______

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-11-08T08:01:07Z

Felix Möhlmann answered Nov 08 2021 at 8:01 AM Felix Möhlmann commented Nov 08 2021 at 3:16 PM

The data you are trying to read doesn't exist (yet), that's why you are seeing empty cells with the red mark in the corner. Because you listen to the entry event of the assign activities, the labels you are creating in them don't exist yet, when the statistics collector is triggered.

Instead of assigning the time to label values, you can get the current model time with "Model.time" and assign that value to the cell in the collector.

You also probably want to use a "Row Value". By defining "data.token" as row value, the collector will first check whether a row already exists for that value (the token). If that's the case, no new row will get created, instead the existing one will get updated.

test-collect-token-time_1.fsm

test-collect-token-time-1.fsm (593.3 KiB)

· 2

shanice.c commented · Nov 08 2021 at 1:01 PM

@Felix Möhlmann Thank you for the example, May I ask how does it know it is the timing to record time if it doesn't check "specify which columns to update" in "starttime"?

is it defaulted to update every columns if not checking anything? In your model, the on second on entry event has checked last two columns(offtime, flowtime), so it seems these 2 columns update at the same time.

I also like to ask how to write down the label value using enumerate, if I have several task executers, I want to write down labels value of each TE every time the value has changed. If still using listen to object event, the column is updated instead of keeping add new rows. I went through the manual, it could write data.token.labelname in the "Row Add Value". What's the mistake I make so that the doesn't exist.

test-collect-token-time_2.fsm

0 ·

1636371795094.png (54.0 KiB)

1636376408804.png (45.8 KiB)

test-collect-token-time-2.fsm (608.6 KiB)

Felix Möhlmann shanice.c commented · Nov 08 2021 at 3:16 PM

The first event "Assign start - On Entry" doesn't update any values. It creates the row and sets the values of the first two columns to the values specified in "Row Add Value". The last two columns are then later filled in by the second event. These are marked to be updated in that event. When a value is "updated" the "Event Value" field is used rather than the "Row Add Value" field.

The "Enumerate" event creates a row for each listed object on model reset. Since the selected objects are task executers it has nothing to do with any tokens, so "data.token" doesn't lead anywhere. Where in the manual was this used?

When using enumerated rows you can only access them from events that occur on that same object, so in this case the task executers.

Attached is an example where I listen to the load and unload triggers of the TEs. As such I assign the count label to the TEs (current), not the tokens.

Also, in your model you use both a dispatcher and an instanced process flow to control the task executers. I'd highly advise against mixing 3D- and process flow logic like this. In this case it leads to an error very early, when both task executers try to transport the same item.

test-collect-token-time-2_1.fsm

0 ·

test-collect-token-time-2-1.fsm (611.4 KiB)

question