Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[0.14.0]

Loading configuration from template definitions in the yaml, in preparation for SALib support. The definition of the variables and their possible values (i.e., a problem in SALib terms), as well as a sampler function, can be provided. Soil uses this definition and the template to generate a set of configurations.
Simulation group names, to link related simulations. For now, they are only used to group all simulations in the same group under the same folder.

dir_path is now the directory for resources (modules, files), and the output dir has been renamed to outdir

Modules with custom agents/environments failed to load when they were run from outside the directory of the definition file. Modules are now loaded from the directory of the simulation file in addition to the working directory

get_agents and count_agents methods now accept lists as inputs. They can be used to retrieve agents from node ids
subgraph in BaseAgent
agents.select method, to filter out agents
skip_test property in yaml definitions, to force skipping some examples
agents.Geo, with a search function based on postition
BaseAgent.ego_search to get nodes from the ego network of a node
BaseAgent.degree and BaseAgent.betweenness

History now defaults to not backing up! This makes it more intuitive to load the history for examination, at the expense of rewriting something. That should not happen because History is only created in the Environment, and that has backup=True.

Agent names are assigned based on their agent types
Agent logging uses the agent name.
FSM agents can now return a timeout in addition to a new state. e.g. return self.idle, self.env.timeout(2) will execute the different_state in 2 units of time (t_step=now+2).
Example of using timeouts in FSM (custom_timeouts)
network_agents entries may include an ids entry. If set, it should be a list of node ids that should be assigned that agent type. This complements the previous behavior of setting agent type with weights.