Change constituent properties parsed from standard name?
Open
Nobody has claimed this yet.
enhancement
post-capgen-unification
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Description
DISCUSSION SOLICITED
The following constituent properties are currently parsed from the standard name:
- volume mixing ratio vs mass mixing ratio vs. number_concentration -> parsed from standard name and saved to properties%const_type
- moist vs wet vs dry -> parsed from standard name and saved to properties%const_water
Alternative options
Do we want a different approach to one or both of these long-term?
- const_type could be determined by units - not necessarily auto-converted
- const_water could be an additional metadata field (like advected); would function the same, but standard name would not include _wrt_dry_air, etc.
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
Start by locating the standard-name parsing path and the code that populates properties%const_type and properties%const_water. Review how units and metadata fields are represented, then resolve which alternative the project wants; done means an agreed approach is documented and its impact on these properties and standard names is addressed.
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