Skip to main content

BoreTHM: models of circulating temperature and borehole stability for drilling into superhot rock

BoreTHM is an open-source Python model for assessing drilling programmes in superhot geothermal rock. It couples circulating-fluid and downhole-tool temperatures with thermal stress at the borehole wall to calculate the mud-weight window: the range of fluid densities that meets the pressure constraints through drilling, connections and trips.

At the deep granite targets studied at Soultz and United Downs, whether a drilling window exists depends on how quickly breakouts form after rock exposure. The Soultz window first opens between the sampled delays of 15 and 20 minutes; the formation time has not been measured. Both complete programmes remain NO-GO for the stated designs. BoreTHM is for drilling engineers and researchers assessing a well design or reusing the thermal and stability calculations. Its reference cases support checks against field observations and published models.

Get started

Install BoreTHM with Python 3.11 or later:

python -m pip install borethm

For figures, install "borethm[plot]". Build the water-property cache and run a first assessment:

borethm-water-table
borethm-evaluate --site newberry --json newberry.json

The IAPWS-95 cache is built once, outside the installed package, in the platform's user cache directory. Set BORETHM_CACHE_DIR to choose another location. The evaluator also builds a missing cache on first use. The assessment command prints its result and saves the inputs and calculation provenance as JSON. Evaluations take several minutes; weighted-fluid cases require repeated coupled solves and can take longer.

The same assessment through the public Python interface:

from borethm import evaluate, export_result, find_site
site = find_site("newberry")
result = evaluate(site)
export_result(result, "newberry.json")
print(result["status"]["label"])

Reproduce the reference calculations

Use Python 3.14.4 and the locked dependencies in a source checkout:

git clone https://github.com/ldocallaghan/BoreTHM.git
cd BoreTHM
python -m venv .venv

Use python3 if your system does not provide python. Activate the environment with .\.venv\Scripts\Activate.ps1 in PowerShell, or source .venv/bin/activate on Linux and macOS, then install:

python -m pip install -r requirements-lock.txt
python -m pip install --no-deps -e .
borethm-water-table

Commands for releases before v1.4.0 are in their release records and run from that release's tag.

Run your own assessment

The built-in site keys are soultz, united-downs, larderello, pannonian and newberry.

borethm-evaluate --site soultz --json soultz.json
borethm-sites

The first command evaluates one site; the second reports all five. Use borethm-evaluate --help for the command-line options.

For a new site, follow the site-input guide and copy the documented template. It records units and sources, and checks the inputs before evaluation. The worked example can validate the template without running the full calculation:

python examples/new_site.py
python examples/new_site.py --evaluate --json result.json

The template starts with Soultz's inputs. Replace them with the new site's measurements or explicitly sourced assumptions.

Reading a result

The output guide maps the JSON fields and explains schedule identity.

Start with status and its reasons, then inspect the components that set it. The report includes the operating programme, thermal and hydraulic outputs, stability in each cycle state, allowable mud densities and equipment checks. The JSON retains every evaluated case and the source of each input.

Status Meaning for the evaluated programme and assumptions
GO The modeled checks pass without the additional conditions listed by the evaluator.
CONDITIONAL The assessment depends on stated conditions, such as prescribed fluids or a circulation schedule. Read those conditions before using the result.
NO-GO A modeled gate fails for this programme and these assumptions; the reasons identify the failing components.
INDETERMINATE A required numerical result did not converge, or an equipment qualification remains unresolved without another decisive failure.

An overall NO-GO can coexist with an INDETERMINATE coating check. Exceeding a manufacturer's stated coating rating identifies a qualification question. It does not predict a particular failure mode.

A mud-weight window is the allowable range of fluid density: enough pressure to keep the borehole stable while staying below the modeled fracture-pressure limit. BoreTHM calculates the range that satisfies all evaluated depths, operating states and stress/strength cases, separately for drilling and trips.

