Outline fields needed by CISM from&to the coupler
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
- backend
Research direction
The issue names no files, tests, or entry points; begin by locating the CISM-to-CESM coupler interfaces and reviewing the referenced discussion with Bill L. Done requires an agreed specification for isotope fields, units, concentrations versus tendencies, and surface, basal-melt, calving, and solid-runoff exchanges.
Written by the indexing model from the issue text.
Description
Based on a conversation with Bill L yesterday, it looks like we will need to bring in an array of isotope amounts with the temperature and surface mass balance at the top of the ice sheet.
Some questions for isotope associated with surface mass balance.
- What units will isotope concentrations be passed around with?
- Will they be straight concentrations or tendencies within the fluxes?
- How will CLM handle the isotope partitioning with regards to the surface mass balance? If some isotopes are preferentially melted, will there be an isotopic tendency associated with the melt?
We may need to send isotope information out to CESM related to basal icesheet melt.
- Is there preferential isotopic melting below the ice sheets?
- Will we be sending concentrations or tendencies or both?
- How much does the ocean care about the isotopic load of basal water? Is it ok if we use ice isotopic loads?
And there should be an isotopic load associated with calving/solid run-off.
- This should just be the same isotopes as the ice that is being removed from CISM
- Dominant language
- Fortran
- Stars
- 4
- Forks
- 18
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 2
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/CISM-wrapper
-
Consider aborting with an error if the user tries to set cisminputfile in a branch runPossibly taken @billsacks claimed this 3 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ESCOMP/CISM-wrapper#152 · 1 comment ·
-
Coupler Updates for Missing AblationPossibly taken @Katetc claimed this 10 days ago. Open
ESCOMP/CISM-wrapper#151 · 1 comment · 1 assignee ·
-
ERI_Ly10.f10_f10_mg37.I1850Clm50SpG.derecho_intel.cism-isostasy_period4 Fail in cism_wrap_3.0.0May be free again @Katetc claimed this 30 days ago, and no pull request is open. Open
ESCOMP/CISM-wrapper#148 · 1 assignee ·
-
Update Externals and Tests for CESM3May be free again @Katetc claimed this 74 days ago, and no pull request is open. Open
ESCOMP/CISM-wrapper#145 · 2 comments · 1 assignee ·
-
Consistency of Isotopes in Surface Mass Balance from CLMMay be free again @Katetc claimed this 247 days ago, and no pull request is open. Open
ESCOMP/CISM-wrapper#136 · 2 comments · 1 assignee ·
All issues in ESCOMP/CISM-wrapper
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Arekkazu/sgpmp-backend#744 ·
Maintainers usually reply within 1 day
-
[Bug] Activity | The activity list ignores taskIds and returns the activities of every taskPossibly taken @NdekoCode claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ever-co/ever-gauzy#11469 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
getgrav/grav-plugin-api#66 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
home-assistant/core#188613 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100