Research, pitched straight

Certified trust in cheap approximations.

Complex scientific and engineering problems often require calculations that are too slow or costly to repeat. Faster methods can provide an answer — but how do we know when that answer can be trusted without running the full calculation? This research develops methods that provide that assurance.

One number to keep in mind
0
solves for a brute-force parameter sweep
0
solves for the adaptive method — with an error certificate

Same accuracy target, orders of magnitude less compute — and you get a bound telling you where the answer is trustworthy. Play the sampling game →

Three questions this work answers

Story 1

My simulations are too expensive to run everywhere.

An adaptive method that decides where the next expensive solve is worth it — and certifies the regions it skipped.
Story 2

My fast surrogate is great… until it silently isn't.

Where systems change character — frequencies collide, modes swap — smooth shortcuts fail. This method flags exactly those regions.
Story 3

My model reasons from similar past cases. Should I trust it?

A certificate that grades the evidence behind a prediction: if the supporting cases churn when the input wiggles, don't trust it.

New to the vocabulary?

All three stories revolve around eigenvalues — the numbers a physical system answers with when you ask it to vibrate, resonate, or settle. Five-minute tour, with sound →

Vocabulary, once

The numbers a system answers with

Flick a wine glass and it rings at a pitch it chooses, not you. Every structure, circuit, and molecule has such preferred numbers. Engineers call them natural frequencies, physicists call them energy levels, mathematicians call them eigenvalues. Three dialects, one idea.

These numbers matter because they are where things resonate, absorb, or break: a bridge's response to wind, a satellite panel's flutter, a molecule's spectral lines. Designing a system means steering its numbers; certifying a design means knowing them, everywhere in the design space.

Turn the peg

Below is a tiny "guitar string" — a chain of masses and springs. The slider is a tuning peg: it stiffens the string. Watch its preferred numbers move. Each curve is one mode's frequency as the peg turns.

Sound plays only when you press the button — it maps the lowest three numbers to audible pitches.

The catch that motivates everything here: computing these numbers for a real design (a full aircraft panel, a reactor coil) takes minutes-to-hours per design variant — and design spaces have thousands of variants. That cost is what the adaptive method attacks.
Story 1 · expensive simulations

Spend solves like money

You have a design space — say, two knobs on a component — and each evaluation of a design is an expensive simulation. You can't afford the full sweep. Where do you spend your solves?

Level 1 — you place the solves

Click (or tap) up to 12 points in the design space below. The heatmap then reveals where your reconstruction of the system's numbers is still wrong. The ridge you'll probably miss is where two of the system's numbers nearly collide — precisely where behaviour changes fastest.

0
solves spent
—
worst remaining error

Level 2 — the adaptive method places them

Now watch the greedy algorithm from the research: each step, it asks a cheap error indicator "where am I most wrong?", solves there, and updates. Shaded regions are certified: the indicator bounds the error below the target, so no further solve is spent on them.

0
solves spent
—
worst remaining error
0%
of design space certified
The point is not that the algorithm beats your intuition on a toy — it's that it does this in six-dimensional design spaces, where intuition has no picture to look at, and returns a certificate instead of a hope.
Story 2 · silent surrogate failure

Where the shortcut breaks — and how to know

Fast surrogates assume the world changes smoothly. Mostly it does. But when two of a system's numbers approach each other, the modes behind them swap identities — and a smooth shortcut tracks the wrong thing, confidently.

Watch two numbers collide

The demo solves a small system live as you drag the design parameter. The symmetry toggle decides the collision's character: with symmetry, the two curves cross cleanly; break the symmetry, and they repel — an avoided crossing, where eigenvalue curves veer apart at close range.

Now add a lazy surrogate

The dashed line is what a cheap interpolant built from a few samples believes. Away from the collision it's fine. Near it, it's wrong exactly where the design is most sensitive — and nothing in the surrogate itself warns you. The shaded band is the region the research's error indicator flags: "do a real solve here."

Silent failure is the expensive kind: a flutter margin or a filter passband missed not because the model was bad everywhere, but because it was bad in the one narrow region that mattered.
Story 3 · trust by analogy

We don't grade the answer — we grade the evidence

Many production models reason by analogy: to value this house, look at similar recent sales; to judge this claim, look at similar past claims. The prediction inherits its credibility from the supporting cases. So interrogate the support.

Wiggle the input

Below, a toy predictor estimates a value from its k nearest past cases (highlighted). Drag the query point. The trust light doesn't watch the prediction — it watches the support set: if a tiny wiggle in the input swaps out the cases the answer rests on, the evidence was fragile, whatever the number says.

stable evidence

This is a certificate on the evidence, orthogonal to the model: it can ride on top of any similarity-based system without retraining it. Stable support doesn't make a prediction right — but churning support tells you, cheaply and before the fact, that this particular answer isn't resting on anything solid.
About

Who's behind this

I'm Moataz Alghamdi — PhD in applied mathematics (KAUST, 2025), working on certified model reduction for parametric eigenvalue problems and on certificates for similarity-based evidence.

This site is the intuitive face of the work. The technical record — algorithms, proofs, convergence studies, reproducible figures — lives in the figure book, which every demo here links back to.

What I'm looking for

Conversations with teams whose pain matches the stories: expensive parametric simulations, surrogates that fail near mode interactions, or similarity-based predictions that need a trust layer. If one of the three stories sounded like your Tuesday, I'd like to hear about it.

Contact

Email: moatazalghamdi@gmail.com
GitHub: github.com/Moatazg