Check valid_datetime of input data #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
b8raoult
previously approved these changes
Sep 8, 2024
for more information, see https://pre-commit.ci
|
I have accepted the PR. I did a small change because we are migrating from CliMetLab to earthkit-data, so one line needed change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dear Baudouin,
I have been experiencing difficulties with my manually crafted GRIB input, specifically related to the datetime information within the metadata. To save myself from the same issue in the future, I believe it would be useful to verify the timestamps of the input data. However, I do not yet have a comprehensive understanding of the inference code, so please feel free to suggest another way to validate the input data.
Best,
Marek