Why is the distance in the pedestrian dynamics model incorrect?

[nrayon]

Checked the distance calculations in the pedestrian model, all distance calculations are being done correctly.

Probable causes for pedestrian spacing:

1. Neighbor spacing tests have too small/large of an area each iteration
2. Pedestrian propulsion is too high causing pedestrians to move too fast from iteration to iteration without checking

[rpahle]

Need to do more precise calculation incl, distance and acceleration so that the pedestrians don't get too close to each other. Need to collect information about distance and speed so that we can compare to the paper.

[rpahle]

Nearest neighbor coordinates, distance, etc. so we can see why it is not stopping them from coming too close.

[nrayon]

Added output from for pedestrian ID 123. Pedestrians are stuck in the middle of the aisle, but after iteration ~400 they continuously move back toward their seats. This output is after changing the nearest neighbor and spatial test as well as resetting pedestrian velocity to 0 when they reach a goal.

This data shows that line 13 is the last time pedestrian 123 has a nearest neighbor across from the aisle.

This happens to all aisle-row pedestrians.

Note: Uploading as a txt file, might need to change to excel in the future.

debugOutput123Cut.txt

[nrayon]

Also attaching output for the first 500 iterations as well as the visualization for a bigger picture.

debugOutput123.txt

[nrayon]

Iterations 392 401

Problem

Pedestrian Propulsion being calculated in the wrong direction

VIPRA_Pedestrian_Dynamics_Model_Output_392_401.txt

[nrayon]

Solution:

Calculate Nearest Neighbor based on the direction of their goal.

[nrayon]

Updated Calm Model to calculate the nearest neighbor in the direction of their goal.

Issues: Pedestrians sway a little in the beginning.