[Discussion] New PedestrianPositionProcessor with higher time-resolution
At the moment, the time component within the output of the PedestrianPositionProcessor - typically postvis.trajectories - are limited to the time steps. That means, the resolution is idential to simTimeStepLength (typicall 0.4s). For several applications it seems useful to increase the resolution of time in this output file. For example for the 3D Visualization (OPMOPS) or UQ (Quest).
Idea: Instead of replacing PedestrianPositionProcessor (which has many dependencies), I would suggest to add a new processor in which the time of the event instead of the timesteps is noted.
Questions: Do the processors have access to the time of the events or only to the timesteps? If the latter applies, can this be changed?