Ad-hoc testing of Kerchunk engine compatibility with xCDAT#61
Open
tomvothecoder wants to merge 25 commits intomainfrom
Open
Ad-hoc testing of Kerchunk engine compatibility with xCDAT#61tomvothecoder wants to merge 25 commits intomainfrom
tomvothecoder wants to merge 25 commits intomainfrom
Conversation
- Add __init__.py to make modules importable
Collaborator
Author
|
Notes from 01/12/26 meeting Debug
Script Extensions
Notes
|
This file contains hidden or 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
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.
Related to xCDAT/xcdat#812
Perform ad-hoc manual testing to confirm that xCDAT works seamlessly with Kerchunk without modifying any code or adding a formal test suite. The goal is to confirm functional parity between Kerchunk-backed datasets and traditional NetCDF I/O through exploratory testing and to document any issues found.
Key areas to check manually:
Basic Open Behavior
Performance and Stability
.load()behavior (subset) in a new notebook -- IN PROGRESSMetadata and CF Handling
time,lat,lon,lev) are detected correctly.xCDAT Functionalities -- identical results?
xCDAT Functionalities -- performance differences + .load?