OpenAI Education US

University of Arizona

University of Arizona researcher Chi-kwan Chan needed faster ways to create stable numerical approximations for black hole simulations because the equations are computationally intractable and new approaches can take years to develop.

It would take me ten days to come up with ten new approximations. With Codex, this can be done in minutes
speed up these calculations by a factor of 1000

Reported impact

Business outcome

Chan dramatically accelerated simulation development, improved the stability of numerical methods, and freed more time for scientific interpretation and discovery.

  • Productivity Improvement
  • Scalability

Solution

At the University of Arizona, computational astrophysicist Chi-kwan Chan uses Codex to accelerate the code and algorithm work behind black hole simulations for the Event Horizon Telescope effort. The scientific workflow starts with telescope observations and the need to model how plasma behaves in extreme environments, but the underlying equations are so complex that even supercomputers struggle and new approximations can take years to invent. Chan uses Codex to generate coordinate transformations, numerical algorithms, and supporting scientific code through an agent skill he wrote, then implements and verifies those outputs before comparing simulation results with observational data. Codex also reviews code and helps catch mistakes in statistics and numerical methods, making the simulation loop both faster and more reliable. In effect, Codex sits between astrophysics questions and software production, letting Chan spend more of his time on research instead of manual coding.

Data flow

Observational goals and simulation problems from the Event Horizon Telescope workflow are turned into coding tasks for Codex, which proposes algorithms and code that Chan validates and runs before comparing the resulting simulations against telescope observations.

Solution architecture

1 components · 1 layer
  1. Orchestration
    • Codex Generates and reviews numerical algorithms and scientific code for black hole simulations.

Architecture clues

  • Chan uses an agent skill he wrote to drive Codex for simulation work
  • Codex is also used for scientific code review and numerical-method validation
  • The workflow compares simulation outputs with telescope observations

Evidence from the source

CK still has to implement and verify each approximation Codex creates
Codex helps CK review scientific code and catch mistakes with statistics and numerical methods
So CK turned to Codex to help accelerate this process
With Codex we are now able to automatically discover new coordinate transformations and algorithms that can speed up these calculations by a factor of 1000
Transparency Evidence & methodology 75/100 reference value · 88% confidence · 2 sources

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 value75/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 impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence88%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/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. OpenAI

    University of Arizona customer story

    First-party
    https://openai.com/index/creating-new-simulations-black-holes/
    Source type
    Vendor-published customer story
    Published
    Jun 11, 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
  2. University of Arizona

    Institutional Information | Research and Partnerships

    First-party
    https://research.arizona.edu/administration-public/institutional-information

    The page describes the University of Arizona as a land-grant PUBLIC/STATE CONTROLLED INSTITUTION OF HIGHER EDUCATION.

    Source type
    Official company website
    Supports
    • Company size

Date evidence

Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.