Additional grid files and removing (for the day) access to velocity data. #326
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.
Closes #323 (grid variables
XU, XV, YU, YV
are now available in the grid file). I checked having these grid variables pre-computed significantly speeds up the cutout function when transforming (lazily) the dataset.This PR also removes the velocity fields from the intake catalog. This is only temporary. I am combining all the zarr stores (within each single filedb volume) into a single one (see issue #324) . This is going to take the rest of the day. The final destination where all the data (within a single filedb node) will be stored will be where currently the velocity data lives. For that, and to avoid issues when reading LLC4320 data today, I am removing this entry (velocities) from the catalog.
Once the data has been written into a single zarr store, I will create another PR where I restore the entry associated with the velocities. In that PR (later today) all data will be in a single zarr store.