NVIDIA Public Sector United States

Argonne National Laboratory

Real-time Analytics

Argonne and its collaborators needed to coordinate gravitational-wave and radio follow-up across observatories without moving proprietary datasets, but CPU-bound processing, siloed data-sharing policies, and slow cross-site workflows limited timely multi-messenger discovery.

5-10x speedup compared to CPU workloads
Processed 4,096 seconds of advanced LIGO data in under 4.5 minutes

Reported impact

Business outcome

RADAR enabled privacy-preserving observatory coordination, processed 4,096 seconds of advanced LIGO data in under 4.5 minutes, and achieved a 5-10x speedup versus CPU workloads so researchers can respond faster to multi-messenger events without breaking data-sharing rules.

  • Productivity Improvement
  • Scalability

Solution

Argonne and partner institutions built RADAR as an event-driven, federated framework for multi-messenger astrophysics and ran it on NVIDIA-accelerated supercomputing systems. Site-local AI inference processes advanced LIGO data and matches detections to public LIGO-Virgo-KAGRA superevents before Octopus publishes a trigger across the workflow, often using ProxyStore to move large intermediate results securely. RADAR then uses an AI parser to convert unstructured GCN circulars into structured metadata and combines those public alerts with private observatory measurements while keeping raw data local. Downstream, Dingo-BNS performs gravitational-wave parameter estimation and afterglowpy models federated radio afterglows. NVIDIA A100, A40, and GH200 GPU systems on Polaris, Delta, and DeltaAI supply the compute layer that makes this privacy-preserving inference and coordination pipeline fast enough for real-time follow-up.

Data flow

RADAR performs site-local AI inference on LIGO data, matches detections with public superevents, sends triggers through Octopus and ProxyStore, parses GCN circulars into structured metadata, combines those alerts with local observatory measurements, and runs Dingo-BNS plus afterglowpy to refine source parameters without moving raw proprietary data.

Solution architecture

8 components · 2 layers
  1. Compute
    • Dingo-BNS Performs gravitational-wave parameter estimation inside the federated inference pipeline.
    • afterglowpy Models federated radio afterglows so the system can refine source parameters from follow-up observations.
    • NVIDIA A100 Tensor Core GPUs Provide accelerated compute for site-local AI inference and large-scale astrophysics processing.
    • NVIDIA A40 GPUs Support the accelerated supercomputing environments used by the RADAR workflow.
    • NVIDIA GH200 GPUs Extend the framework's high-performance GPU capacity for next-generation astrophysics workloads.
  2. Orchestration
    • RADAR Coordinates the federated multi-messenger workflow across observatories while preserving data locality.
    • Octopus Acts as the cloud-hosted messaging fabric that publishes event triggers across the workflow.
    • ProxyStore Moves large intermediate results efficiently and securely between RADAR workflow stages.

Architecture clues

  • Public alerts and local observatory measurements are combined without requiring raw-data transfer between institutions.
  • RADAR is explicitly designed as a federated, privacy-enhancing workflow rather than a centralized data lake.
  • The framework parses unstructured GCN circulars into structured machine-readable metadata.

Evidence from the source

Integrating NVIDIA GPUs on the Polaris, Delta, and DeltaAI supercomputers, the framework's AI module for signal detection processed over an hour—4,096 seconds—of advanced LIGO data in under 4.5 minutes.
Researchers at Argonne National Laboratory and collaborating institutions have developed RADAR, a federated, privacy-enhancing framework that enables observatories to coordinate gravitational-wave and radio follow-up without moving or exposing proprietary data.
Subsequently, RADAR integrates information across messengers by running Dingo-BNS for gravitational-wave parameter estimation and afterglowpy for federated radio afterglow modeling.
This translates to a speedup of 5-10x compared to the initial timeframe when running on CPU workloads.
When a matching superevent is found, RADAR publishes a trigger to Octopus—a cloud-hosted, event-driven messaging fabric—often using ProxyStore to handle large intermediate results efficiently and securely.
Transparency Evidence & methodology 95/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. NVIDIA

    Argonne National Laboratory customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/argonne-ai-cosmic-discovery/
    Source type
    Vendor-published customer story
    Published
    Jan 27, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Jan 27, 2026 · NVIDIA · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.