A*Navigator stuck on calculating path

Question

question

Paula LG asked Jul 29 2024 at 2:40 PM Sam Stubbs commented Aug 01 2024 at 3:21 PM

A*Navigator stuck on calculating path

Hi,

I've recently noticed an unusual behavior while developing some models.

I have a certain amount of task executers (defined by a Delete and Copy Group Members parameter). When the simulation starts, I create a dummy transporter for each task executer and make them travel between 2 stations in a loop. These dummy transporters are added to a group called "Dummies", and every object that belongs to that group is destroyed On Model Reset.

There's a moment during the simulation where the model gets stuck. If we then start recording with the performance profiler, we can see that the A*Navigator is stuck trying to calculate a path. No error pops up, it just can't run any further.

I have developed a dummy model to replicate the issue I encountered: 24.1 Dummy AStarNavigator stuck.fsm

We have also tried to run it in 24.2 Beta and the exact same thing happened.

Thank you in advance!

Software Version:

FlexSim 24.1.1

bug report astar navigator

241-dummy-astarnavigator-stuck.fsm (42.9 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2024-07-31T17:22:27Z

Sam Stubbs answered Jul 31 2024 at 5:22 PM Sam Stubbs commented Aug 01 2024 at 3:21 PM

Deadlock management is a tricky issue to resolve in AStar. The problem is that you have groups of taskexecuters running between two locations back and forth in a straight line, and they are all crowding at those two locations. With that much overlapping traffic, and collision detection, it's no wonder there is deadlocking going on.

My recommendation is to use preferred paths to create in and out drop off and pick up routes around your queues (like you'd probably use in real life). It also helps to add your locations to the AStar navigator as well. Create a flow that helps space out and direct your travelers so they aren't all overlapping with each other.

Here's a version of your model using the preferred path method.

241-dummy-astarnavigator-stuck_2.fsm

241-dummy-astarnavigator-stuck-2.fsm (48.0 KiB)

· 2

Paula LG commented · Aug 01 2024 at 11:06 AM

Hi Sam,

Thank you for taking the time to explore the issue I presented on this post. The routing I had on the original model was more complex than a simple straight line between two stations; however, it is true that a lot of transporters had to follow the same route. When I first noticed it happened, I tried using preferred paths as you just suggested, but it kept happening. If I run the model you attached for a long time, I get a deadlock error that FlexSim is able to identify, as opposed to what I initially reported.

I understand that this kind of crowded routing can easily lead to traffic problems, but I reported it as a bug because FlexSim doesn't detect it as an error, no message window pops up and no error is registered on the console.

1 ·

Sam Stubbs ♦ Paula LG commented · Aug 01 2024 at 3:21 PM

Yeah the behavior of getting stuck without reporting a deadlock does seem like an unintended response (or lack of response) from FlexSim.

1 ·

Answer 2 · 2024-07-29T16:54:08Z

Jason Lightfoot answered Jul 29 2024 at 4:54 PM Paula LG commented Jul 30 2024 at 7:00 AM

I would try adding a deallocation time offset (e.g. 0.5 secs) which seems to resolve the issue.

· 1

question