Is it possible to get the references to the tokens reserved by a resource?

Question

question

Axel Kohonen asked Dec 12 2016 at 11:15 AM Matt Long commented Dec 22 2016 at 2:55 PM

Is it possible to get the references to the tokens reserved by a resource?

Hi,

Is it possible to get the token references of the tokens that have reserved a numeric resource somewhere else in the code? I have paired tokens and would like to create a "zone" that can be entered only if the ID of a token already in the zone matches the ID of the token now entering the zone and the token "weight" can fit into the resource reservation.

In the attached example model I look at the model tree for the resource in process flow, but I cannot figure out a way to access the tokens.

Any clue on how to do this?

Thank you!

Kind regards,

Axel

20161212-howdoigetreferncetotokensthathavereserved.fsm

Software Version:

FlexSim 16.2.1

process flow tokens reference

capture.jpg (99.3 KiB)

20161212-howdoigetreferncetotokensthathavereserved.fsm (22.3 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 · 2016-12-21T16:21:52Z

Matt Long answered Dec 21 2016 at 4:21 PM Matt Long commented Dec 22 2016 at 2:55 PM

There are reasons we removed the "Explore Tree" option from the Process Flow view. We do not recommend diving into the tree and messing with or getting data directly from the nodes. The structure is not guaranteed to always be the same. Things can get quite confusing when dealing with instances as well.

Instead, use the given commands to access tokens. If your code is in the same Process Flow as the Resource, then 'current' is the instance. To get a reference to the tokens that have acquired a Resource use the following code:

gettoken(current, "Resource", 1);
or
gettoken(current, getactivity(processFlow, "Resource"), 1);

If you're in a different Process Flow then the instance would either be:

node("Tools/ProcessFlow/ProcessFlowName", model()); //For General
or
node("Processor1", model()); //For a FR or TE

This is a lot simpler than trying to access tokens through the tree.

· 2

Axel Kohonen commented · Dec 22 2016 at 11:18 AM

Hi @Matt Long

Thank you for the comment! Your solution makes much more sense.

How would you know how many tokens there is in the resource so you know how far in the index to loop? Now I have used the stats information

getstat(resource, "Content", STAT_CURRENT);

and loop according to that. I tried to check for a NULL returned from the gettoken function when the index points to a token that does not exists, but I could not get it to work. Not sure what I did wrong. Anyhow, using stats does work, but was thinking if there would be a better solution for it.

Kind regards,

Axel

0 ·

Matt Long Axel Kohonen commented · Dec 22 2016 at 2:55 PM

It does look like there's a slight bug in the gettoken() on a Resource such that when you ask for a index beyond the number of tokens that have acquired the Resource it throws an exception. We'll get that fixed.

If you open an Assign Labels and add a label and then use the Sampler for the Value field, you can hover over the Resource and it will give you a getstat() option which looks like this:

getstat(getactivity(processFlow, "Resource"), "Output", STAT_CURRENT, current)

Notice the difference between this code and the one you posted in your comment. The last parameter, current, is a reference to the instance object. When getting stats on Process Flow objects you need to pass the instance in as well. So to get the number of tokens that have acquired it would be:

getstat(resource, "Content", STAT_CURRENT, current)

1 ·

Answer 2 · 2016-12-21T08:28:28Z

Jason Lightfoot answered Dec 21 2016 at 8:28 AM

gettoken(<processflow/instance>,<activity>,<index>)

can also be used.

Answer 3 · 2016-12-12T12:18:26Z

Axel Kohonen answered Dec 12 2016 at 12:18 PM

Hi,

Found the answer myself. The nodes inside tokens are coupling nodes and the nodes they are linked to can be found with the following "+" syntax (where firstToken is the coupling node):

var tokenTest = node("+", firstToken);

So the code to get the owner token is the following

//reference to process flow
treenode processFlow = ownerobject(activity);
 
//create reference string
string path = concat(">stats/instances/", getnodename(processFlow),"/tokens");
 
//get reference to tokens
treenode tokens = node(path, getactivity(processFlow, "Resource"));
 
//get the first token node as an example (it must exist so
//the first time we get into this code in the model it will not)
treenode firstToken = rank(tokens, 1);
 
//get the token reference from the data
var tokenTest = node("+", firstToken);
 
//the main token is the 
treenode theToken = up(up(tokenTest)); //HERE WE HAVE THE TOKEN ITSELF
 
//get label value
var labelValue = getlabel(theToken, "resource");
//get token id
int theTokenID = gettokenid(theToken);

And the model file with the same code is this

20161212-fixed-howdoigetreferncetotokensthathavere.fsm

Axel

20161212-fixed-howdoigetreferncetotokensthathavere.fsm (20.4 KiB)

question