Open tools / reproducible examples

Make Lagging Theory and transformation uncertainty testable.

The list below separates public teaching demos, selected research code, archival analytical code, and collaboration routes. Some working repositories remain private while manuscripts, data permissions, or documentation are still pending.

Tool index

Browse by maturity and use case.

Each entry states its problem, intended use, and scope.

Public demonstrator

Normalized LDL response animation

teaching demo

A browser-computed normalized response showing how the drawdown-gradient lag (τ_s) exceeding the flux lag (τ_q) can produce an S-like transition.

Problem
Shows why Lagging Darcy Law differs from a visual time shift and how response shape can change before parameter transfer.
Use when
Use as a first explanation for collaborators, students, reviewers, or technical teams that need a concrete LDL calculation.
Scope
Simplified line-source teaching implementation without wellbore storage or skin; it is not calibrated for field analysis.
Evidence
The public demonstration uses a normalized Lin-Yeh special case.
Lagging Darcy Lawnormalized responseteaching calculation
Public demonstrator

Lagging pumping-test diagnostic demo

teaching demo

An interactive constant-rate pumping-test example comparing a Classical Darcy response and a lag-aware response.

Problem
Shows when separated flux and gradient response lags can create early-time residual structure and timing shifts.
Use when
Use before a technical discussion about whether a pumping test needs lag-aware interpretation.
Scope
Calculation-backed teaching model that omits wellbore storage and finite well radius. Site-specific analysis is required before design use.
Evidence
The demonstration is available from the home page and the Lagging Theory page.
pumping testearly residualmodel-form check
Public demonstrator

Lagging Darcy Law Necessity Checker

teaching demo

A qualitative screening tool for deciding whether lag-aware aquifer-test interpretation should be evaluated before informing engineering decisions.

Problem
Turns pumping duration, observation window, recovery duration, lag or drainage scale, boundary response, residual-structure severity, and decision type into a screening result.
Use when
Use when a team needs a quick decision about whether conventional interpretation is enough for a first screen.
Scope
Qualitative screening only; it does not perform quantitative aquifer-test inversion or site-specific engineering calculation.
Evidence
Available on the Decision Lab page.
screeningdecision variablelag-aware interpretation
Research code

TRUST-TC

research release

MIT-licensed Python research tool for transformation-uncertainty intervals in thermal response test interpretation.

Problem
Converts apparent TRT estimates into uncertainty intervals, reliability classes, and geothermal design reference factors.
Use when
Use when TRT interpretation needs explicit transformation uncertainty before shallow-geothermal design transfer.
Scope
The public repository contains software, documentation, tests, a calibration table, and small examples. It does not include raw field data.
Evidence
Repository documentation is current as of 2026-06-20.
Python MIT
TRTthermal conductivitytransformation uncertainty
Archival code

Mathematica stream-depletion code

archival artifact

Mathematica notebook for evaluating drawdown values in a new stream-depletion solution.

Problem
Keeps an analytical well-hydraulics computation visible for readers who need to inspect older solution code.
Use when
Use for archival Mathematica evaluation of the linked stream-depletion solution.
Scope
Archival notebook; it is not maintained as an open-source release.
Evidence
Repository documentation is current as of 2026-06-20.
Mathematica No license asserted in GitHub metadata
stream depletionMathematicaanalytical solution
Archival code

ApproximateAnaFlow

archival artifact

Python scripts for approximate Zech solutions under constant-rate and constant-head pumping in confined aquifers.

Problem
Provides earlier analytical-flow calculation scripts for confined-aquifer pumping cases.
Use when
Use for inspecting earlier approximate analytical-flow implementations.
Scope
Standalone scripts; they are not a maintained Python release or validated design calculator.
Evidence
Repository documentation is current as of 2026-06-20.
Python No license asserted in GitHub metadata
confined aquiferZech solutionPython scripts
Collaboration route

Groundwater Model-Assumption and Decision Audit

service route

A structured review of whether data, aquifer-test interpretation models, uncertainty propagation, and decision variables support a groundwater action.

Problem
Connects analysis tools to project decisions while preserving the confidentiality of project datasets and the stated scope of public demonstrations.
Use when
Use when a consultant, industrial team, or agency needs a bounded pilot before a larger groundwater or subsurface-energy study.
Scope
Applied collaboration route; it is not open-source software and does not replace engineering judgment.
Evidence
Published service route on this website.
model assumptionsauditpilot analysis
Scope

What the labels mean.

The labels keep teaching demos, research code, and applied services separate because groundwater decisions depend on model-specific evidence.

Teaching demo

For explanation, not design calculation.

Browser demos show mechanisms and interpretation sensitivity. They do not replace a calibrated aquifer-test analysis or site-specific uncertainty propagation.

Selected research code

For inspection and reproduction.

Selected research code shares examples, tests, or documentation without forcing readers into unpublished manuscript details. Assumptions still control where results can transfer.

Collaboration route

For confidential or decision-bound work.

When project data are sensitive or decisions are high-stakes, the correct output is a scoped audit or pilot analysis rather than a public demo.

Next step

Bring a dataset, a decision variable, and the analytical model currently being used.

Collaboration begins when an existing pumping test, recovery curve, TRT record, or model output must support a decision. The tools above provide public inspection; the technical work begins with the assumptions behind the data.

Send a technical brief