Skip to content

End-to-end sponsor example: catalog → shardmap → dual aggregation → cached reads #168

Description

@espg

🤖 from Claude

(espg-directed, in-session)

Tracking issue for the sponsor-facing end-to-end example: two notebooks plus the executed pipeline behind them, on real public data.

Deliverables

Environment premise

Notebooks are written against zagg ≥ 0.14 (main + #163 virtual-index backends + #165 morton location channel — both now merged; 0.14.0 is the release the notebooks assume) and h5coro-hidefix ≥ 0.2. Anything not yet released is flagged in a provisional cell. Lambda invocation cells document the deployed path; the actual execution run is local/in-process until 0.14.0 deploys.

Phases

  • 1. Scaffolding + catalog & shardmap sections (executed)
  • 2. Dual aggregation runs (executed, outputs in bucket)
  • 3. Read-back / PDF / waveform sections
  • 4. Notebook B + binder wiring
  • 5. Polish + full top-to-bottom re-execution of both notebooks + self-review folds

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions