Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pyaerocom gives warnings about files not being in metastandards version #1067

Closed
heikoklein opened this issue Mar 19, 2024 · 1 comment · Fixed by #1094
Closed

pyaerocom gives warnings about files not being in metastandards version #1067

heikoklein opened this issue Mar 19, 2024 · 1 comment · Fixed by #1094
Assignees
Labels
bug 🐛 Something isn't working good first issue Good for newcomers
Milestone

Comments

@heikoklein
Copy link
Member

Describe the bug
Please provide a clear and concise description of what the bug is.

  • Pyaerocom version: 0.16
  • Error message (if applicable):
pyaerocom.metastandards:INFO:Invalid or old data ID ECMWF_CAMS_REAN. Consider format <model-name>-<meteo-config>_<experiment>-<perturbation>

This info message is confusing and not real since metastandards are not enforced in pyaerocom yet, and 4 different standards are possible while only one is tested.

To Reproduce
python cfg_benchmark.py

Expected behavior
No INFO/warning should be given on default, DEBUG-message still possible.

@heikoklein heikoklein added bug 🐛 Something isn't working good first issue Good for newcomers labels Mar 19, 2024
@heikoklein heikoklein added this to the m2024-04 milestone Mar 19, 2024
@heikoklein heikoklein changed the title pyaerocom gives warnings about files not being in metadata-standards version pyaerocom gives warnings about files not being in metastandards version Mar 20, 2024
@lewisblake lewisblake modified the milestones: m2024-04, m2024-05 Apr 2, 2024
@Ovewh
Copy link
Collaborator

Ovewh commented Apr 3, 2024

I think the "Meteorology config substring in data_id {meteo} needs to start with met." warming should also only be a DEBUG message not warning. Since this is also not enforced.

thorbjoernl added a commit that referenced this issue Apr 5, 2024
thorbjoernl added a commit that referenced this issue Apr 5, 2024
@heikoklein heikoklein modified the milestones: m2024-05, m2024-04 Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants