Checked against a reference

A calculation can be checked: Ophiolite runs it on a small, reviewed test file and compares the numbers with a reference made another way, such as an independent calculation or a published file. A check says something about those numbers on that data only. It does not prove that a result is right for your data.

Read the check on a result

Open a result and look under How this was made. A result calculated by Ophiolite says one of these:

• “Checked against an independent calculation (version 1) on HON-GT-01 gamma-ray excerpt, 7 October 2026: passed.” followed by the allowed difference, for example “Within 0.000001 V/V.”, and “This shows these numbers on this data only.”
• ”…: differed.” followed by the largest difference and at how many depths, for example “Largest difference 0.03 V/V, at 4 of 5 depths.”, and the allowed difference.
• “Reported check by Marit Jansen: passed on HON-GT-01 gamma-ray excerpt.” followed by “Ophiolite did not repeat this check.”, when the person who published the check ran it and Ophiolite did not repeat it. A reported check is never shown as “Checked against”.
• “Not checked against a reference.”, when no check was published for the calculation and release that made the result.

A check applies to every result made by the same calculation, in the same version, under the same Ophiolite release. Checks made under other conditions, such as another allowed difference or another reference, are listed separately. Older checks of the same conditions are under Earlier checks. If two checks of the same conditions disagree, both are shown with their times. The exact identifiers of each check are under Technical details.

Compare a result with a file

Under the result, choose Compare with a file. This works on a result with only one version too.

1. Choose a well log (LAS) or a grid file (ESRI ASCII) you trust, up to 2 MiB.
2. If the file has several curves, choose the one to compare.
3. For a grid file, confirm its coordinate system, units and datum. They are saved with the comparison. Nothing is converted: a file confirmed in feet is not compared with a result in metres.
4. Leave Allowed difference empty to ask for exactly equal values, or give a number in the curve’s unit.

The answer says whether the values match, or how far they differ and at how many depths. The comparison is saved on this result only, for you and for project administrators who can read the result. It is not a check of the calculation.

From Python or a terminal:

ophiolite checks compare --asset <result> --revision <version> --file my-reference.las --curve VSH --tolerance 0.001

Publish a release’s checks

Checks are published by project administrators, and by people an administrator allows, as part of qualifying a release. The release’s conformance run writes one folder per check without a network connection:

python -m conformance.checks produce checks/
ophiolite checks publish checks/shale-volume-hon-gt-01

The server repeats each calculation on the check’s test file and compares the result itself. Only then does a check read “Checked against”. A check made for another release, or with a file that is not the recorded one, is refused and nothing is saved:

What happened	What you see
You may not publish checks	Publishing checks needs permission. Ask a project administrator.
Another release	Not published: the check was made for release 2026.10.55, not the release this server runs.
A changed reference file	Not published: the reference file does not match the recorded file.
The server took too long	Not published: the server did not finish the check in time. Nothing was saved.
The server is busy	Not published: the server is busy. Try again.

--json adds the name of the part of the check that was refused. An administrator changes who may publish with ophiolite checks publishers add <person> and ophiolite checks publishers remove <person>.