ImperialCollegeLondon / ImperialCollegeLondon/virtual_ecosystem
M1.1.2 Define update order in the daily loop
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 5
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 34
Description
Summary
Define the daily execution sequence for snow, radiation, energy balance, melt, and hydrologic routing.
Purpose
Ensure that snow mass and energy interact with the existing model in a consistent and reproducible order.
Tasks
- Define the daily sequence for processes defined in #1700
- Identify whether the energy balance is solved once per day, per daylight period, or using representative subdaily conditions.
- Document where effective albedo enters the radiation code.
- Document what other surface properties change when snow cover is present.
- Provide either an ordered bullet list or a simple flow diagram.
Acceptance criteria
- A documented update sequence exists.
- There is no ambiguity about whether snow albedo is updated before or after energy-balance calculations.
- The update order for snowfall, albedo refresh, melt, and SWE update is documented.
- The insertion point of hydrologic routing is documented.
Suggested tests
- Walk through one synthetic snowy day and one snow-free day using the documented order to confirm that the sequence is physically consistent.
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.
Research direction
Start by reading issue #1700 and tracing the existing daily loop. Walk through one synthetic snowy day and one snow-free day, checking the ordering of snowfall, albedo refresh, energy balance, melt, SWE updates, and hydrologic routing. Done means an ordered list or flow diagram removes ambiguity about each insertion point and update dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100