question

Tomi Kosunen avatar image
0 Likes"
Tomi Kosunen asked Jason Lightfoot commented

Proximity agent system does not fire

Hi. I have been testing the proximity agent system. My plan is to use it like a photo eye traffic calculator in a AStar model. In most of the cases it seems to work ok but in some cases I don't understand, why the logic doesn't fire (as there is a collision between objects). My guess is that it is somehow connected to the Operator walking too close to the wall. Is there

Pls take a look and run the model attached.

Q1: If the operator moves the pallet to Sink1, why only "TrafficLine3" fires (why TrafficLine1 and TrafficLine2 does not)?

Q2:If the operator moves the pallet to Sink2 (change connection), all the TrafficLines fire ok.

Q3: I have set a Labels to Operator and TrafficLines to calculate the number of enters and exits. Why the Operator's Entry ad Exit logic fires twice as often as the TrafficLines (while TrafficLine gets one entry/exit per operator crossing, the Operator gets two. Except while the operator is returning from Sink2, then it gets only one hit per line).

Q4: Is the proximity agent system reliable enough to be used for the statistics collection or is it only for visualisation purposes?

test_aStar_Agent.fsm

FlexSim 20.2.3
flexsim 20.2.3proximity agent system
test-astar-agent.fsm (37.0 KiB)
· 1
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Jason Lightfoot avatar image Jason Lightfoot ♦♦ commented ·

Hi @tomi.kosunen, was jason.lightfoot'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

Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Jason Lightfoot commented

The proximity is evaluates as a radius from the centre point of the agent object and you can see in the first cases the operator walks around the circle drawn for the traffic line.

test-astar-agent_jl.fsmIn the attached model I've added the code to change the color of the neighbor.


operatorwalksaroundneigborsradius.png (77.8 KiB)
test-astar-agent-jl.fsm (37.7 KiB)
· 4
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Tomi Kosunen avatar image Tomi Kosunen commented ·

Thanks @jason.lightfoot . While I tested the model, I noticed that the Operator actually fires the proximity logic but the Traffic line does not. That's why your edition of the model seems to work (as you use the Operators neighbour to set the colour etc.). My next question is, why the Operator fires and the Traffic line does not fire the proximity logic even they have the same setup? Sometimes both fire - then I would hit twice and potentially get wrong statistics.

0 Likes 0 ·
Jason Lightfoot avatar image Jason Lightfoot ♦♦ Tomi Kosunen commented ·
Each object evaluates if other members within the radius shown. As you can see in the picture, the operator is not inside the radius of the traffic line, so its logic does not fire.
0 Likes 0 ·
Tomi Kosunen avatar image Tomi Kosunen Jason Lightfoot ♦♦ commented ·

Yes, you are right. Thanks. Now I got it. Just one more: Why the proximity entry fires twice, while the operator crosses the Traffic line? (At 2.60 and 3.20 sec.) You can add line "print(Model.time,":",myName,"-",neighbor.object.name);" to the proximity entry to see it.

0 Likes 0 ·
Show more comments