Two pressure descriptions appear in the outputs:

  • Target SG-equivalent expresses pressure as an equivalent static column at the target. It is a local stability diagnostic, with the existing friction/backpressure treatment.
  • Surface SG at 20 °C is fluid density divided by 1,000 kg/m³. The combined pressure constraints set the allowable range of that surface density.

A positive target interval does not establish a workable whole-hole fluid. If the required minimum density exceeds the permitted maximum, no mud density satisfies both pressure limits. The densities reported in that situation are calculation inputs and cannot be prescribed.

Example results

The worked assessments target rock at 400 °C. Every status below refers to this programme and these assumptions.

Site Target, km Status Main finding
Soultz-sous-Forêts 10.70 NO-GO No drilling or trip fluid density satisfies all pressure limits; the best attempted run-in exceeds the tool limit.
United Downs 12.86 NO-GO No drilling or trip fluid density satisfies all pressure limits; drilling and run-in exceed the tool limit.
Larderello 2.40 CONDITIONAL Requires weighted drilling and trip fluids.
Pannonian Basin 9.71 NO-GO No drilling or trip fluid density satisfies all pressure limits; coating qualification is unresolved.
Newberry 3.63 GO The evaluated programme passes with water.

These sites have different evidence quality. Soultz and United Downs use measured or calibrated stresses and strengths, extrapolated to the targets. Larderello and Pannonian retain unsourced strength assumptions. Newberry's well check does not reproduce the observed pattern in every rock type. The input-source records explain those differences.

Local stability and the complete programme

At Soultz, eight of nine selected stress/strength cases have an open target drilling interval; at United Downs, two of four do. Both complete programmes remain NO-GO for this programme and these assumptions because no mud density satisfies the pressure limits throughout the evaluated hole, and tool-temperature limits are exceeded.

Target-depth case table and its interpretation

Need and limit are static-column SG-equivalent values at the target. They differ from the surface mud densities a programme would prescribe. The saved target stability-cycle verdict also checks connections and the trip; it excludes separate whole-hole, tool and equipment gates. Each site's reference thermal/hydraulic solution is reused across cases without a fresh coupled evaluation for each case. An open interval does not prove the saved attempted fluid lies inside it.

Case UCS, MPa Drilling need / limit, SG-equivalent Target stability-cycle verdict
Soultz: SHmax lower bound (0.90 Sv) 100 1.230 / 1.296 CONDITIONAL
Soultz: SHmax lower bound (0.90 Sv) 115 1.209 / 1.296 CONDITIONAL
Soultz: SHmax lower bound (0.90 Sv) 130 1.189 / 1.296 CONDITIONAL
Soultz: SHmax mid-range 100 1.271 / 1.296 CONDITIONAL
Soultz: SHmax mid-range 115 1.251 / 1.296 CONDITIONAL
Soultz: SHmax mid-range 130 1.230 / 1.296 CONDITIONAL
Soultz: SHmax upper bound (1.05 Sv) 100 1.313 / 1.296 NO-GO
Soultz: SHmax upper bound (1.05 Sv) 115 1.292 / 1.296 CONDITIONAL
Soultz: SHmax upper bound (1.05 Sv) 130 1.272 / 1.296 CONDITIONAL
United Downs: intact, 0 K 203 1.169 / 1.220 CONDITIONAL
United Downs: intact, 40 K 172 1.205 / 1.220 CONDITIONAL
United Downs: weak zones, 0 K 147 1.234 / 1.220 NO-GO
United Downs: weak zones, 40 K 118 1.267 / 1.220 NO-GO

Soultz target 10.70 km; United Downs target 12.86 km. Sv is vertical stress. United Downs retains the existing 0 K / 40 K strength-calibration cases; these labels do not specify a newly applied cooling intervention. These 13 selected scenarios are not samples from a probability distribution. Eight of nine and two of four count the cases with an open target drilling interval. They do not estimate a probability of successful drilling. All verdicts refer to this programme and these assumptions.

