Add more metadata to the aerosol deposition climatology files
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by locating the code that creates the monthly climatology datasets, then read how it receives args and builds merged_ds.attrs. Compare the existing ozone_strataero and NDEP metadata with the requested attributes, noting that the Description value is not specified. Done means the monthly climatology datasets include the applicable requested metadata.
Written by the indexing model from the issue text.
Description
There's some additional metadata on the ozone_strataero datasets and NDEP datasets from CAM-Chem that would be good to add to the monthly climatology datasets we are creating.
It looks like useful; metadata that we should add are:
merged_ds.attrs["User"] = args.user merged_ds.attrs["Email"] = args.email merged_ds.attrs["Lab"] = args.lab merged_ds.attrs["cycleYear"] = args.cycleYear merged_ds.attrs["firstYear"] = args.firstYear merged_ds.attrs["lastYear"] = args.lastYear merged_ds.attrs["Description"]And from looking at the NDEP file, metadata that could be added:
:mip_era = "CMIP7" ; :contact = "Michaela Hegglin ([email protected]); Douglas Kinnison ([email protected]); Xiaodan Ma ([email protected]); Olaf Stein ([email protected])" ; :dataset_category = "surfaceFluxes" ; :grid = "2px2p5 degree latitude x longitude" ; :grid_label = "gn" ; :grid_resolution = "2px2p5 degree" ; :nominal_resolution = "250 km" ; :realm = "atmos" ;
Originally posted by @ekluzek in #4285
- Dominant language
- Fortran
- Stars
- 362
- Forks
- 372
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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/CTSM
-
b4b code health next
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ESCOMP/CTSM#4330 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue next size: small test: python usability
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
b4b next size: small
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Remove ARSLu and ESLgS from the list of available PLUMBER2 sites displayed by running run_tower --helpPossibly taken @samsrabin claimed this 8 days ago. Openb4b good first issue priority: low usability
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ESCOMP/CTSM#4313 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
b4b usability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
core good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
[dbt] exported dataset keys reference physical columnsPossibly taken @WilliamKelley claimed this today. Openneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/ossie-converters#251 ·
Maintainers usually reply within 2 days
-
data difficulty: medium enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
lab P3 tooling
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100