Address potential duplicate names

Open
#146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
content

Research direction

Start by investigating the usage of lwe_surface_snow and lwe_thickness_of_surface_snow to determine whether they represent a true duplicate. Then inspect the remaining standard names for similar potential duplicates; done means the identified pair and any additional findings are clearly resolved or documented.

Written by the indexing model from the issue text.

Description

On a recent PR @nusbaume pointed out a potential pair of duplicate names. We will need to investigate the exact usage of these names to determine if it is a true duplicate. I'll also plan a deeper dive to ensure there are no other similar potential duplicates hiding in the names.

Potential duplicates

  • lwe_surface_snow and lwe_thickness_of_surface_snow
Dominant language
Python
Stars
9
Forks
17
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ESCOMP/ESMStandardNames

All issues in ESCOMP/ESMStandardNames

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.