Bioturbation Model
A simple model of earthworm bioturbation, using a layered soil profile. The model predicts the mixing of mass pools (e.g. of contaminants) over time as a function of earthworm density.
Quickstart
The model can be installed using pip:
$ pip install bioturbation
Alternatively, you can download the source code and use the provided Conda environment file to install the relevant dependencies:
$ git clone https://github.com/samharrison7/bioturbation-model.git
$ cd bioturbation-model
$ conda env create -f environment.yml
Usage
Check out the examples directory for examples of how to use the model.
Conceptualisation
See the conceptualisation notebook for a mathematical description of how the model works.
Limitations
No guarantee is given as the to scientific validity of this model for your data. The onus is on the user to verify this validity. Indeed, there are a number of limitations to the model as it stands which might limit its applicability:
- Transport is only between adjacent soil layers, therefore neglecting preferential flow pathways, e.g. representing deep burrowing earthworms transporting tracers directly from upper to lower layers.
- No change in soil properties due to bioturbation is modelled. That is, there is an implicit assumption that the amount of soil mixed between layers is negligible. This assumption might not always be valid.
We welcome requests for collaboration if you are interested in exploring the validity of the model for your own research. Please get in touch.
Metadata
Release files for bioturbation 1.0.1
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 |
|---|---|---|---|---|
| bioturbation-1.0.1.tar.gz | 4.5 kB | Without provenance | Details for bioturbation-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bioturbation-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for bioturbation-1.0.1-py3-none-any.whl |
Total release size: 9.6 kB
Release files / bioturbation-1.0.1.tar.gz
| Download URL | bioturbation-1.0.1.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4359c5b1c18d745437bcbbe7a318f0000851529e494dd7654911fe97c2ececcc
|
|
BLAKE2b-256 checksum How to use checksums |
94fb84f4cb416b5834db672038670c98845a4762ceeb57e59e7a3a5a8ec47a1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.25.1 requests-toolbelt/0.9.1 urllib3/1.26.3 tqdm/4.63.0 importlib-metadata/3.7.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.7.10
|
Release files / bioturbation-1.0.1-py3-none-any.whl
| Download URL | bioturbation-1.0.1-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
270a79ceaca494f8f0bdd9508a82df8ef50a934ffe698469ff0f48b27abe1d93
|
|
BLAKE2b-256 checksum How to use checksums |
babc2e2a98df1037bf25090b3de86e58687f4e6273763037407ff0ed6c142f71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.25.1 requests-toolbelt/0.9.1 urllib3/1.26.3 tqdm/4.63.0 importlib-metadata/3.7.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.7.10
|
Security for bioturbation 1.0.1
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.