earth-report-the-lattice-and-show-the-field

Solid

Use at analysis and figure planning when a geospatial or gridded result is about to be reported only as regional aggregates. Covers reporting the stratified lattice, showing the field the strata came from, and which map a study of this kind is expected to publish.

AI & Automation 804 stars 25 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 85/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Earth: report the stratified lattice, and show the field it came from Before designing anything, read the archive's own layout: directory names, filename tokens, categorical columns, coordinate dimensions. Those are the axes the data distinguish, and in this field they are mandatory reporting axes rather than optional cuts. Deliver every headline quantity as a per-stratum table or small-multiple panel over the full cross-product the data support (method x sub-region, variable x level x lead, scenario x class, epoch x unit), each stratum carrying its own uncertainty, plus a total or global row. A pooled aggregate alone reads as the analysis never having been done. Pair every skill, risk or change number with the spatial field that produced it: a map at the data's native resolution per scenario, period or lead time, plus zoomed regional panels over each place your result names, because coastal and mesoscale structure is invisible in a global panel and readers here look for it. Where the metric varies with lead time, horizon or epoch, plot it along that axis and mark the threshold crossing (skill horizon, sign change, acceleration), attaching an uncertainty to the change itself and not only to the levels. Name and rank the specific regions, countries or basins that dominate the total, that carry the largest relative change, and where estimates disagree; a qualitative pattern description does not substitute. Print the governing numbers inside the panel. Produce the study's o...

Details

Author
tangxiangru
Repository
tangxiangru/AutoR
Created
5 months ago
Last Updated
today
Language
Python
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

earth-two-orderings-of-a-regional-decomposition

Use at study design when the figure and table plan is fixed, at analysis, and again at writing, whenever the deliverable splits a global or basin-wide total into per-region parts and you are about to report each part as an absolute rate. Covers the two normalisations every row owes and why their disagreement is the result, where the intensity denominator has to be captured before you need it, and what the spare cell of a small-multiple grid is for.

804 Updated today
tangxiangru
AI & Automation Solid

earth-the-technique-grid-needs-values-in-its-cells

Use at study design when the figure list is chosen, at implementation before any pipeline code is written, and again at analysis, when the supplied archive is stratified by measurement technique or instrument and you are about to describe that stratification. Covers reading the per-technique columns the archive already ships, drawing the technique grid with estimates in it rather than file counts, and why a no-peek rule about the reference product must not reach your figures.

804 Updated today
tangxiangru
AI & Automation Solid

earth-shape-of-the-record-and-share-of-the-budget

Use at analysis and again at writing when the deliverable is a multi-year record - an annual time series, a reconstruction, a trajectory - and you are about to report it as a period mean, a cumulative total and a validation residual against a reference version of itself. Covers the change over the record's own length, the extremes, the per-unit split, and the record's share of the budget it is one term of.

804 Updated today
tangxiangru