Is there anyway to make the taskexecutor run one way with A*? I tried with Mandatory Path, but can't seem to make the taskexecutor run one way like capture below.
The purpose is of this is that customer want to create car traffic, and sometimes have smaller taskexecutor run the side of the other taskexecutor avoiding collision. For this purpose, I thought of using A*. I saw some youtube video replicating the traffic(https://www.youtube.com/watch?v=9enF87I6x4Q), how was this done? Network node?
Hi @Ryosuke S, was Jeanette F's or Gokulakrishnan Kandasamy's answer helpful? If so, please click the red "Accept" button on one of their answers. Or if you still have questions, add a comment and we'll continue the conversation.
If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.
@Ryosuke S by trailing @jeanette answer you can try using the network node and process flow if you want to simulate traffic model. I think your reference video is simulated by a specific process flow( travel based on assigned token label value for specific location). I tried the preferred paths with traffic nodes. Look into the model. If have any doubt let us know. We r happy to help you! agv-avoid.fsm
Hello @Ryosuke S,
Mandatory paths have to have a complete look and the task executers have a box in their properties that has to be checked to use the mandatory path. I do not think this solely will give you the outcome you are looing for.
I use preferred paths and had a better outcome of the task executers maneuvering around obstacles but still traveling clockwise.
Another option would be to use a divider but change the properties to only be one way. Then a task executer can enter a pathway only from one direction and therefor only travel one direction.
Here is a post that goes over a possible Process Flow reroute option when a task executer using A* is blocked.
@Jeanette F Thank you for your reply. Your suggestion worked perfectly. I'm a little puzzled however, because preferred works like mandatory. Just vocabulary issue.
Hello @Ryosuke S,
The mandatory path's vocabulary is fitting because when it is used the task executer cannot deviate from the path. The task executer is required to follow it.
The preferred path is used when possible but the task executer can deviate from it if necessary.
Does that help with the terminology?
Also I recently watched a video about agent systems that could be of help to you as well. At about the 36:40 mark is the content that would help your task executers know how to move around each other. The whole video is incredibly informative though and I would suggest watching all of it to know all the resources available to you in agent systems.
@Jeanette F Thanks for the Agent video. I've seen it before, but I didn't pay much attention on the path settings at the time. Thank you.
15 People are following this question.
© 1993- FlexSim Software Products, Inc. All Rights Reserved.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
