Choose a documentation path
Use the application
Install a distribution, validate a baseline EPW, run Standard or Advanced Climate Change, and interpret generated files.
Review the science
Understand climate-change signals, monthly morphing, interpolation, ensembles, uncertainty variants, SolarQC, and methodological limitations.
Develop and integrate
Build the Java 17 source, use the service API, understand package boundaries, run tests, and prepare reproducible releases.
Produce climate resources
Implement schema 1.4 manifests, grids, monthly signals, standard deviations, validity masks, integrity metadata, and climate-resource acceptance.
Compare distributions
Identify CMIP generation, CORDEX driving generation, geographic domain, nominal resolution, release status, and future product lineage.
Audit a run
Trace baseline correction, climate resources, spatial weights, morphing settings, derived variables, warnings, and output checksums.
Scientific pipeline at a glance
Documentation principles
Scientific transparency
Equations, data meanings, assumptions, fallback behavior, and limitations are stated explicitly. Climate-resource values are treated as signals to be applied to a baseline weather sequence, not as a reconstructed future chronology.
Reproducibility
Versioned distribution manifests, SHA-256 verification, per-scenario manifests, record-level diagnostics, deterministic builds, and acceptance tests create an auditable chain from input data to generated weather files.
Distribution separation
The engine is shared. Scientific data identity, pathways, periods, domain, model catalog, branding, and artifact naming are supplied by a separately prepared distribution overlay.
Conservative failure
Malformed resources, non-finite selected values, invalid topology, out-of-domain sites, and incompatible options fail with context. Documented fallbacks are narrow, variable-specific, and written to provenance.