MétaCan
Menu
Back to cohort
Record W4220784098 · doi:10.5194/egusphere-egu22-6593

FAIR building blocks for climate resilience information systems

2022· preprint· en· W4220784098 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typepreprint
Languageen
FieldComputer Science
TopicDistributed and Parallel Computing Systems
Canadian institutionsNatural Resources CanadaComputer Research Institute of MontréalOuranos
Fundersnot available
KeywordsInteroperabilityComputer scienceService (business)ImplementationDatabaseWorld Wide WebSoftware engineeringBusiness

Abstract

fetched live from OpenAlex

<p>Cloud-based big earth data workflow architectures for operational decision making across communities need to follow<strong> </strong>FAIR (Findable, Accessible, Interoperable, Reusable) principles in order to be effective. This presentation highlights mature implementations of OGC standards-based building blocks for climate data processing and service provision that are deployed in leading climate services information server systems such as the COPERNICUS Climate Change Service C3S. OGC Web Processing Services (WPS) form the bases of component operations in these implementations, from simple polygon subsetting to climate indices calculation and complex hydrological modelling. Interoperable building blocks also handle security functions such as user registration, client-site utilities, and data quality compliance. </p><p>A particular focus will be the ROOCS (Remote Operations on Climate Simulations) project, a set of tools and services to provide "data-aware" processing of ESGF  (Earth System Grid Federation) and other standards-compliant climate datasets from modelling initiatives such as CMIP6 and CORDEX. One example is the WPS service ‘Rook’, that enables remote operations, such as spatio-temporal subsetting, on climate model data. It exposes all  the operations available in the ‘daops’ library based on Xarray. Finch is a WPS-based service for remote climate index calculations, also used for the analytics of ClimateData.ca, that dynamically wraps Xclim, a Python-based high-performance distributed climate index library. Finch automatically builds catalogues of available climate indicators, fetches data using “lazy”-loading, and manages asynchronous requests with Gunicorn and Dask. Raven-WPS provides parallel web access to a dynamically-configurable ‘RAVEN’ hydrological modelling framework with numerous pre-configured hydrological models (GR4J-CN, HBV-EC, HMETS, MOHYSE) and terrain-based analyses. Coupling GeoServer-housed terrain datasets with climate datasets, RAVEN can perform analyses such as hydrological forecasting without requirements of local access to data, installation of binaries, or local computation.</p><p>The EO Exploitation Platform Common Architecture (EOEPCA) describes an app-to-the-data paradigm where users select, deploy and run application workflows on remote platforms where the data resides. Following OGC Best Practices for EO Application Packages, Weaver executes workflows that chain together various applications and WPS inputs/outputs. It can also deploy near-to-data applications using Common Workflow Language (CWL) application definitions. Weaver was developed especially with climate services use cases in mind.</p><p>The architectural patterns illustrated by these examples will be exercised and tested in the upcoming OGC Climate Services Pilot initiative, whose  outputs will be also  incorporated into disaster risk indicators developed in the upcoming OGC Disaster Pilot 2022.</p><p><img src="https://contentmanager.copernicus.org/fileStorageProxy.php?f=gnp.090231131ed165283491461/sdaolpUECMynit/22UGE&app=m&a=0&c=67d3cb8cdcd79c816211ccddfc20b1fb&ct=x&pn=gnp.elif&d=1" alt=""></p><p>Further reading:</p><p>https://docs.google.com/document/d/1IrwlEiR-yRLcoI9fGh2B1leH4KU0v0SUMWQqiaxc1BM/edit</p><p><br><br></p><p> </p>

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.957
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0030.004
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.018
GPT teacher head0.270
Teacher spread0.252 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it