Skip to content

Open issue on linking it to agents #2

Closed

Description

@kauedesousa

AgERA5 is untested live. The repo has no CDSAPI_KEY secret, so that job step is skipped. Its offline tests pass.
No lock files. They need PyPI, which this chat cannot reach. The PR description gives the one-line command.
CHIRTS has a single source. It still depends on one personal Hugging Face account, and the Monday test only flags a break.
Store end dates. I told you earlier that both stores cover your latest window, which ends in February 2025. I had not verified that, and the live check only reached April 2024. The scripts fail loudly if a window runs past the store’s last day.
Proxy for the other three stores. I added proxy support only to the two HTTP readers. CHIRPS, elevation and soil use other libraries that I could not test behind a proxy.

Activity

  1. bjyberg commented on Nov 18, 2026

    @bjyberg
    Member

    Pr #1 is merged and addresses the proxy support, window reads, store start/end dates, and tests for PyPI + all of the data urls. I have added fallback for Chirps and Chirts in #3, and the zarr links will be migrated from a personal HF account to storage managed by the Climate Data Hub shortly. All python code uses inline script metadata (PEP 723, # /// script block) - we could add versions to this instead of a lockfile, but realistically the weekly cron job from #1 will catch failing dependencies due to version bump.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions