Skip to content

Conversation

@jvegreg
Copy link
Contributor

@jvegreg jvegreg commented Mar 9, 2020

Before you start, please read CONTRIBUTING.md.

Tasks

  • Create an issue to discuss what you are going to do, if you haven't done so already (and add the link at the bottom)
  • This pull request has a descriptive title that can be used in a changelog
  • Add unit tests
  • Public functions should have a numpy-style docstring so they appear properly in the API documentation. For all other functions a one line docstring is sufficient.
  • If writing a new/modified preprocessor function, please update the documentation
  • Circle/CI tests pass. Status can be seen below your pull request. If the tests are failing, click the link to find out why.
  • Codacy code quality checks pass. Status can be seen below your pull request. If there is an error, click the link to find out why. If you suspect Codacy may be wrong, please ask by commenting.
  • Please use yamllint to check that your YAML files do not contain mistakes
  • If you make backward incompatible changes to the recipe format, make a new pull request in the ESMValTool repository and add the link below

If you need help with any of the tasks above, please do not hesitate to ask by commenting in the issue or pull request.


Closes #373

@jvegreg jvegreg requested review from bouweandela and schlunma March 9, 2020 10:42
if coord.standard_name in standard_names:
coords = [c.var_name for c in self._cube.coords(
standard_name=coord.standard_name)
]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

any way we can fix this on the fly and report a warning rather than just collecting the duplicates and reporting an error?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you think of a way to decide consistently which is the good one, yes. I am not sure about how to do it

@mattiarighi mattiarighi added the cmor Related to the CMOR standard label Mar 12, 2020
Copy link
Contributor

@schlunma schlunma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Successfully tested with the datasets mentioned in #537:

esmvalcore.cmor.check.CMORCheckError: There were errors in variable tos:
There are multiple coordinates with standard_name "latitude": ['lat', 'latitude']
 There are multiple coordinates with standard_name "longitude": ['lon', 'longitude']

Thanks!

@bouweandela bouweandela merged commit 735f416 into master Mar 24, 2020
@bouweandela bouweandela deleted the detect_frankencubes branch March 24, 2020 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cmor Related to the CMOR standard

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Wrong error message for duplicate coordinate

6 participants