Read domain data directly from geo_em file
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 2
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 1
Description
It is often inconvenient to have to provide a namelist text file to update the fire fields. All of the information needed to add NFUEL_CAT (fuel category) and ZSF (terrain) fields for the fire domain is contained within the geo_em.dXX.nc file, so we should add the option to read the information directly from there
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 Python entry point that currently reads the namelist text file and inspect how NFUEL_CAT and ZSF are written to the fire domain. Use a geo_em.dXX.nc file as input and verify that both fields can be obtained without a namelist; done means the fire fields are populated correctly from the domain data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100