question

Raul V3 avatar image
0 Likes"
Raul V3 asked Natalie White commented

Pull from task executors list labor utilization

Hello Team,

  • Could you please let me know what is the correct way to use "pull from task executor list" due when we use in "Pick Operator" option we saw that state is not "processing" and one example please?
    • Maybe is a bug,but please let me know
  • Could you please let me know what is the correct way to use "Pull from Task Executer list" in Send to port option and one example please?


Thanks in advance for the support.

Bug.fsm

FlexSimBugs.pdf

FlexSim 20.1.2
flexsim 20.1.2pull from task executors list
bug.fsm (52.7 KiB)
flexsimbugs.pdf (835.5 KiB)
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

1 Answer

tannerp avatar image
1 Like"
tannerp answered Julie Weller commented

@Raul V3,

1) For your first question, I'm not sure whether the operator is supposed to show his state as "Utilized" or "Processing" by default. You could probably set up a manual state change to do this if needed. What I found is that if you leave the operators on the TE list after pulling, their utilization is tracked on the list as shown in the image below:

If you need the operators to be utilized, you might consider using a different method, such as a dispatcher, to call the operators.

2) To answer your second question: the Send To Port logic still works despite the error that you pointed out, but I do think it might be time to update that in the code. @phil.bobo @Jordan Johnson @Matthew Gillespie, is there a need to change the "Pull from Task Executer List" code?

It looks like you have the Pull from Task Executer List working correctly in your model, but is there a different example you were hoping to see? I'm attaching my updated version of your model here:

bug_1.fsm


op-utilization.png (5.6 KiB)
bug-1.fsm (223.9 KiB)
· 6
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Raul V3 avatar image Raul V3 commented ·

Hi Tanner,

Thanks for the prompt response.

For question 2 ill wait the feedback that you mention and let me add more details to question 1:


  • If I use the "normal" pick Operator option using "current.centerObject [1] " once I have the state "processing" in the processor at the same time the labor change the state to "Utilize"


  • If I use the "Pull from task executors list" to pick the Operator once I have the state "processing" in the processor the Operator have the state "travel empty". I mean the state don't change from "travel empty" to "utilize" like in the above example, so I think that the state need to be "Utilize" as well , right? can you please let me know if i used properly the "Pull from task executors list".

0 Likes 0 ·
processingusingcenterconnection.png (224.7 KiB)
travelempty.png (192.4 KiB)
tannerp avatar image tannerp Raul V3 commented ·

You're using the "Pull from Task Executers List" correctly. The problem is just that the operator is not changing his state like you want. We can manually trigger a state change and delay (process time) as shown in the code here:

This will cause the operator to be "utilized" for the duration of the processor's process time. Hopefully this solves the issues with states you're facing.

bug-1_1.fsm

2 Likes 2 ·
add-delay-task.png (56.8 KiB)
bug-1-1.fsm (53.2 KiB)
Raul V3 avatar image Raul V3 tannerp commented ·

Hi Tanner,

Thanks for the answer the above help me to resolve my original issue.. and let me make a short summary and please correct me if I'm wrong:


  • Question 1: I think that is needed to change or modify the code for further releases due I don't know why we use the "Pull from task executors list" if is not graphed properly
  • Question 2: is a bug and this would modified to maybe next releases?


Really appreciate your previous answers and waiting for the conclusion comment.


0 Likes 0 ·
Show more comments
Show more comments