time: 15.279353 exception: TaskExecuter1 has run into TaskExecuter3 on an accumulating path. This is not allowed.
In this exception, would like to understand why deadlock trigger has not triggered
time: 15.279353 exception: TaskExecuter1 has run into TaskExecuter3 on an accumulating path. This is not allowed.
In this exception, would like to understand why deadlock trigger has not triggered
As Jordan pointed out to me in this post, acculumation should not be used with two-way paths. In this case, the accumulation error you are seeing causes the Task Executer 1 to stop its travel before the deadlock would happen. Due to this, the TE is not trying to allocated the CP currently held Task Executer 3 and the resulting situation is not a deadlock cycle.
If you set the paths to have no accumulation, the deadlock reroute will trigger, but since Task Executer 1 is surrounded by two other TEs at that point, it can't find an alternate path to the destination.
14 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
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.
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © Autodesk Inc. All rights reserved