Build-once emissions store
Prepare offline inventories once — conservatively remapped onto a model's grid and kept behind a provenance manifest — so the runtime just serves flux. This is a concept for a separate, model-agnostic tool that could plug into MUSICA via MIEM. These docs describe the design and what it would mean for your work — pick where to start.
Choose a document
New here? Start with the case for it — the rest is the design in depth.
Why a build-once store — and what's still open
Why we're considering this at all, the open questions for the next phase of MIEM (who sources the data, how sign-in works), and what a Zarr v3 layer over the ECCAD catalogue could look like.
The concept — technical
The full design and trade-offs: the two-tier + manifest architecture, conservative remap (generate weights once, apply many), Zarr v3 vs. netCDF, model-agnostic SCRIP/ESMF grid descriptors, and the open build-time questions.
For scientists — overview
The same design from the emissions side: what Tier 1 and Tier 2 actually are, how building Tier 2 compares to UPTEMPO today, what Zarr v3 adds over the netCDF and GRIB you already use, and what stays in MIEM at run time.
See what gets read — netCDF vs Zarr v3
A hands-on demo: choose a spatial extent (global or regional) and a time period (climatology, seasonal, sub-seasonal) — or drag your own — and watch how much of the store each layout actually transfers. Includes the honest netCDF-4 comparison and what "different-resolution data" means here.
In one sentence: remap each offline inventory onto your mesh exactly once, store it with full provenance, and let every run — and any model that consumes it via MIEM — read flux straight from the store.