[Task] Running multiple crops: Vectorization of phenology and data of AgroManagement
@fnattino is already working on this.
Since Apr 8, 2026.
- Dominant language
- Python
- Stars
- 25
- Forks
- 6
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 1
Description
The parameters IDSL, DLO, DLC, and DVSEND in the DVS_Phenology class control when the simulation should stop. Depending on their values, DVS_Phenology sends a signal to the Engine to end the simulation. These parameters are closely related to AgroManagement settings such as crop_start_date, crop_start_type, crop_end_date, crop_end_type, crop_name, and max_duration.
The main issues are:
- The
Enginecan currently run only one crop model at a time, as defined inAgroManagement. It executes the Euler loop day-by-day for a single crop. - The dispatcher can handle only a single signal from a single crop.
As a result, the existing tests loop over different datasets one crop at a time. Ideally, we want to run all crops together with one Engine instance. Achieving this will mainly require changes to the Engine, and later the phenology module should also be revisited.
Note: related pcse notebook is 04 Running PCSE in batch mode.ipynb. This include examples of running model with several agro management data using a loop. But we want to replace the loop with vectorization operations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.