gea-program 0.5.0__tar.gz → 0.7.0__tar.gz

{gea_program-0.5.0/gea_program.egg-info → gea_program-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gea-program
-Version: 0.5.0
+Version: 0.7.0
 Summary: GEA-Program: downhole gauge monitoring - canonical measurement records, quality rules, drift evaluation with a re-fit change log, well-test validation, alarm management, model cards, store-and-forward, monthly SLA measurement, FAT/SAT protocols and a dashboard, generated from live objects in the client's reporting outline.
 Author: Daniel T. Murphy
 License: MPL-2.0
@@ -98,8 +98,22 @@ reaches a client document. Nothing unmeasured is ever reported as met.
   lines above the local floor out, and the detectability test: one station's
   record against a list of known rigs with positions and working windows,
   verdict per rig, the detection radius bracketed between the farthest rig
-  heard and the nearest not heard. The decoder is proven against records
-  written by libmseed. See *The second leg*.
+  heard and the nearest not heard. The instrument response (`seismic_response.py`):
+  the station's StationXML read into its stages, evaluated as evalresp does,
+  removed with a water level - counts to m/s, m or m/s^2. The decoder is proven
+  against libmseed on a corpus of real-station files; the response against
+  evalresp on a real IRIS channel. The array step (`seismic_array.py`):
+  beamforming over a slowness grid with the array response function's width
+  beside every bearing, the crossing of bearings from several arrays with its
+  ellipse, location from lags with the velocity named as an input, and the
+  array's detectability test - did it point at each known rig. On a site the
+  leg lives on the dashboard: a Seismic page where a station or an array is
+  added by upload with its rigs list and station file, refreshed as a job,
+  and read - spectrum, lines, verdicts, bearing - with its Seismic Station
+  Report under Reports; and the SAR panel on that page, a control panel and a
+  screen that plays the leg's arithmetic forward in time on the labelled
+  synthetic scene (`seismic_film.py`), every frame stamped SIMULATION_SELF_TEST.
+  See *The second leg*.
 
 ## Quick start
 
@@ -111,8 +125,8 @@ gea dashboard --catalog-well volve_f12_f14_production_excerpt:15/9-F-12:10000 --
 gea client-report --report accuracy --out client_report
 gea model-cards --out model_cards
 gea sbom --out sbom
-gea accept                     # the product gate (246 checks)
-gea help drift                 # the help library, by the job (15 pages; the same text is on every dashboard page)
+gea accept                     # the product gate (266 checks)
+gea help drift                 # the help library, by the job (16 pages; the same text is on every dashboard page)
 gea guide                      # the click-by-click tester guide (docs/TESTER_GUIDE.md)
 gea gui                        # the desktop window (pip install "gea-program[desktop]")
 gea workspace --path C:\site --action init --name "Pad 3"     # a site folder
@@ -240,10 +254,10 @@ text: JSON, JSON lines, CSV, Markdown, HTML.
 
 ### The help library
 
-`gea help` lists fifteen pages indexed by the job a reader arrives with -
+`gea help` lists sixteen pages indexed by the job a reader arrives with -
 start, bring data in, quality rules, drift, well tests, alarms and the month,
 the site, instruments, shut-ins and build-ups, seismic (the second leg),
-patches, files, notifications, which code is running, upkeep. Each page carries four lines and stops: the
+patches, files, notifications, which code is running, audit / update, upkeep. Each page carries four lines and stops: the
 command, what it writes, the one number to check, and what the page will not
 call a measurement. The pages ship inside the package (`gea/help/`), and the
 same text is what `/api/help` serves and what the dashboard shows under every
@@ -309,7 +323,60 @@ produces the standard spectral products: the Welch PSD, a spectrogram, and
 the lines that persist above a running-median floor in the band where rig
 machinery sits (1-50 Hz by default). The decoder is proven in the acceptance
 suite against records written by libmseed, the format's reference
-implementation (`gea/reference/`).
+implementation (`gea/reference/`), and `tools/seismic_reader_check.py` runs it
+against libmseed on about ninety real-station files of every encoding and
+byte order (the obspy test corpus, fetched with pip, never redistributed):
+every time-series file sample-exact.
+
+Physical units come from the station's own response file. `gea seismic
+--action remove-response --stationxml station.xml` reads the FDSN StationXML
+the archives serve beside the data (`fetch --with-response` fetches it),
+builds the response from its stages - the poles and zeros of the sensor, the
+gain of each stage, the FIR and IIR coefficients of the digitizer with their
+delay corrections - the way evalresp builds it, and removes it in the
+frequency domain with a water level and a pre-filter, giving velocity,
+displacement or acceleration in SI units. The acceptance suite holds the
+evaluation to evalresp's numbers on a real IRIS channel (IU.ANMO.10.BHZ,
+`gea/reference/`) to one part in a hundred thousand. A station file whose
+stages disagree with their own declared sensitivity, a polynomial stage, a
+channel the file does not cover: refused with the reason, never patched, and
+the record stays in counts, labelled.
+
+One station detects; an array gives a direction. `gea seismic --action beam`
+takes three or more sensors' records with their positions and returns the
+back-azimuth and slowness the band's energy crossed the array with, by
+frequency-domain beamforming over a slowness grid (the conventional Bartlett
+beam, or Capon), refined around its maximum - and, beside the bearing, the
+array response function's half-power width, which is the resolution the
+geometry allows at that band, and whether the geometry has aliasing lobes
+there, so a lone peak is not mistaken for a source. `--action array-detect`
+is the array's form of the detectability test: for each rig on the
+ground-truth list, in the windows it worked alone, did the array point at it
+within its own tolerance (POINTED, NOT_POINTED, INCOHERENT). `--action
+locate` crosses the bearings of two or more arrays, weighted by their
+uncertainties, and returns the point with its 1-sigma ellipse, the crossing
+angle and the residual of each bearing; a location from station-pair lags is
+there too, with the medium velocity it needs named as the input it is. On
+the labelled synthetic scene (`--action array-selftest`) a 1.2 km,
+nine-sensor array points at rigs from 6 to 45 km within 0.3 degrees against
+a 7-degree tolerance, and three arrays' bearings cross within a kilometre of
+the rig. What none of it claims: a position from one array, a bearing to a
+source nearer than five apertures, a direction finer than the array response
+function, or a velocity that was not measured.
+
+On a site the leg is a page. Seismic, beside Wells: a station (one record)
+or an array (one record per sensor and a sensors CSV) is added by upload with
+its position, its rigs list and, when there is one, its StationXML, and lives
+under `seismic/<station>/` in the workspace with its files copied in verbatim
+and hashed. Refresh - a button, or `gea workspace --action refresh-seismic`,
+and like every other action a job with its log - reads the record, removes
+the response when the station file is there, writes the spectrum, the
+persistent lines, the detectability verdicts and, for an array, the beam and
+the array verdicts under `reports/seismic/<station>/`, and the Seismic
+Station Report beside them; the station page draws the spectrum and shows
+the tables with the limits printed under each. The home page counts the
+stations and the listed rigs heard. The sample report is in
+`docs/report_samples/`.
 
 The first number is the detectability test (`--action detect`): one station's
 continuous record, the station's position, and a CSV of known rigs - position
@@ -330,6 +397,70 @@ a rig not on the list, and any quantity in physical units until a station's
 response has been applied and named. `--action selftest` runs the test on a
 synthetic scene and labels its output SIMULATION_SELF_TEST.
 
+The SAR panel at the foot of the Seismic page is the control panel and the
+screen. "Run the scene" is `gea workspace --action sar-film` as a job: the
+labelled synthetic array scene, one frame per window, written under
+`reports/seismic/SIMULATION/`. The screen plays it - the trace, the
+spectrogram column arriving, the beam power map on the slowness grid swinging
+onto the working rig, the map with the bearing and the array's tolerance
+wedge against the rigs where the scene put them, the tally per rig, and at
+the end the array detectability test's verdict on the whole scene, the same
+function a real record goes through. Every frame carries SIMULATION_SELF_TEST
+and the line "not a measurement of any ground"; a real record is refreshed on
+its station and the page shows what it earned, never a film. `gea seismic
+--action sar-film --out film.json` writes the same film from the command line.
+
+### Tracks - the time dimension
+
+The array step gives one bearing for one window. `seismic_track.py` runs it
+window after window: a bearing history per array (a bearing with the array's
+own tolerance where the beam was coherent, a gap where it was not, change
+points where the bearing moved beyond the tolerance), a position history from
+two or more arrays crossed window by window (a position only where two or
+more arrays were coherent, the bearings crossed at 15 degrees or more and the
+point lies in front of every array - every other window a gap with its
+reason), and the track: the principal line through the longest continuous
+segment of positions, with its heading, length and rate, the ellipses beside
+every point, and segments listed apart where positions jump farther than
+their ellipses allow (a coherent background crossing in a quiet hour is not
+the rig an hour later). The verdict against ground truth - the lateral's
+surveyed points or a permit's surface hole with its date, interpolated to
+each position's time - is TRACKED, PARTIAL, NOT_TRACKED or INSUFFICIENT, with
+the fraction and the heading difference printed. The labelled scene behind
+`--action track-selftest` is a bit advancing along a straight lateral past
+two arrays. On a site a track is two or more array stations and an optional
+truth CSV, refreshed as a job into the Seismic Track Report; the track view
+shows the map with every position's ellipse, a slider through time and the
+bearings over time, and the SAR panel's second scene plays the same thing
+forward with the track drawn as it is earned.
+
+Ground truth from a permit export: `gea permits --file export.csv --out
+rigs.csv --within LAT LON KM` finds the columns of a regulator's query (an
+identifier, a surface position, a spud or approval date) by name, with a
+mapping file when the guesses are wrong, and writes the rigs CSV the tests
+read beside an import note that says which columns were used, how many rows
+were dropped and why, and how many end dates it assumed (a permit rarely says
+when drilling stopped). The Seismic page's add form takes a permit export in
+place of the rigs CSV and keeps both.
+
+### Audit / Update
+
+The Audit / Update tab holds three things. The whole audit log
+(`records/audit.jsonl`) with filters by who, by action and since a date, and
+a CSV download - Administration keeps the last hundred lines and points here.
+The program card: the running version and code path, the newest release on
+PyPI (`current`, `behind`, or `PyPI not reachable` when the machine is
+offline), which extras are installed here, and links to PyPI, the releases
+with the install kits, and the CHANGELOG; "Update the program from PyPI"
+(admin) is `gea update` as a job - pip --upgrade from the same Python, after
+which the service must be restarted; the program never restarts itself, and
+an offline kit is updated by installing the newer kit. The data card: every
+report against its source - `current` or `stale` when the source changed
+after the report was written - and "Update every report from its source"
+(operator), which is `gea workspace --action refresh-all` as a job: the
+dashboard for every well, then every seismic station, errors collected and
+listed, never hidden.
+
 ### Before a site goes live
 
 `deploy/README.md` is the checklist: keep the service on the loopback
@@ -377,12 +508,13 @@ attaches the zips to the GitHub release of that tag.
 gea/            the package: engines, record layer, reports, monitor, dashboard, cli, shell, acceptance suite,
                 workspace, jobs, service, patches and web/app.html (the served dashboard)
 gea/catalog/    52 public archive entries, each with a provenance file
-gea/reference/  miniSEED records written by libmseed, with their provenance: the decoder's independent reference
+gea/reference/  miniSEED records written by libmseed and an IRIS StationXML with evalresp's numbers, with provenance: the independent references
 docs/report_samples/  one rendered example of every client report, from this build (tools/render_report_samples.py; SAMPLES.md names each command)
 docs/           TESTER_GUIDE.md, REQUIREMENTS_MATRIX.md (the scope-of-work mirror that shaped the reports), examples/ (port configs),
                 SESSION_LOG.md (the working record, session by session),
                 commercial/ (pilot proposal, bench readiness, commercial use), HISTORY.md (the ship-by-ship record)
-tools/          standalone_check.py (the self-contained guard; run by ci and ship.ps1), build_installer.py (the kit)
+tools/          standalone_check.py (the self-contained guard; run by ci and ship.ps1), build_installer.py (the kit),
+                render_report_samples.py (docs/report_samples), seismic_reader_check.py (the reader against libmseed)
 CHANGELOG.md    per-release summary (a tag ships only with its section); SHIP_LOG.md is written by ship.ps1
 tests/          pytest wrapper around the acceptance suite and the standalone check
 ```

{gea_program-0.5.0 → gea_program-0.7.0}/README.md

@@ -59,8 +59,22 @@ reaches a client document. Nothing unmeasured is ever reported as met.
   lines above the local floor out, and the detectability test: one station's
   record against a list of known rigs with positions and working windows,
   verdict per rig, the detection radius bracketed between the farthest rig
-  heard and the nearest not heard. The decoder is proven against records
-  written by libmseed. See *The second leg*.
+  heard and the nearest not heard. The instrument response (`seismic_response.py`):
+  the station's StationXML read into its stages, evaluated as evalresp does,
+  removed with a water level - counts to m/s, m or m/s^2. The decoder is proven
+  against libmseed on a corpus of real-station files; the response against
+  evalresp on a real IRIS channel. The array step (`seismic_array.py`):
+  beamforming over a slowness grid with the array response function's width
+  beside every bearing, the crossing of bearings from several arrays with its
+  ellipse, location from lags with the velocity named as an input, and the
+  array's detectability test - did it point at each known rig. On a site the
+  leg lives on the dashboard: a Seismic page where a station or an array is
+  added by upload with its rigs list and station file, refreshed as a job,
+  and read - spectrum, lines, verdicts, bearing - with its Seismic Station
+  Report under Reports; and the SAR panel on that page, a control panel and a
+  screen that plays the leg's arithmetic forward in time on the labelled
+  synthetic scene (`seismic_film.py`), every frame stamped SIMULATION_SELF_TEST.
+  See *The second leg*.
 
 ## Quick start
 
@@ -72,8 +86,8 @@ gea dashboard --catalog-well volve_f12_f14_production_excerpt:15/9-F-12:10000 --
 gea client-report --report accuracy --out client_report
 gea model-cards --out model_cards
 gea sbom --out sbom
-gea accept                     # the product gate (246 checks)
-gea help drift                 # the help library, by the job (15 pages; the same text is on every dashboard page)
+gea accept                     # the product gate (266 checks)
+gea help drift                 # the help library, by the job (16 pages; the same text is on every dashboard page)
 gea guide                      # the click-by-click tester guide (docs/TESTER_GUIDE.md)
 gea gui                        # the desktop window (pip install "gea-program[desktop]")
 gea workspace --path C:\site --action init --name "Pad 3"     # a site folder
@@ -201,10 +215,10 @@ text: JSON, JSON lines, CSV, Markdown, HTML.
 
 ### The help library
 
-`gea help` lists fifteen pages indexed by the job a reader arrives with -
+`gea help` lists sixteen pages indexed by the job a reader arrives with -
 start, bring data in, quality rules, drift, well tests, alarms and the month,
 the site, instruments, shut-ins and build-ups, seismic (the second leg),
-patches, files, notifications, which code is running, upkeep. Each page carries four lines and stops: the
+patches, files, notifications, which code is running, audit / update, upkeep. Each page carries four lines and stops: the
 command, what it writes, the one number to check, and what the page will not
 call a measurement. The pages ship inside the package (`gea/help/`), and the
 same text is what `/api/help` serves and what the dashboard shows under every
@@ -270,7 +284,60 @@ produces the standard spectral products: the Welch PSD, a spectrogram, and
 the lines that persist above a running-median floor in the band where rig
 machinery sits (1-50 Hz by default). The decoder is proven in the acceptance
 suite against records written by libmseed, the format's reference
-implementation (`gea/reference/`).
+implementation (`gea/reference/`), and `tools/seismic_reader_check.py` runs it
+against libmseed on about ninety real-station files of every encoding and
+byte order (the obspy test corpus, fetched with pip, never redistributed):
+every time-series file sample-exact.
+
+Physical units come from the station's own response file. `gea seismic
+--action remove-response --stationxml station.xml` reads the FDSN StationXML
+the archives serve beside the data (`fetch --with-response` fetches it),
+builds the response from its stages - the poles and zeros of the sensor, the
+gain of each stage, the FIR and IIR coefficients of the digitizer with their
+delay corrections - the way evalresp builds it, and removes it in the
+frequency domain with a water level and a pre-filter, giving velocity,
+displacement or acceleration in SI units. The acceptance suite holds the
+evaluation to evalresp's numbers on a real IRIS channel (IU.ANMO.10.BHZ,
+`gea/reference/`) to one part in a hundred thousand. A station file whose
+stages disagree with their own declared sensitivity, a polynomial stage, a
+channel the file does not cover: refused with the reason, never patched, and
+the record stays in counts, labelled.
+
+One station detects; an array gives a direction. `gea seismic --action beam`
+takes three or more sensors' records with their positions and returns the
+back-azimuth and slowness the band's energy crossed the array with, by
+frequency-domain beamforming over a slowness grid (the conventional Bartlett
+beam, or Capon), refined around its maximum - and, beside the bearing, the
+array response function's half-power width, which is the resolution the
+geometry allows at that band, and whether the geometry has aliasing lobes
+there, so a lone peak is not mistaken for a source. `--action array-detect`
+is the array's form of the detectability test: for each rig on the
+ground-truth list, in the windows it worked alone, did the array point at it
+within its own tolerance (POINTED, NOT_POINTED, INCOHERENT). `--action
+locate` crosses the bearings of two or more arrays, weighted by their
+uncertainties, and returns the point with its 1-sigma ellipse, the crossing
+angle and the residual of each bearing; a location from station-pair lags is
+there too, with the medium velocity it needs named as the input it is. On
+the labelled synthetic scene (`--action array-selftest`) a 1.2 km,
+nine-sensor array points at rigs from 6 to 45 km within 0.3 degrees against
+a 7-degree tolerance, and three arrays' bearings cross within a kilometre of
+the rig. What none of it claims: a position from one array, a bearing to a
+source nearer than five apertures, a direction finer than the array response
+function, or a velocity that was not measured.
+
+On a site the leg is a page. Seismic, beside Wells: a station (one record)
+or an array (one record per sensor and a sensors CSV) is added by upload with
+its position, its rigs list and, when there is one, its StationXML, and lives
+under `seismic/<station>/` in the workspace with its files copied in verbatim
+and hashed. Refresh - a button, or `gea workspace --action refresh-seismic`,
+and like every other action a job with its log - reads the record, removes
+the response when the station file is there, writes the spectrum, the
+persistent lines, the detectability verdicts and, for an array, the beam and
+the array verdicts under `reports/seismic/<station>/`, and the Seismic
+Station Report beside them; the station page draws the spectrum and shows
+the tables with the limits printed under each. The home page counts the
+stations and the listed rigs heard. The sample report is in
+`docs/report_samples/`.
 
 The first number is the detectability test (`--action detect`): one station's
 continuous record, the station's position, and a CSV of known rigs - position
@@ -291,6 +358,70 @@ a rig not on the list, and any quantity in physical units until a station's
 response has been applied and named. `--action selftest` runs the test on a
 synthetic scene and labels its output SIMULATION_SELF_TEST.
 
+The SAR panel at the foot of the Seismic page is the control panel and the
+screen. "Run the scene" is `gea workspace --action sar-film` as a job: the
+labelled synthetic array scene, one frame per window, written under
+`reports/seismic/SIMULATION/`. The screen plays it - the trace, the
+spectrogram column arriving, the beam power map on the slowness grid swinging
+onto the working rig, the map with the bearing and the array's tolerance
+wedge against the rigs where the scene put them, the tally per rig, and at
+the end the array detectability test's verdict on the whole scene, the same
+function a real record goes through. Every frame carries SIMULATION_SELF_TEST
+and the line "not a measurement of any ground"; a real record is refreshed on
+its station and the page shows what it earned, never a film. `gea seismic
+--action sar-film --out film.json` writes the same film from the command line.
+
+### Tracks - the time dimension
+
+The array step gives one bearing for one window. `seismic_track.py` runs it
+window after window: a bearing history per array (a bearing with the array's
+own tolerance where the beam was coherent, a gap where it was not, change
+points where the bearing moved beyond the tolerance), a position history from
+two or more arrays crossed window by window (a position only where two or
+more arrays were coherent, the bearings crossed at 15 degrees or more and the
+point lies in front of every array - every other window a gap with its
+reason), and the track: the principal line through the longest continuous
+segment of positions, with its heading, length and rate, the ellipses beside
+every point, and segments listed apart where positions jump farther than
+their ellipses allow (a coherent background crossing in a quiet hour is not
+the rig an hour later). The verdict against ground truth - the lateral's
+surveyed points or a permit's surface hole with its date, interpolated to
+each position's time - is TRACKED, PARTIAL, NOT_TRACKED or INSUFFICIENT, with
+the fraction and the heading difference printed. The labelled scene behind
+`--action track-selftest` is a bit advancing along a straight lateral past
+two arrays. On a site a track is two or more array stations and an optional
+truth CSV, refreshed as a job into the Seismic Track Report; the track view
+shows the map with every position's ellipse, a slider through time and the
+bearings over time, and the SAR panel's second scene plays the same thing
+forward with the track drawn as it is earned.
+
+Ground truth from a permit export: `gea permits --file export.csv --out
+rigs.csv --within LAT LON KM` finds the columns of a regulator's query (an
+identifier, a surface position, a spud or approval date) by name, with a
+mapping file when the guesses are wrong, and writes the rigs CSV the tests
+read beside an import note that says which columns were used, how many rows
+were dropped and why, and how many end dates it assumed (a permit rarely says
+when drilling stopped). The Seismic page's add form takes a permit export in
+place of the rigs CSV and keeps both.
+
+### Audit / Update
+
+The Audit / Update tab holds three things. The whole audit log
+(`records/audit.jsonl`) with filters by who, by action and since a date, and
+a CSV download - Administration keeps the last hundred lines and points here.
+The program card: the running version and code path, the newest release on
+PyPI (`current`, `behind`, or `PyPI not reachable` when the machine is
+offline), which extras are installed here, and links to PyPI, the releases
+with the install kits, and the CHANGELOG; "Update the program from PyPI"
+(admin) is `gea update` as a job - pip --upgrade from the same Python, after
+which the service must be restarted; the program never restarts itself, and
+an offline kit is updated by installing the newer kit. The data card: every
+report against its source - `current` or `stale` when the source changed
+after the report was written - and "Update every report from its source"
+(operator), which is `gea workspace --action refresh-all` as a job: the
+dashboard for every well, then every seismic station, errors collected and
+listed, never hidden.
+
 ### Before a site goes live
 
 `deploy/README.md` is the checklist: keep the service on the loopback
@@ -338,12 +469,13 @@ attaches the zips to the GitHub release of that tag.
 gea/            the package: engines, record layer, reports, monitor, dashboard, cli, shell, acceptance suite,
                 workspace, jobs, service, patches and web/app.html (the served dashboard)
 gea/catalog/    52 public archive entries, each with a provenance file
-gea/reference/  miniSEED records written by libmseed, with their provenance: the decoder's independent reference
+gea/reference/  miniSEED records written by libmseed and an IRIS StationXML with evalresp's numbers, with provenance: the independent references
 docs/report_samples/  one rendered example of every client report, from this build (tools/render_report_samples.py; SAMPLES.md names each command)
 docs/           TESTER_GUIDE.md, REQUIREMENTS_MATRIX.md (the scope-of-work mirror that shaped the reports), examples/ (port configs),
                 SESSION_LOG.md (the working record, session by session),
                 commercial/ (pilot proposal, bench readiness, commercial use), HISTORY.md (the ship-by-ship record)
-tools/          standalone_check.py (the self-contained guard; run by ci and ship.ps1), build_installer.py (the kit)
+tools/          standalone_check.py (the self-contained guard; run by ci and ship.ps1), build_installer.py (the kit),
+                render_report_samples.py (docs/report_samples), seismic_reader_check.py (the reader against libmseed)
 CHANGELOG.md    per-release summary (a tag ships only with its section); SHIP_LOG.md is written by ship.ps1
 tests/          pytest wrapper around the acceptance suite and the standalone check
 ```

{gea_program-0.5.0 → gea_program-0.7.0}/gea/__init__.py

@@ -100,6 +100,8 @@ from .seismic import (
     welch_psd, spectrogram, persistent_lines, band_power,
 )
 from .seismic_detect import Source as SeismicSource, detectability_test, load_sources_csv, haversine_km, DRILLING_BAND_HZ
+from .seismic_response import read_stationxml, remove_response, transfer as response_transfer, fdsn_stationxml
+from .seismic_array import Sensor as SeismicSensor, load_sensors_csv, beam as array_beam, array_detectability, intersect_backazimuths, locate_from_lags
 from .bench import (
     bench_analysis, bench_selftest,
 )
@@ -120,7 +122,7 @@ from .profile_catalog import (
     read_pangaea_txt,
 )
 
-__version__ = "0.5.0"
+__version__ = "0.7.0"
 __all__ = [
     "aging_rate", "rate_psi_yr", "accuracy_psi",
     "Sensor", "SimulatorConfig", "DownholeEngine",