How to choose travel network path for a taskexecuter

Question

question

Mario García López asked Jul 12, '24 jc commented Jul 17, '24

How to choose travel network path for a taskexecuter

I have a travel network node system in which the taskexecuter goes through the wrong path, I want to choose the correct path that I want. How can I do this?

Software Version:

FlexSim 24.1.0

network nodes travel networks nodes

Answer 1 · 2024-07-15T14:02:50Z

jc answered Jul 15, '24 jc commented Jul 17, '24

Hi, @Mario García López!
I am not sure if this is what you wanted but I changed the "on arrival" code of your node to this:

if (traveler == Model.find("TaskExecuter1") && fromedge == 1) {

return 2;

} else if (traveler == Model.find("TaskExecuter2") && fromedge == 1) {

treenode newDestination = Model.find("NN11");

redirectnetworktraveler(traveler,newDestination);

return 3;

}

I think it works as you wanted it to work but if you have any concern please let us know.
path.fsm

path.fsm (32.2 KiB)

· 2

Mario García López commented · Jul 16 at 01:39 PM

It actually worked! Thank you so much. One more thing if possible... The second taskexecuter starts its work when there are more than one box in the queu. If there are only one, the first taskexecuter returns to get the box, even if the distance is much longer than the other taskexecuter.

How can I make sure that the taskexecuter in charge of the task is the one closest to the next task?

All the best.

0 ·

jc Mario García López commented · Jul 17 at 07:16 AM

Hi, @Mario García López

In the dispatcher options you can explore different options for instance ths one:

"Shortest distance if available"

0 ·

1721200509585.png (33.0 KiB)

Answer 2 · 2024-07-12T14:15:14Z

Joerg Vogel answered Jul 12, '24 Mario García López commented Jul 12, '24

You can edit path option to be not connected. A network node has a connections (edge) to another. You can disconnect it by code or by attribute variable.

alternatively you can add travel tasks to networknodes by which a taskexecuter must go to reach a station. While reaching a destination of a Tasksequence next task will be evaluated to plan next destination by shortest distance. So you don’t need all network nodes being a destination but a few or only one to divert a taskexecuter.

· 2

Jason Lightfoot ♦♦ commented · Jul 12 at 02:24 PM

You can also return the output connection/edge number you want the traveller to take in the Network Node's OnArrival trigger to encourage it to take a different route.

1 ·

Mario García López Jason Lightfoot ♦♦ commented · Jul 12 at 03:11 PM

Thanks! I think it should be the best solution, but i am not able to get it done. Moreover i would like that each of the task executers choose the output and go through different path

Could you help me? Path.fsm

0 ·

path.fsm (33.7 KiB)

question