GCRI · Data and Compute
Research and evidence
The research behind Data and Compute: the questions it asks, the models and measurements it uses, how uncertainty is stated and how a result is reviewed and reproduced before it is published.
Research and evidence in four parts.
What the research asks.
- 01
Public interest data infrastructure
Dataspaces and interoperable evidence.
- 02
High performance computing
HPC/GPU workloads and scientific compute.
- 03
Cloud and edge systems
Hybrid, local and sovereign computing options.
- 04
Chips and semiconductors
Critical compute hardware and supply chains.
- 05
Data rights and trust
Data access, licensing and privacy.
- 06
Reproducible pipelines
Pipelines, models and experiment provenance.
What data and compute research cannot yet answer well enough for decisions.
Data and compute are now infrastructure for science and public services. The agenda addresses access, concentration, sustainability and the trustworthiness of pipelines.
- How should public-interest data infrastructure be governed so that it remains open and secure? See public-interest data infrastructure.
- What is the energy and water demand of compute growth, and where does it stress local systems? See compute, energy and water.
- How concentrated is advanced chip supply, and what would a disruption mean for research and services? See chips and semiconductors.
- What makes a data pipeline reproducible years later? See reproducible pipelines.
Every result keeps its label.
Results are labelled as observed, published statistics, estimated, modelled, forecast, scenario or expert judgement. Missing data is shown as missing, never filled silently.
Where this page's references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Pages in Research and evidence.
Questions and answers.
Can I propose a research question?
Contribute evidence from this page.
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.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring a method, a dataset or a question.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.