Independent programme failures

The bounds below combine the pressure constraints across the evaluated depths, states and cases. They are expressed as surface SG at 20 °C; width is upper minus lower. A negative width means the required minimum density exceeds the permitted maximum. Both sites remain NO-GO for this programme and these assumptions.

Site and state Lower / upper, surface SG Width, SG
Soultz drilling 1.37892 / 1.31256 -0.06637
Soultz trip 1.44362 / 1.36461 -0.07901
United Downs drilling 1.33132 / 1.28519 -0.04613
United Downs trip 1.40134 / 1.36503 -0.03631

Tool peaks, drilling / connection / best attempted run-in: Soultz: 197.0 / 197.3 / 201.2 °C; United Downs: 205.7 / 206.1 / 224.5 °C. The limit is 200 °C. Best attempted means the lowest peak among the schedules searched. A wider search could find a lower one. Soultz's reference FORGE-practice run-in reaches 214.5 °C, separately from the 201.2 °C search result.

Reference-practice coating run-in maxima are 274.3 °C at Soultz and 287.4 °C at United Downs, against the stated 204 °C rating. Both retain INDETERMINATE qualification. The coating histories are not necessarily those of the best attempted tool schedule.

Soultz's 0.017 SG-equivalent target drilling deficit and 1.2 °C tool excess are local facts. They do not measure how close the entire programme is to passing: incompatible density requirements elsewhere in the hole and coating qualification remain independent issues.

Sources: Soultz reference, United Downs reference, and settings-matched L4 base trials for Soultz and United Downs. The summary, also available as a two-page PDF, gives the findings and open questions together.

Breakout timing

Whether breakouts form as soon as the rock is exposed, or take time to form, decides whether a drilling mud weight window exists at Soultz and United Downs. See Breakout timing for the criterion, the results and how to reproduce them.

Design comparisons

No evaluated individual design setting or evaluated pair made either deep site's programme pass. Deeper casing gives Soultz an allowable trip-fluid density range while drilling and tools still fail. Lower viscosity can give United Downs an allowable drilling-fluid density range while other gates still fail. Stronger insulation cools tools but leaves pressure and pump constraints.

Only one pair per site was evaluated, and continuous searches sampled settings. The design study gives the tested settings, remaining failures and equipment-availability evidence. It establishes no complete operating envelope or general impossibility.

Models and evidence

The circulation model solves the downgoing and returning fluid temperatures with frictional heating and heat transfer through the pipe, casing and surrounding rock. Rock conduction carries each depth through its exposure and circulation pauses. Fluid properties and pressure losses feed back into the stability and tool calculations.

Model or check Role Evidence and detail
Circulation Fluid temperatures, heat transfer and hydraulics Utah FORGE comparisons and published-model benchmark
Rock reheating Temperature recovery when circulation stops Analytic checks and the limits of the FORGE pause comparison
Borehole stability Breakout width and pressure requirements UD-1 strength calibration and other well checks
Spallation, drilling rate and creep Exploratory estimates of quench effects and closure Physical models and their limits

The circulation/FORGE comparisons, strength calibration and other checks have distinct scopes. They do not validate a complete 10-13 km drilling programme. Full derivations and diagnostic figures are in the physical-model guide; the bibliography, material properties and site inputs retain their sources.

Scope and limitations

BoreTHM screens a stated drilling programme. A passing result is conditional on the modeled inputs and checks; a failure does not settle whether a different design or existing technology could drill the site. Reservoir production and detailed well-integrity design are outside the assessments.

The deep targets lie well below measured stress data. Strength calibration depends on the assumed stress profile, and the reference mud's rheology and constant barite properties are approximations. Full-cycle qualification of insulated pipe and managed-pressure equipment remains unresolved for the hot conditions studied.

