question

Haneen A avatar image
0 Likes"
Haneen A asked Ben Wilson commented

Flexsim not responding with large input

our model stops and crashes at the same time each run when we enter 32 or more passengers.

why does this happen? our experiments will have way more than 32 passengers.

your help is really appreciated.

Thank you,


finaal-jl.fsm

FlexSim 20.2.0
processflowconveyorsflexsim 20.2.0photoeye
capture.png (1.5 MiB)
finaal-jl.fsm (4.5 MiB)
· 1
5 |100000

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

Ben Wilson avatar image Ben Wilson ♦♦ commented ·

Hi @Haneen A, was Phil BoBo's answer helpful? If so, please click the red "Accept" button at the bottom of their answer. 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.

0 Likes 0 ·

1 Answer

Phil BoBo avatar image
1 Like"
Phil BoBo answered

The reason your model is so slow that it seems to have crashed is because your A* Navigator grid is humongous. It is much larger than your model and your grid node spacing is set to 0.1.

Below is an image of your grid with the node spacing changed from 0.1 to 10. This grid has 29,108 nodes; yours has 291,084,032 nodes.

When a person wants to travel from one position to another, it has to calculate a path through that entire grid. Because your grid has 300 million nodes, that calculation takes a long time.

To speed up your model, you should make your grid as small as possible. You should also change the node spacing to the size of the travelers that move on it. Each node should represent the space that one traveler takes up on the grid. For your model, 1 would probably be more appropriate than 0.1, and then you will have 100 times fewer grid nodes. You should also use barriers and dividers to block out nodes that travelers do not travel on. Then they won't check those nodes when trying to calculate a path.

Additionally, you should turn on Cache Paths so that travelers do not need to recalculate paths that have already been calculated.

Also, your model throws tons of errors when you run it. You should fix the logic in your model to not throw errors.

finaal-jl_2.fsm


1614098721022.png (118.0 KiB)
1614099216187.png (764.4 KiB)
finaal-jl-2.fsm (4.5 MiB)
5 |100000

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