Repository navigation
feat: Add CHC geotiff files as backup path when agents cant access zarr - #5
Merged
Merged
Conversation
Some agent sandboxes block S3 but allow data.chc.ucsb.edu. The yearly NetCDFs there hold the same rnl product, chunked, so point reads stay small. Retries back off on the server's 429 rate limit.
Same reason as CHIRPS: data.chc.ucsb.edu is reachable where Hugging Face is not, and serves the CHIRTS-ERA5 data the Hugging Face store copies.
Otherwise check.py reports CHIRPS and CHIRTS as blocked in sandboxes where their fallback works.
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.
On Alliance Claude for example, the chc website is permitted, but the others are not. This tries the zarr datasets first, if they cannot be accessed for chirps/chirts, it now falls back to the CHC hosted data