GitLab

+ Add local analysing/knowledge (without visualisation currently)
~ Fixed some bugs in central analysing which were introduced when converting DRAS to a standalone service.
+ Add README explaining how DRAS works

~ Integrate crater specific TimeoutMap into original TimeoutMap.
~ Fix usages of crater specific TimeoutMap in CRATER to use the original TimeoutMap.
- Delete crater specific TimeoutMaps and corresponding interfaces from monitoring.crater and monitoring.clientserver
- Delete TimeoutCollections-Package in Peerfact, as there are no usages and the package is a duplicate of the Overlay TimeoutCollections

+ Add TimeoutPairedList
~ Change to usage of this list, because otherwise there could only be one noUMTSLocation per Node, which isn't realistic.

+ Make some options configurable via XML
+ Add OSM-Visualization for Social Movement

+ Disaster Regions can now be analyzed and visualized in a centralized way. All data is uploaded to the cloud and passed on to the analyzer.

+ Cells can be killed/shutdown by using the setConnectivity method on a FiveGTopologyDatabase entry.
+ Add visualisation for "dead" cells
+ Cells can be killed and resurrected by clicking on them in the visualisation.

actually changed.

implemented by all netlayers
updates MaxPeerCountChurnGenerator to support the interface (default
behavior still triggers the network-layer functions)

Fixed minor error in PositionVector for Lat = Y and Long = X.



See merge request !29

JSON Placement for OSM Data

Added a Placement Model for Hosts that takes OSM Input data for real map placement of e.g. infrastructure entities such as AccessPoints at "attraction point" locations.

See merge request !28

fix transition strategy to only fire once an Attraction Point is reached
remove POI limitation for Json-based Attraction Points

(used for #cloudlet-evaluation)

to enable easy filtering for postprocessing without relying on host IDs

enabled direct instantiation of custom attraction points in the XML
config

Merge nr/master-debug into master

Added MaxPeerCountChurnGenerator. A churn model what follows a predefined "trace" that states how many nodes should be in the network. Nodes may be used for multiple times, thus overlays have to ensure to handle such events. The csv file must highlight the time when a churn should start, the length of the churn (used to calculate the inter arrival rate of nodes), and the number of nodes that is to be achieved. 

See merge request !26

Fixed stupid bug in 5G-StaticDB configuration



See merge request !27

Merge master into nr/master-debug



See merge request !25