Batch interpretation

One parameter set, every well in the project, one table

Run the whole interpretation, shale volume through net pay, across all the wells in a project folder in a single pass, then read the field on one summary table, a posted map, and a set of exports, without opening the wells one at a time.

A field study is the same interpretation repeated across wells, and repeating it by hand is where inconsistency creeps in: one well gets last week's cut-offs, another a different Rw. Batch Interpretation takes the parameter set you tuned on one well and applies it to every saved case in the project, or lets each case keep its own saved parameters where a well genuinely differs. Each well runs the full deterministic route, Vsh, organic matter where enabled, porosity, Sw and net pay, with per-zone lithology from the solver and true vertical depth from the directional survey, and lands as one summary row: net pay, net-to-gross, pay-weighted porosity, Sw and Vsh, bulk volume water, porosity-thickness and hydrocarbon pore thickness. Everything runs in your browser on a project folder you choose; the well files never leave your computer.

Batch Interpretation is part of Formation Evaluation and is included from the Professional plan. See pricing

Create account See the connected workflow

The Batch Interpretation workspace with six synthetic wells selected and run: the case list on the left, the run controls, and a results table with one summary row per well showing net pay, net-to-gross, pay-weighted porosity and water saturation, beside a base map posting net pay at each well. — Six synthetic wells interpreted in one run with the default parameter set: a summary row each, expandable to the zones, and the map posting net pay. Captured from the app; nothing here is client data.

Six synthetic wells interpreted in one run with the default parameter set: a summary row each, expandable to the zones, and the map posting net pay. Captured from the app; nothing here is client data.

What one run does

Pick the cases from the project's case list, keep the open well in or out, and run. For each well the engine:

Runs the same deterministic route the single-well workspaces use: Vsh, the organic-matter step where it is switched on, porosity, Sw and net pay, with the case's zones, curve aliases, depth unit and directional survey
Applies one parameter set to every well, or each case's own saved parameters, with the choice recorded on every result row
Accepts per-well Archie overrides where a single value is wrong for the field: Rw, formation temperature, a, m and n, each as a fixed number or read from a curve in that well's LAS
Sums the zones into one row: net pay, gross, net-to-gross on a stated basis, pay-weighted porosity, Sw, Vsh and bulk volume water, porosity-thickness and hydrocarbon pore thickness, and the zone count, with the zone table one click below
Reports a well as blocked, with the reason, rather than silently skipping it, when its curve slots cannot support the route
Runs in a background thread, so the workspace stays responsive and a long run can be cancelled
Runs a saved calculation chain on every well first, so a derived curve built once in the Log calculators is written on each well before interpretation and lands in the exports, with a per-well count of the steps that ran

QC across the batch

A field table is only useful if the odd well stands out. After every run the workspace flags:

Statistical outliers in net-to-gross, average Sw or average porosity against the rest of the batch, found with the median absolute deviation, so one wild well does not move the threshold
Wells whose interpretation silently degraded: no Sw computed while the other wells have it, or no porosity
Wells with no zones defined, which sum to nothing

The map and the exports

The results leave the table in the forms a field study needs:

A base map posting net pay, hydrocarbon pore thickness, porosity-thickness, average porosity or net-to-gross at each well's surface location from its LAS header, with well-type symbols
A zone-summary CSV across all wells, a parameters-by-well CSV that records exactly what each well was run with, and flat tops
A ZIP with every well's computed curves as LAS 2.0, LAS 3.0, DLIS or CSV, plus the field tables
A printable report, saving the results into the project, and sending every well's zone averages to Volumetrics in one hand-off

Measured on the synthetic wells

The engine is the same code the single-well workspaces run, so it is quick: the 6 synthetic wells, four zones each and feet and metres mixed, interpret in about a tenth of a second on a laptop, and 200 wells of the same size (about 550,000 samples) in under two seconds, using around 30 MB of memory. The run is repeated by an automated test on every release, and the synthetic wells are free to download so you can time it yourself.

Batch feeds the rest of the workflow

Formation Evaluation

The single-well workspaces where the parameter set is tuned before it is applied to the field.

Well Correlation

Pick tops across the same wells and post them to the base map the batch also draws on.

Volumetrics

Every well's zone averages arrive in one hand-off for the in-place and Monte Carlo runs.

Common questions

Where do the wells come from?

From the cases saved in the open project folder, plus the well currently open in the workspace if you include it. Load wells with the multi-well import, which probes every dropped file first so you settle unit and neutron decisions once, then save each as a case.

Do all wells have to use the same parameters?

No. By default the batch parameter set applies to every well. Switch on saved parameters and each case runs with the parameters stored in it; the result row records which was used. Per-well Rw, temperature, a, m and n overrides cover the common case where only the Archie inputs differ.

What happens to a well that cannot be interpreted?

It is reported as blocked with the reason, for example missing resistivity, and the rest of the batch still runs. It is not silently dropped from the summary.

Can wells in feet and metres run together?

Yes. Each case carries its own depth unit and the summary reports thickness in the well's unit. The synthetic benchmark mixes both.

Is any of this sent to your servers?

No. The batch runs in a background thread in your browser, reading cases from the project folder on your computer, and the exports are written by the browser.

Interpret the field in one run

Included on Professional and Team; the 30-day trial includes it too. Start the trial, load the synthetic wells, and run them in one pass.

Create account Book a demo / Talk to sales