Framework must be able to calculate derived variables
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
For expediency when porting physics into CCPP and testing them with various host models, the framework must be able to calculate derived variables in cases where such conversions are unambiguous and reasonable to implement (this is not an open-ended task!).
For example, if potential temperature is not provided, calculate it from temperature and geopotential.
This is a post-capgen-unification task.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by locating the framework's post-capgen-unification handling for variables and the tests covering conversions; define a bounded set of unambiguous derived-variable cases, including potential temperature from temperature and geopotential, and make those cases pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100