GitLab

refactoring the base class for operative models

Pedestrians are now stored in a single vector.

Add more geometries to cover width range
[1.0, 1.2, 1.4, 1.6, 2.0, 2.2, 2.5]

Use Gompertz model for validation

Conflicts:
	Simulation.cpp
	Simulation.h
	mpi/LCGrid.cpp
	mpi/LCGrid.h

Conflicts:
	Simulation.cpp
	Simulation.h
	events/EventManager.cpp
	general/ArgumentParser.cpp
	general/ArgumentParser.h
	general/Macros.h
	inputfiles/events/Schule/traffic.xml
	main.cpp
	mpi/LCGrid.cpp
	mpi/LCGrid.h
	routing/GlobalRouter.cpp
	routing/GlobalRouter.h

Conflicts:
	Simulation.cpp
	Simulation.h
	events/EventManager.cpp
	general/ArgumentParser.cpp
	general/ArgumentParser.h
	general/Macros.h
	inputfiles/events/Schule/traffic.xml
	main.cpp
	mpi/LCGrid.cpp
	mpi/LCGrid.h
	routing/GlobalRouter.cpp
	routing/GlobalRouter.h

testing ...

perform 20 runs pro width

is still failing :-(

this is the bottleneck test. Only three  widths are tested. Should be enough to check if the flow increases
linearly with the width

Some debug messages are still there, since we are looking for some
ugly bugs..

Usage:

./bin/jpscore  inputfiles/Bottleneck/ini_bottleneck.xml 2>log.txt 1>log1.txt
python plot_neighbors.py log.txt the_geometry_file_used_in_the_simulation.xml

Checking visibility function and neighborhood lists

Conflicts:
	math/GompertzModel.cpp

Call with:
 if(ped->GetID()==61) building->GetGrid()->HighlightNeighborhood(ped,building);

Call with:
 if(ped->GetID()==61) building->GetGrid()->HighlightNeighborhood(ped,building);

by pedestrian 2 or pedestrian 4

- Add test 12: Test if pedestrians are influenced by other pedestrians that they not see (behind walls or Obstacles)
- Add template test directory

Try new timeout

Corrected egde factor in quickest path Router

Updated demos files

refactoring the demos files

Two commits for refactoring the test files

1. Test 7 is still failing: Router issue
2. Test 8 is strangely failing: Pedestrian banishes. What the hell?

1. Cutoff radius is only calculated for Gompertz not for GCFM
2. New trajectory format (xPos, yPos) --> (x,y).
3. move some python-functions to a separate module (utils.py) to avoid repetition