WUR-AI / WUR-AI/diffWOFOST

[Task] Running multiple crops: Vectorization of phenology and data of AgroManagement

Open
#60 2 comments 0 reactions 1 assignee View on GitHub

@fnattino is already working on this.

Since Apr 8, 2026.

technical
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 Engine can currently run only one crop model at a time, as defined in AgroManagement. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.