Skip to content

GCRI · Water Nexus

داتا و ڕێگا تەکنیکییەکان

The public technical tools of Water Nexus: the models and data behind them, how to reproduce a view and the uncertainty it carries.

01شوێنی کار

The workspace for data and technical methods.

Build workspace

Water · Data and technical methods · Run R-7518 · Example interface, not a record

Run in progressGCRI · Water Nexus

Runs

same inputs, versioned

R-3125Hydrology and waterv7.20.47کارا
R-5152Water and environmentalv8.70.73Passed
R-8820Geospatial informationv3.40.44Passed
R-8148چاودێریی زەویv7.60.61Passed

کارتی مۆدێل

ڕێگا
هایدرۆلۆژی و زانستی ئاو
تێکردنەکان
Gauge network telemetry, Reanalysis precipitation
پشتڕاستکردنەوە
held-out period, skill reported
ناونیشان
مۆدێلکراو

Run log

  1. 00:00:57زانیاریIngest gauge network telemetry
  2. 00:03:12زانیاریSchema and licence checks passed
  3. 00:06:40ئاگادارکردنەوەGap filled by interpolation, flagged
  4. 00:16:03تەواو بووCalibration complete
  5. 00:21:55دەروازەIndependent test queued
Build workspace.ڕووکاری نموونەیی؛ داتای ڕاستەوخۆ نییە.

Water Nexus · Build workspace. Build workspace: example names and illustrative values, not a record.

02ئامرازەکان

What is published here.

نەخشەکان

Released maps

Open the released maps

مۆدێلەکان

Reviewed models and scenarios

Open the reviewed models

Scenarios

Sector scenarios

Open the sector scenarios

03What the tools answer

Three questions every water tool should answer about itself.

  • Which basin, period and spatial resolution it represents.
  • Which inputs it uses, with evidence labels, and which it lacks.
  • What decision it is fit for, and what it is not fit for (for example, a regional drought map is not a well-siting tool).

Released maps carry the indicator register; model descriptions are on models and scenarios.

04پرۆسە

چۆن پرۆسەکە کار دەکات.

Process explorer · Process

Data and technical methods: Build, sign and accept

10 steps4 قۆناغ2 دەروازە

پرۆسە

Data and technical methods: Build, sign and accept

An admitted mission becomes a cycle project; the build is pinned, verified and signed, and the Global Risks Forum (GRF) records acceptance for exercise, not permission to deploy.

  1. 01 Request and sources

    1. 01Admitted mission becomes a cycle projectتۆمار · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
    2. 02Qualify data sources and resourcesStep · the Global Centre for Risk and Innovation (GCRI)GCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.
  2. 02 Build and verify

    1. 03Source snapshotتۆمار · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
    2. 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
    3. 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
    4. 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.
  3. 03 Sign and admit

    1. 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
    2. 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.
  4. 04 Accept

    1. 09ڕاپۆرتی بنیاتنانی سەرەکیتۆمار · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
    2. 10G3 · Build بۆ ڕاهێنان وەرگیراوەدەروازە · Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.

ساڵی پڕۆگرام · NXS-FAC · UniverseDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The record order follows the Builds and Releases room lists of NXS-FAC.

05Build environment

Working with the tools.

Analysis runs in Foundry for authorised projects. Public pages show released views only, each with its time and space reference and its rights.

06سەرچاوەکان

Where this page’s references lead.

ئەو لەش و بەڵگەنامانەی ئەم لاپەڕەیەیان لەگەڵ دەخوێنرێتەوە. دۆخ و وەشانەکان دەگۆڕێن؛ هەر بەستەرێک دەچێتە لای لەشی دەرکەر.

07لاپەڕەکان

Pages in Data and technical methods.

08پرسیارەکان

پرسیار و وەڵام.

Can I use the data?
Each released view states its licence and terms. Data that is not released is not available through these pages.
Reportsبەشداربە

لەم لاپەڕەیەوە بەڵگە پێشکەش بکە.

Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

GCRIWater Nexusمەترسی و خۆڕاگریی کەرتی جیهانیمەترسی و خۆڕاگریی سیستەمی وڵاتئاماژەی چاودێرگە
Water Nexus

ڕێگایەک، کۆمەڵە داتایەک یان پرسیارێک بهێنە.

زانیاری و پرسیار ئەمڕۆ کراوەن. پرسیارێک ژمارەی ئاماژەی پێدەدرێت و هەنگاوی دواتر دیاری دەکات؛ داواکاری، پارەدان، تەرخانکردنی کۆمپیوتەر و تۆمارکردن تەنیا کاتێک دەکرێنەوە کە تیم، مەرج و توانای پێداچوونەوەیان هەبێت.