Currently, the migration database can only be read
archi.get_migrants_db()
however migrants can not be manipulated (besides implicitly by evolution).
This creates some undesirable side-effects: i.e. resetting an island population while migrants are still in the database will bump the new random population quickly to the old fitness level.
Consequently, it would be useful to have a way to manipulate the migrant database directly. Additionally, other convenient functions would be to "flush" (trigger a migration manually) and "erase" (reset the complete database, removing all migrants).
Currently, the migration database can only be read
archi.get_migrants_db()
however migrants can not be manipulated (besides implicitly by evolution). This creates some undesirable side-effects: i.e. resetting an island population while migrants are still in the database will bump the new random population quickly to the old fitness level.
Consequently, it would be useful to have a way to manipulate the migrant database directly. Additionally, other convenient functions would be to "flush" (trigger a migration manually) and "erase" (reset the complete database, removing all migrants).