how to pull a specific taskexecuter from a resource

Question

question

Pedro Veiga asked Nov 12, '24 Pedro Veiga commented Nov 12, '24

how to pull a specific taskexecuter from a resource

Hi,

I have 11 taskexecuters at the same resource, but I'd like to pull them based on a label that counts from 1 to 11, and with that number as a reference, pull the specific taskexecuter with that value.

Thanks in advance,

Pedro

Software Version:

FlexSim 24.0.5

acquire resource

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Answer 1 · 2024-11-12T14:20:18Z

Joerg Vogel answered Nov 12, '24 Pedro Veiga commented Nov 12, '24

query_labeled_resource.fsm

query-label-resource.jpg (202.1 KiB)

query-labeled-resource.fsm (63.1 KiB)

· 3

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Pedro Veiga commented · Nov 12 at 03:00 PM

Hi, @Joerg, I tried to use your exemple, but my issue is that the value that I want to use comes from a random statistical distribution. Therefore I need to add this random value to the operators labels.

I took your example and tried to adapt into what I need but didn't managed it.

query-labeled-resource.fsm

0 ·

1731423387042.png (122.6 KiB)

query-labeled-resource.fsm (67.1 KiB)

Joerg Vogel Pedro Veiga commented · Nov 12 at 03:36 PM

@Pedro Veiga, assigning a token label twice with different datatype can work but it is not recommended. You did it from number to treenode. I choose a different value for comparison. A String. List entries are accessed by value keyword. On your Resource list the entries are treenodes. you can get a field value by an expression, too. My token label is an abreviation of your composed treenode reference.
Puller is a keyword to get access to the element that is responsible to initiate a pull from a resource list.

acquire_random_name.fsm

1 ·

acquire-by-composed-random-name.jpg (136.9 KiB)

Pedro Veiga Joerg Vogel commented · Nov 12 at 04:51 PM

Thank you @Joerg, it worked as intended.

0 ·

question