INDEPENDENT MODEL CONSISTENCY · BY DYMENT.STUDIO
Find the inconsistency.
Before the long run.
An atomistic model can return plausible forces that do not belong to a consistent potential energy. We look for reproducible counterexamples—and give your team the exact path back to the problem.
A bounded investigation. Your model can stay on your machine.
For a conservative force model, work around a closed configuration path should vanish within numerical error.
Conceptual illustration · not measured data01 / INSPECT THE INSTRUMENT
A finding needs
a reproducible counterexample.
The examples below are executed synthetic reference tests. They demonstrate the instrument; they are not findings about a commercial AI model.
Recorded findings
A clean result means no inconsistency was detected in these tests. It does not establish physical accuracy or universal validity.
Evidence available
Inspect the report data
Your selected report is read inside this browser. It is not uploaded. This viewer does not execute your model.
Ordinary point checks, nearby energy-gradient checks, and closed-path evidence. We publish the benchmark with the runner, including cases where a simpler check is enough.
02 / THE DELIVERABLE
Less detective work
for your simulation team.
Use the audit before a larger simulation, while integrating a model, or when a regression makes results difficult to trust.
- 01
A scoped finding
What failed, where it failed, and whether refinement supports the conclusion.
- 02
The exact counterexample
Coordinates, force outputs, model settings, tolerances, and source identifiers.
- 03
A repeatable regression
A local runner and report your team can use after a model or integration change.
03 / FIRST PAID PILOTS
One model.
One clear scope.
For teams with a model intended to represent conservative forces and a specific simulation or release decision to make.
Existing verification tools, including OpenKIM, already test energy–force consistency. This service adds an independent, scoped investigation and a handoff your team can reproduce.
$750 USD
- One accepted CPU-runnable model
- Up to 10 nonperiodic configurations, 100 atoms each
- Up to two CPU-hours of agreed tests
- Findings report, recorded evidence, and local reproducer
- Target: two business days after scope confirmation
We confirm compatibility and scope before invoicing. You pay for the investigation and deliverables; finding an error is not guaranteed. This is not a physics or regulatory certification.
Opens your email app. Nothing is submitted here. Please do not attach confidential models before the scope is agreed.
04 / WORK WHERE YOUR MODEL LIVES
Keep the model local.
Bring the evidence.
The Python runner evaluates trusted local model code. The website only reads the saved report. No account or model upload is needed to inspect the reference tests.
Download the local runner ↓Read the quick start ↗Current boundaries
Initial pilot: position-dependent conservative force components, nonperiodic configurations, and accepted local adapters.
Thermostat forces, friction, external driving, periodic-cell workflows, expensive remote APIs, and unsupported model environments need a separately agreed scope.
Reference tests establish software behavior. We have not established accuracy or performance on your model.