topic Re: Multiple Teams - Set State of First Operator Until Other Operators Available in FlexSim Forum

Multiple Teams - Set State of First Operator Until Other Operators Available

nicholas_d — Wed, 24 Mar 2021 22:24:51 GMT

[ FlexSim 21.0.3 ]

I have a model in which the processor uses multiple teams as a dispatcher. When the first operator arrives, the state of that operator is automatically set to Utilize (even if the other operators needed are not available yet). Is there any way to change the state of this operator during this "waiting for other operators duration"?

Re: Multiple Teams - Set State of First Operator Until Other Operators Available

nicholas_d — Thu, 25 Mar 2021 14:33:22 GMT

@Logan Gold I apologize for the urgent request, but this is a time-sensitive matter. Is there any chance you can get back to me sometime today on this?

Re: Multiple Teams - Set State of First Operator Until Other Operators Available

joerg_vogel_HsH — Thu, 25 Mar 2021 20:01:09 GMT

If you explore the tree of the taskexecuter (eg, operator), you will find a ongoing coordinated tasksequence in activetasksequence node. Herein you have a utilizetask. A utilizetask can set a taskexecuter in any state. Currently the state is STATE_UTILIZE or 22 (list of states). If you want to set a different state then you have to exchange the state parameter, when the taskexecuter receives the tasksequence in the utilize task. (OnReceive event or trigger). You will identify the tasksequence and cast a pointer to the class TaskSequence, if the receiving tasksequence is still a treenode. Then you set a pointer in the tasksequence by their task rank in the tasks array to get access to the task. Var1 is responsible of the state the taskexecuter gets into, when the utilize gets executed.

Re: Multiple Teams - Set State of First Operator Until Other Operators Available

jason_lightfoot_adsk — Thu, 25 Mar 2021 20:31:15 GMT

To do this we need to take control of all the operator requests by creating task sequences in code.

How long do we have?

Re: Multiple Teams - Set State of First Operator Until Other Operators Available

nicholas_d — Thu, 25 Mar 2021 20:41:34 GMT

@jason.lightfoot I was able to figure out an effective way to get this done. When the operator receives the task sequence a message is sent to the corresponding processor that sets the operator as a label on the processor. The processor then has an OnSetupFinish trigger (both operators must be available) that sets the state of the operator to Busy rather than Utilize. I can then track the operator utilization by only considering the duration in which the operator is in the Busy state.

Re: Multiple Teams - Set State of First Operator Until Other Operators Available

jason_lightfoot_adsk — Thu, 25 Mar 2021 20:43:25 GMT

Okay thanks for the update. I'll still try and post a task sequence method here for future reference.