search

JuPedSim / jpsreport

Analysis tool
https://www.jupedsim.org/jpsreport_introduction.html
Other
3 stars 9 forks source link

Method A with varying FPS #114

Closed chraibi closed 5 years ago

chraibi commented 5 years ago

In Gitlab by @chraibi on Jan 19, 2016, 16:30 [origin]

When using Method A with varying FPS, the data extraction seems not to work.

failed attempts for resolving:

a very basic example is attached. The problem occurs at <measurement_area id="3" /> report_fehler.rar

chraibi commented 5 years ago

In Gitlab by @chraibi on Dec 17, 2016, 08:20

Original comment by b.schroeder on 29 Jan 2016, 12:15

could you reproduce the error?

chraibi commented 5 years ago

In Gitlab by @chraibi on Dec 17, 2016, 08:20

Original comment by zhang on 29 Jan 2016, 16:18

@schroederbenjamin Please to be sure that there is trajectory information at both side of the measurement line. Otherwise, Method A does not work, because it is not possible to check whether the person go out or not. When the fps is small, the trajectory information will be not so fine. The distance between two neighboring position will be larger. there will be no trajectory information at the other side of measurement line. This could be the reason!

chraibi commented 5 years ago

In Gitlab by @chraibi on Dec 17, 2016, 08:20

Original comment by zhang on 29 Jan 2016, 16:20

you can let pedestrian move a little bit more behind the exit to check it again. @schroederbenjamin

chraibi commented 5 years ago

In Gitlab by @chraibi on Dec 17, 2016, 08:20

Original comment by chraibi on 30 Jan 2016, 00:52

Should jpsreport give a warning in this case?

chraibi commented 5 years ago

In Gitlab by @chraibi on Dec 17, 2016, 08:20

Original comment by b.schroeder on 30 Jan 2016, 16:16

as I already have said, we repositioned the measurement line a couple of meters towards the centre of the room - no success. Did you check the supplied example?

chraibi commented 5 years ago

In Gitlab by @chraibi on Dec 17, 2016, 08:20

Original comment by zhang on 31 Jan 2016, 13:48

I see, the poisition of the measurement line with id 3 is y=7.05. which is 16cm to the exit (y=7.21). If you check the trajectory file, you can find not all pedestrians' last y coordinates are larger than 7.05. for example, the agent with ID=21 left the room at frame 8. His last position is y=7.00 at frame 7. @schroederbenjamin

chraibi commented 5 years ago

In Gitlab by @chraibi on Feb 21, 2017, 13:56

Please consider to extend the geometry such that ALL pedestrians are ensured to leave the geometry.

chraibi commented 5 years ago

In Gitlab by @chraibi on Feb 21, 2017, 13:56

closed