Chimera
Chimera simulates the spread of ideas within a population.
Installation
pip install zf-chimera
Usage
$ chimera --help
usage: chimera [-h] [--population POPULATION] [--start START] [--infected INFECTED] [--radius RADIUS] [--spread SPREAD] [--steps STEPS]
Simulate the diffusion of innovations
options:
-h, --help show this help message and exit
--population POPULATION
The population size of the society
--model MODEL The model to use (e.g. v1, v2)
--start START The style of the simulation (e.g. middle, random)
--infected INFECTED The number of initially infected (e.g. 1, 10)
--radius RADIUS The geographic radius of each agent (e.g. 5, 10)
--spread SPREAD The number of agents each agent will infect (e.g. 2, 7)
--steps STEPS The number of steps to simulate (e.g. 50, 100)
$ chimera
Running simulation for 50 steps with 3481 agents
Parameters
You can control the simulation by changing parameter which will affect the spread of the idea.
Transmission Rate
The transmission rate is the probability that an agent will be infected by another agent.
The argument name is --rate and its default value is set to 0.5.
For the following tables, the initial infected is set to 1 while varying the transmission rate.
Rate = 0.3 |
Rate = 0.5 |
Rate = 1.0 |
Initial Infected
The initial infected is the number of agents that will be infected at the start of the simulation.
The argument name is --infected and its default value is set to 1.
For the following examples, the transmission rate is set to 0.5 while varying the initial infected.
Infected = 1 |
Infected = 3 |
Infected = 5 |
Geographic Radius
The geographic radius is the distance that an agent can transmit the idea to another agent.
For the following examples, both the transmission rate and initial infected are set to 1 while varying the geographic radius.
Radius = 1 |
Radius = 3 |
Radius = 5 |
Questions
- How many friends does a person have?
- How many people does a person talk to?
- When do people act upon some information?
- How to model hierarchies and groups?
- How to model lateral communication?
References
Metadata
Release files for zf-chimera 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zf-chimera-0.0.2.tar.gz | 9.6 kB | Without provenance | Details for zf-chimera-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zf_chimera-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for zf_chimera-0.0.2-py3-none-any.whl |
Total release size: 19.4 kB
Release files / zf-chimera-0.0.2.tar.gz
| Download URL | zf-chimera-0.0.2.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d5e54cfb7f148de9c73c3d2cd71f733496f5f1f33dbf5657a70d91e093c0bd88
|
|
BLAKE2b-256 checksum How to use checksums |
c1ab974a80ed42e06a7aa6cb08b61d5fdfb5c90a3d266d7a8a0929eab7be4a7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Release files / zf_chimera-0.0.2-py3-none-any.whl
| Download URL | zf_chimera-0.0.2-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f20c1c0c623ee87651117d70c91effdb2f79c068412a1200d64a6991f90feac
|
|
BLAKE2b-256 checksum How to use checksums |
2b217876bd12ab5cfb83b8c1c5ac121014cbac347ecd310217da9495020617c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Security for zf-chimera 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.