What makes a useful prior?
Inverse problems often require knowledge beyond the measurements. We investigate how that knowledge can be represented, learned, and reused—and how it shapes the reliability of a solution.
OpenInverse is a research initiative advancing AI for inverse problems across science and engineering. We study how models, learned priors, and evaluation methods can transfer across problems.
Inverse problems start with observations and ask what produced them: reconstructing an image from measurements, estimating a material’s properties, or recovering the structure beneath the Earth. The challenge is that incomplete and noisy observations can support more than one answer.
What changes between problems is the operator and the space the unknown lives in, while the difficulty stays the same. This is why a method developed for one problem keeps reappearing, in slightly different form, in problems that share nothing else.
There is more than one way for a method to generalize. It may be reusable within a single problem, portable across measurement setups, or transferable between problems that share no physics, and each of those claims requires different evidence.
One problem, one setup, one dataset.
The same prior carries to a new instance.
Adapts to different forward operators and scientific domains.
Pretrained models that adapt across operators, tasks, and domains.
Inverse problems often require knowledge beyond the measurements. We investigate how that knowledge can be represented, learned, and reused—and how it shapes the reliability of a solution.
We explore how AI and deep learning can combine with physics, mathematical models, numerical methods, and domain knowledge to solve inverse problems across science and engineering.
We study what can be shared across tasks, operators, and domains, and how to evaluate the capabilities and limitations of reusable and pretrained models.
OpenInverse Bench brings together problem definitions, datasets, baselines, and evaluation protocols to study how inverse methods perform—and how well they transfer.
Operators, noise settings and splits, published as code.
Classical and learned reference implementations, kept with the data.
Reconstruction quality, measurement consistency, uncertainty, and computational cost.
Trained on one operator family, tested on an unseen one.
We organize challenges, competitions, workshops, and fellowships around shared inverse problems, connecting method researchers with domain expertise.
One stated problem, a held-out set, a deadline.
Leaderboard rounds on the benchmark.
Method work and domain work in one room.
Longer work on a single open question.
Working on an inverse problem? We’d like to hear about your research, your measurements, or a question you want to explore together.
contact@openinverse.com