PHISHES seeks to bridge the gap between soil health data and actions, providing much-needed predictive capability in terms of the consequences of actions on the provision of soil functions and associated ecosystem services, taking into account soil use, soil contamination and various drivers such as climate change.
This repository hosts Python tooling and notebooks that support the PHISHES simulation platform. It includes:
- Data download and preprocessing utilities for model forcing data
- A Plant Growth Module (PGM) workflow for generating DFS2 maps
- Reproducible project structures, logging, and analysis helpers
Most user-facing workflows are provided as Jupyter notebooks in the module folders.
- Windows, Linux, or macOS
- Python x64 3.10 - 3.13
Installations are handled per sub-project. See the module README files for setup steps:
- Module-specific documentation:
- Repository design: REPOSITORY_DESIGN.md
Generates spatially distributed DFS2 maps for DHI’s ECO Lab Plant Growth Module using land-use data and species parameters.
- Location: plant-growth-module/
- Documentation: plant-growth-module/README.md
Provides scripts and notebooks for dataset organization, downloads, and reproducible project structure setup.
- Location: data-download-tool/
- Documentation: data-download-tool/README.md
phishes-pdp/
├── README.md
├── REPOSITORY_DESIGN.md
├── SECURITY.md
├── .github/
├── images/
├── data-download-tool/
└── plant-growth-module/
- Repository-level design: REPOSITORY_DESIGN.md
- Module technical details:
Version: 1.0 Last Updated: February 9, 2026 Contact: PHISHES Research Team
This repository has branch protection rules enabled to ensure code quality and security.
- Direct pushes to
mainare not allowed - All changes must go through pull requests
- Pull requests require approval from code owners
- All CI/CD checks must pass before merging
- Create a new branch from
main - Make your changes
- Open a pull request
- Wait for code owner approval and CI checks to pass
- Merge after approval
Code reviews are required from designated code owners (defined in .github/CODEOWNERS).
Note for administrators: Before enabling branch protection with code owner requirements, ensure the team or users referenced in the CODEOWNERS file exist and have appropriate permissions.
- Security Policy - Security guidelines and vulnerability reporting
- Branch Protection Guide - Configuration instructions for administrators
For more information, see our Security Policy.