Implementation of sectoral water usage in CESM
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- fortran
- Domain
- hpc
Research direction
Start by reviewing the affected CTSM, MOSART, CMEPS, and CESM_CPL7andDataComps repositories and the existing sectoral water abstraction implementation. Confirm how the completed modeling, testing, and validation work is intended to be deployed to the main development branch, and identify the integration steps and acceptance checks with the listed coordinators.
Written by the indexing model from the issue text.
Description
Hi!
I am a PhD researcher from VUB, Belgium (https://hydr.vub.be/people/Sabin.Taranu).
We have been working for some time now on implementing human sectoral water abstractions in the CESM model.
This includes abstractions for domestic, livestock, thermoelectric, manufacturing and mining sectors.
At the moment the modeling, as well as testing and validation, is completed. So we are ready to deploy the solution to the main development branch.
The repositories which will be affected are:
https://github.com/ESCOMP/CTSM
https://github.com/ESCOMP/MOSART
https://github.com/ESCOMP/CMEPS
https://github.com/ESCOMP/CESM_CPL7andDataComps
From NCAR, our main coordinators for this project are David Lawrence and Erik Kluzek.
Other people from NCAR who contributed to the discussions are: Sean Swenson, Naoki Mizukami, and Andrew Wood.
Outside the NCAR, the people involved or supporting this project are: Wim Thiery, Yoshihide Wada, Ting Tang, Yi Yao, Inne Vanderkelen, Steven Johan De Hertog.
For any questions, feel free to contact me at [email protected].
Best regards,
Sabin
- Dominant language
- Fortran
- Stars
- 12
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from ESCOMP/MOSART
-
MOSART does not have the `history_tape_in_use` functionalityMay be free again @slevis-lmwg claimed this 456 days ago, and no pull request is open. Openenhancement low priority
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
code cleanup enhancement low priority
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
bug 🔥 diagnostics outputs I/O
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
flux-framework/flux-coral2#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
kynema/kynema-sgf#2064 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
EMsoft-org/EMsoftOO#20 ·