Skip to content

Flee 3.0
Compare
Choose a tag to compare
@djgroen djgroen released this 14 Jul 16:39
· 345 commits to master since this release
v3.0
4e27454

This is the release of Flee 3.0.

Major new features

  • New format for defining simulation settings (simsettings.yml).
  • Support for custom-based location-specific and link-specific properties.
  • Support for demographic attributes on agents.
  • Addition of four new demographics-based move rules.
  • Support for conflict-driven spawning, where new displaced persons are spawned based on conflict intensity, rather than provided in advance by the user.
  • Large revisions and extensions to https://flee.readthedocs.io
  • Hugely extended logging infrastructure, allowing logs for individual agent movements, individual links, and counting the number of hops.

Minor new features

  • Added support for the idpcamp location type, which can be opened or closed.
  • Added support to load agents in advance from an agents.csv file.
  • Added support for remove_forced_redirection.
  • Added support for sink locations, which deactivate agents when agents reside there.
  • Added support for delayed camp openings.
  • Added support for link-dependent MaxMoveSpeeds.
  • The conflict property of a location is no longer a binary values, but a float with which intensity can be varied by changing its value.
  • Added support for a foreign_weight parameter for foreign locations, separately from camp_weight
  • Added YYYY-MM-DD date information to out.csv, to make parsing easier.

Bugfixes

  • Removed several bugs from the Burundi conflict example in FabFlee.
  • Revised the path selection algorithm for higher awareness levels, such that routes are pre-planned more sensibly.
  • Default camp capacities are changed from 0 to unlimited.
  • Refactored the source code altogether, making it more modular and easier to debug.
  • Removed a range of obsolete and/or unused functions.
  • Rephrased "refugees" to "displaced persons" in output and plotting infrastructure.
  • Fixed a wide range of test cases and added several new unit tests to improve code reliability.

Note that unlike previous versions, Flee 3 will be subject to regular incremental releases and updates, as we foresee the need to implement a range of new mechanisms and move rules during the lifetime of this version.

Lastly, note that Flee 3.0 can only be used with FabFlee 3.0 or higher. It is backwards compatible with the Flee 2.0 input files, but the simsetting.yml will need to be defined and added.

Assets 2
Loading