Skip to content

fix slice_number which could have a wrong number of values #5

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.

Sign up for GitHub

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

Jump to bottom
Open
agrouaze wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix slice_number which could have a wrong number of values #5

agrouaze wants to merge 1 commit into from

Conversation

@agrouaze
Copy link
Contributor

@agrouaze agrouaze commented Sep 19, 2023 •
edited
Loading

  • reduce info logs (dataframes content is no more displayed in logger.info)
  • try-catch for slice_number decoding

It seems that we have a new error (probably coming from scihub system): the number values given by the field slice_number is inconsistent with the other fields. For instance you can found 5 SAFE matching a space-time query but only 4 slice_number are given.

@agrouaze agrouaze changed the title reduce info logs and fix slice_number which could have a wrong number… fix slice_number which could have a wrong number of values Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@agrouaze