Inverse Earth Studio, a Geophysical Inversion Workbench on Original Synthetic Earths
Published:
Geophysical inversion is taught one method at a time on one example each, and every method hides its non-uniqueness in its own way. Inverse Earth Studio holds several physics on the same synthetic earths, runs every method on every case under the same conditions, and lets the reader watch the inversion converge instead of reading that it did.
Several physics, the same earths
Twenty distinct geological constructors under six conditions each produce 120 artifacts and 324 method results, baked locally on an RTX 4070 and never in CI. Gravity with SimPEG integral kernels, checked against independent Choclo and SimPEG prism computations; layered magnetotellurics with complex parity tests and a live browser solve; acoustic full-waveform inversion with an executed Deepwave CUDA adjoint derivative; learned inverses (a CNN and an autoencoder on 800, 160 and 160 independent realizations, the inverse CNN estimating column density rather than a 3D volume); and joint cross-gradient inversion coupling two physics on one earth.
One case at a time
The App selects a case with its hypothesis, an experiment and an inverse method (sparse IRLS among them), scrubs the inversion over its computed states, shows the known and the recovered geology in a 3D scene with survey plane, cut, threshold and rotation, and exports the run. Fifteen numerical and fifteen frontend tests; both public hosts match the local build byte for byte (120 experiment hashes, six route documents, three model files).
A rejected version, withdrawn
The first version, with a bespoke look and a course’s material it had no permission to redistribute, was rejected; the whole-project complete claim was retracted, the 0.03.000 correction gave the visual layer back to the shared shell and rewrote the science in both languages, and every case was regenerated on refined grids. Not claimed: field validation, posterior uncertainty, algorithmic novelty; Devito, MTpy/MTH5 and PGI were surveyed and are not implemented, and EDI, PGI and ensemble uncertainty stay open in a public issue. Apache-2.0 code, CC-BY-4.0 content; the lifecycle is building.