Immediate exposure and the skin heuristic prevent cooling from reducing the initial drilling demand in the base model. The failure-delay experiments test hypotheses that no data yet support. They give no evidence that breakouts wait an hour to form. Near-bit pre-cooling and breakout growth remain separate open questions.

The base deep-site verdicts remain NO-GO for this programme and these assumptions across the A1-A9 comparisons performed. These generally change one approximation at a time and do not cover every joint uncertainty. Coolant delivery, trip timing and fluid displacement are among the deferred approximations. Pannonian's historical 0.041 °C tool threshold remains numerically unresolved.

Tests and reproducibility

Run the fast suite in the activated environment:

python -m pytest

The default excludes physical regressions marked slow. To include the complete suite after building the water-property cache:

python -m pytest -m "slow or not slow"

Full physical runs can take an hour or more. Single-threaded BLAS avoids oversubscription during repeated solves; set OPENBLAS_NUM_THREADS=1, OMP_NUM_THREADS=1 and MKL_NUM_THREADS=1 before starting Python for those runs.

Saved reference outputs and numerical regression tables support comparison with the published calculations. The changelog records changes. Historical diagnostic figures use their stated programmes and should be interpreted with their captions.

Find your way around the repository

Location Contents
src/borethm/ Installed package, physical models and study modules
scripts/ Standalone diagnostic and figure scripts
benchmarks/ Reference dataset with inputs, expected outputs and tolerances
examples/ Site template and worked example
docs/ Reading guide, model use, science and historical records
src/borethm/data/ Packaged observations and input-source records
results/ Retained numerical evaluations and trial evidence
tests/ Unit checks and physical regressions, including fixed reference tables
figures/ Diagnostic and field-comparison figures

How to cite and data credits

Use CITATION.cff for the software citation. The scientific bibliography lists the scientific sources.

The benchmark dataset has a separate citation. Its DOI will be added after deposit on Zenodo.

The FORGE data come from the Geothermal Data Repository: well 16B drilling data and deep-well temperature surveys. The Newberry extracts come from well 55-29 stimulation data. These datasets are used under CC-BY 4.0. The UD-1 image interpretation contains NERC materials ©NERC 2024.

The FORGE and Newberry data guides describe the extracts and how to rebuild them. Other input sources are recorded alongside the corresponding data.

Questions and contributions

Use GitHub issues for questions and problem reports. See SUPPORT.md for what to include and CONTRIBUTING.md for development setup and proposing changes.

Licence

The code in src/, scripts/, tools/, tests/ and examples/ is released under the Apache License 2.0. The documentation, figures, results and summary PDF are released under CC BY 4.0. Data in src/borethm/data/ and benchmarks/data/ keep their source licences, as recorded in their data guides and in NOTICE. Releases up to v1.3.4 were published under the MIT licence.

Metadata

Release files for borethm 1.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for borethm 1.4.0
File Size Uploaded Provenance
borethm-1.4.0.tar.gz 837.6 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for borethm 1.4.0
File Interpreter ABI Platform
borethm-1.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.7 MB

Release files / borethm-1.4.0.tar.gz

Download URL borethm-1.4.0.tar.gz
Size 837.6 kB
Tags Source
SHA-256 checksum
How to use checksums
b58ebdadf8ed0f9d43053c472f810d7ef2abec15ef23fd0b8911b302376158a9
BLAKE2b-256 checksum
How to use checksums
eec8eb48a164275bfb95e3961a0c4f207c3ad2cb3fa46a3dd42d99299c9c2949
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Release files / borethm-1.4.0-py3-none-any.whl

Download URL borethm-1.4.0-py3-none-any.whl
Size 854.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cfed7f360017d7ac11b8d7bdc512dead84552e44aa36c82a4b118b7f393d9704
BLAKE2b-256 checksum
How to use checksums
3de3c586dedad08f28c24e5b712803b89d46900d224350ff9ecbfc23a98570c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Security for borethm 1.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for borethm-1.4.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page