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

Example code does not error on opening v0 dataset model #147

Open
BrianMichell opened this issue Dec 11, 2024 · 1 comment · May be fixed by #148
Open

Example code does not error on opening v0 dataset model #147

BrianMichell opened this issue Dec 11, 2024 · 1 comment · May be fixed by #148
Assignees
Labels
bug Something isn't working Improvement Something could be better

Comments

@BrianMichell
Copy link
Collaborator

  • Ingest SEG-Y to MDIO using stable v0 Python command.
  • $ ./real_data_example --print_dataset --dataset_path="ingested_mdio"
  • No output to terminal.

The expected output should be an error message regarding failure to parse schema.
Need to investigate whether this is an issue in the API skipping some step or the example code needing to be updated.

@BrianMichell BrianMichell added the bug Something isn't working label Dec 11, 2024
@BrianMichell BrianMichell self-assigned this Dec 11, 2024
@BrianMichell
Copy link
Collaborator Author

The behavior is from the example not printing the error status on failure. The returned error for opening v0 is very opaque and should be improved.

Error: NOT_FOUND: Error opening "zarr" driver: Metadata at test.mdio/data/.zarray does not exist

This error is due to the v0 data being further broken down into transpose chunked volumes.

@BrianMichell BrianMichell added the Improvement Something could be better label Dec 11, 2024
@BrianMichell BrianMichell linked a pull request Dec 11, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Improvement Something could be better
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant