-
Notifications
You must be signed in to change notification settings - Fork 108
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
H5Coro Integration #636
Comments
When testing user-customized variable queries, I noticed that attempting to append default variables to
This has been observed for the following products: ATL08 (lat/lon/time only), ATL10 (returns value error), ATL12 (lat/lon/time only). Higher-level products have not yet been tested. Will focus on ATL06 for H5coro integration tests, to avoid this issue for now. |
Script that reads icepyx variables using H5Coro works, and is decently fast. I still want to try and improve the speed of the code (maybe parallelizing it somehow), and I need to add the beams as a variable column. Might also add whether it's a "strong" or a "weak" beam. One issue I ran into is that some of the variables ( |
Update on the varying size issue. I am attempting to use the icepyx Sample output for
(full output is too long, but there are many more variable paths. Sample output for
Variable paths are missing from the variable dict, and the secondary |
We are currently looking to update the icepyx reader module to use H5Coro to efficiently read in queried ICESat-2 data. As is, the reader module is quite slow, especially if reading in data from the cloud, and H5Coro should make data reading much faster.
However, some work is needed for H5Coro to work with icepyx. H5Coro needs variable paths to be specified in a list format. It is also unclear how feasible it is to convert data loaded with H5Coro to Xarray. The easiest method is to read the data into GeoDataFrames, but converting these to Xarray is too memory-intensive.
A proposed temporary solution for the reader module is to convert local files into Xarray, and cloud-based files to GeoDataFrames. Moving forward, a more concrete solution will be needed for the H5Coro integration.
Current Tasks
The text was updated successfully, but these errors were encountered: