gea-program 0.80.0__tar.gz → 0.81.0__tar.gz

{gea_program-0.80.0/gea_program.egg-info → gea_program-0.81.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gea-program
-Version: 0.80.0
+Version: 0.81.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
@@ -483,7 +483,10 @@ a dip across the plan line as well as along it, the hole is placed by
 minimum curvature through the surveys' azimuths, the corridor the lease
 and the offset wells leave the hole is in the twin and on the screen's
 plan view, and the config's model carries the plan's azimuth, the cross
-dip and the corridor. Every recommendation, answer and
+dip and the corridor. A vibration index read off the surface torque,
+weight and hook load (since 0.81.0) stands in for the downhole tool a
+string does not carry, and the record says which the agent read. Every
+recommendation, answer and
 command is on record with its hash, and GEA pulls the records into the
 well from the **Drill string** tab's card (`gea workspace --path C:\site
 --action driller-pull --box http://192.168.1.60:8790 --well SWD-1`). The
@@ -837,7 +840,7 @@ unsigned, the key hand-overs - and shows the reports as they were signed. A
 reader made from the workspace knows the site's key fingerprints, so it
 says whether a dossier is the site's; it allows no network request, and it
 leaves the trusted time-stamp to `verify_dossier.py`. For a client who wants
-it installed, every release also carries `GEA-Reader-Setup-0.80.0.exe`: GEA
+it installed, every release also carries `GEA-Reader-Setup-0.81.0.exe`: GEA
 Reader as a Windows program of its own - its own icon and taskbar button,
 Check with GEA Reader on a dossier's right-click menu, fingerprints the client
 saves kept on that computer, nothing of GEA-Program. `gea help reader`.
@@ -1602,7 +1605,7 @@ attaches the zips to the GitHub release of that tag.
 
 ### The Windows installer
 
-Every release also carries `GEA-Program-Setup-0.80.0.exe` (for 0.80.0): the
+Every release also carries `GEA-Program-Setup-0.81.0.exe` (for 0.81.0): the
 same Windows kit installed like any Windows program, for the signed-in user
 alone and with no administrator rights (`%LOCALAPPDATA%\Programs\GEA-Program`).
 It asks for the site workspace (an existing one such as `C:\site` is used as
@@ -1621,7 +1624,7 @@ it, removes the program and leaves the workspace. Silent, for a site's
 software deployment:
 
 ```
-GEA-Program-Setup-0.80.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"
+GEA-Program-Setup-0.81.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"
 ```
 
 The setup is built by Inno Setup 6 from `tools/installer.iss` in the same

{gea_program-0.80.0 → gea_program-0.81.0}/README.md

@@ -444,7 +444,10 @@ a dip across the plan line as well as along it, the hole is placed by
 minimum curvature through the surveys' azimuths, the corridor the lease
 and the offset wells leave the hole is in the twin and on the screen's
 plan view, and the config's model carries the plan's azimuth, the cross
-dip and the corridor. Every recommendation, answer and
+dip and the corridor. A vibration index read off the surface torque,
+weight and hook load (since 0.81.0) stands in for the downhole tool a
+string does not carry, and the record says which the agent read. Every
+recommendation, answer and
 command is on record with its hash, and GEA pulls the records into the
 well from the **Drill string** tab's card (`gea workspace --path C:\site
 --action driller-pull --box http://192.168.1.60:8790 --well SWD-1`). The
@@ -798,7 +801,7 @@ unsigned, the key hand-overs - and shows the reports as they were signed. A
 reader made from the workspace knows the site's key fingerprints, so it
 says whether a dossier is the site's; it allows no network request, and it
 leaves the trusted time-stamp to `verify_dossier.py`. For a client who wants
-it installed, every release also carries `GEA-Reader-Setup-0.80.0.exe`: GEA
+it installed, every release also carries `GEA-Reader-Setup-0.81.0.exe`: GEA
 Reader as a Windows program of its own - its own icon and taskbar button,
 Check with GEA Reader on a dossier's right-click menu, fingerprints the client
 saves kept on that computer, nothing of GEA-Program. `gea help reader`.
@@ -1563,7 +1566,7 @@ attaches the zips to the GitHub release of that tag.
 
 ### The Windows installer
 
-Every release also carries `GEA-Program-Setup-0.80.0.exe` (for 0.80.0): the
+Every release also carries `GEA-Program-Setup-0.81.0.exe` (for 0.81.0): the
 same Windows kit installed like any Windows program, for the signed-in user
 alone and with no administrator rights (`%LOCALAPPDATA%\Programs\GEA-Program`).
 It asks for the site workspace (an existing one such as `C:\site` is used as
@@ -1582,7 +1585,7 @@ it, removes the program and leaves the workspace. Silent, for a site's
 software deployment:
 
 ```
-GEA-Program-Setup-0.80.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"
+GEA-Program-Setup-0.81.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"
 ```
 
 The setup is built by Inno Setup 6 from `tools/installer.iss` in the same

{gea_program-0.80.0 → gea_program-0.81.0}/gea/__init__.py

@@ -123,7 +123,7 @@ from .profile_catalog import (
     read_pangaea_txt,
 )
 
-__version__ = "0.80.0"
+__version__ = "0.81.0"
 __all__ = [
     "aging_rate", "rate_psi_yr", "accuracy_psi",
     "Sensor", "SimulatorConfig", "DownholeEngine",

{gea_program-0.80.0 → gea_program-0.81.0}/gea/acceptance_tests.py

@@ -16566,6 +16566,7 @@ def section_dv_driller(tmp: str) -> None:
             time.sleep(0.2)
         s_ov, _ = call("/api/answer", {"what": "override", "by": "tester", "note": "held", "override": {"build_deg_100ft": 0.0, "wob_klb": 25}})
         md = drl.feed.snapshot()["state"]["hole_depth"]
+        drl.cfg["limits"]["vibration_index"] = 5.0                       # the section's end alone ends this arming: the vibration index the feed now derives (0.81.0) may cross 1.2 in the shale
         s_long, _ = call("/api/arm", {"by": "tester", "to_md": md + 5000})
         s_arm, armed = call("/api/arm", {"by": "tester", "to_md": md + 150})
         t_end = time.monotonic() + 30
@@ -17011,6 +17012,179 @@ def section_dx_third_dimension(tmp: str) -> None:
        "plan azimuth and cross dip go through" + (f" [failed: {', '.join(failed3)}]" if failed3 else ""))
 
 
+def section_dy_vibration(tmp: str) -> None:
+    """Section DY - the vibration index from the feed: the index off the surface channels (a steady feed near zero, a
+    torque swinging as the twin's limit swings it reading the limit, a weight swinging reading lateral, the statistics
+    path equal to the samples path, pooled statistics, a window without torque or weight reading nothing); on the twin
+    the derived index tracking the twin's own; the rig side (the twin as the rig publishing the surface channels and
+    no downhole index, the advisor reading the derived one and saying so, the downhole item winning, a feed with
+    neither reading none, the loop disarming on the derived index, the screen, the help); GEA's side (the lateral
+    file from the self-test export with the statistics, the replay reading the stick-slip stretch over the limit
+    and the advisor easing there, a record without the statistics unjudged, the card)."""
+    import http.cookiejar
+    import importlib
+    import math as _m
+    import urllib.error
+    import urllib.request
+    from . import driller_link as DL
+    from . import edr as E
+    from . import helplib as H
+    from .service import Service, Users
+    from .workspace import Workspace
+    pkg = Path(__file__).parent
+    d = Path(tmp, "dy"); d.mkdir()
+    prog = DL.program()
+    if prog is None:
+        ok(True, "DY the driller's program (gea-driller) is not installed beside GEA in this install; nothing to check here")
+        return
+    if prog["env"] and prog["env"] not in sys.path:
+        sys.path.insert(0, prog["env"])
+    T = importlib.import_module("gea_driller.twin"); V = importlib.import_module("gea_driller.vibration"); P = importlib.import_module("gea_driller.policy")
+    A = importlib.import_module("gea_driller.advisor"); C = importlib.import_module("gea_driller.config"); S = importlib.import_module("gea_driller.service")
+    R = importlib.import_module("gea_driller.rig"); SH = importlib.import_module("gea_driller.shadow")
+    np_ = importlib.import_module("numpy")
+    # -- DY1 the index --------------------------------------------------------------------------------------------------------
+    tt = np_.arange(60)
+    steady = {"torque": 10 + 0.02 * np_.sin(tt), "rpm": 120 + 0 * tt, "wob": 25 + 0.05 * np_.cos(tt), "hkld": 175 - 0.05 * np_.cos(tt), "spp": 2800 + 0 * tt}
+    ss = {"torque": 10 * (1 + 0.48 * np_.sin(2 * _m.pi * tt / 8)), "rpm": 120 + 0 * tt, "wob": 25 + 0 * tt, "hkld": 175 + 0 * tt, "spp": 2800 + 0 * tt}
+    lat = {"torque": 10 + 0 * tt, "rpm": 120 + 0 * tt, "wob": 25 * (1 + 0.24 * np_.sin(2 * _m.pi * tt / 5)), "hkld": 175 - 25 * 0.24 * np_.sin(2 * _m.pi * tt / 5), "spp": 2800 + 0 * tt}
+    v0 = V.index(steady); v1 = V.index(ss); v2 = V.index(lat)
+    v1s = V.index_from_stats(V.stats(ss))
+    pooled = V.index_from_stats(V.combine_stats([V.stats({k: v[:30] for k, v in ss.items()}), V.stats({k: v[30:] for k, v in ss.items()})]))
+    none = V.index({"rpm": 120 + 0 * tt, "spp": 2800 + 0 * tt})
+    short = V.index({k: v[:5] for k, v in ss.items()})
+    # on the twin: the derived index against the twin's own, step by step over twenty scenes
+    tr, de = [], []
+    for sd in range(20):
+        lt = T.Lateral(T.Scene(sd)); o = lt.reset()
+        while not lt.done:
+            o, _, _, inf = lt.step(T.textbook_action(o))
+            if inf.get("conditioning") != "drill":
+                continue
+            smp = [lt.surface_sample() for _ in range(20)]
+            v = V.index({"torque": [x["torque"] for x in smp], "rpm": [x["rpm"] for x in smp], "wob": [x["wob"] for x in smp], "hkld": [x["hookload"] for x in smp], "spp": [x["spp"] for x in smp]})
+            tr.append(lt.vib); de.append(v["index"])
+    tr_, de_ = np_.array(tr), np_.array(de)
+    corr = float(np_.corrcoef(tr_, de_)[0, 1]); agree = float(((tr_ > T.VIB_LIMIT) == (de_ > T.VIB_LIMIT)).mean())
+    c1 = {
+        "steady": v0 is not None and v0["index"] < 0.1,
+        "stick_slip": v1 is not None and abs(v1["index"] - 1.2) < 0.08 and v1["kind"] == "stick-slip" and abs(v1["torque_amplitude"] - 0.48) < 0.03,
+        "lateral": v2 is not None and abs(v2["index"] - 1.2) < 0.1 and v2["kind"] == "lateral" and v2["stick_slip"] < 0.1,
+        "paths": v1s["index"] == v1["index"] and abs(pooled["index"] - v1["index"]) < 0.08,
+        "nothing": none is None and short is None,
+        "twin": len(tr) > 1500 and corr > 0.95 and agree >= 0.95 and float(np_.median(np_.abs(tr_ - de_))) < 0.05,
+        "words": "stick-slip" in V.words(v1, 1.2) and "over the limit" in V.words(v1, 1.0) and "over the limit" not in V.words(v0, 1.2),
+    }
+    failed1 = [k for k, v in c1.items() if not v]
+    ok(not failed1,
+       f"DY1 the vibration index off the surface channels: a steady feed reads {v0['index'] if v0 else 'none'}, a torque swinging ±48% reads {v1['index'] if v1 else 'none'} as stick-slip, "
+       f"a weight swinging ±24% reads {v2['index'] if v2 else 'none'} as lateral, the statistics path equals the samples path and pooled windows agree, a window without torque "
+       f"or weight reads nothing; on twenty twin scenes the derived index tracks the twin's own (correlation {corr:.3f}, the limit's crossings agreeing {100 * agree:.0f}%, "
+       "SIMULATION - the twin's calibration, not a string's)" + (f" [failed: {', '.join(failed1)}]" if failed1 else ""))
+    # -- DY2 the rig side ---------------------------------------------------------------------------------------------------------
+    shipped = P.Policy.load(S.SHIPPED_POLICY)
+    cfg = json.loads(json.dumps(C.EXAMPLE)); cfg["output"]["dir"] = str(d / "rig"); cfg["status"]["port"] = 0; cfg["status"]["bind"] = "127.0.0.1"
+    cfg["rig"]["transport"] = "sim"; cfg["closed_loop"]["allowed"] = True; cfg["closed_loop"]["stale_s"] = 30
+    cfg = C.check(cfg)
+    try:
+        C.check(json.loads(json.dumps(cfg)) | {"rig": {**cfg["rig"], "vibration_window_s": 2}}); win_refused = False
+    except C.ConfigError:
+        win_refused = True
+    drl = S.Driller(cfg, policy=shipped, twin_seed=11, twin_pace_s=0.6)
+    drl.start()
+    try:
+        t_end = time.monotonic() + 25
+        while time.monotonic() < t_end and len(drl.advisor.history) < 3:
+            time.sleep(0.2)
+        snap = drl.feed.snapshot(); live = drl.live()
+        cur = dict(drl.advisor.history[-1]) if drl.advisor.history else None
+        md = snap["state"].get("hole_depth")
+        rq = urllib.request.Request(drl.url + "/api/arm", data=json.dumps({"by": "tester", "to_md": md + 400}).encode(), headers={"Content-Type": "application/json"}, method="POST")
+        with urllib.request.urlopen(rq, timeout=5) as r_:
+            armed = json.load(r_)
+        drl.cfg["limits"]["vibration_index"] = 0.01                      # the limit lowered under the loop: the derived index crosses it at the next look
+        t_end = time.monotonic() + 8
+        while time.monotonic() < t_end and drl.advisor.armed is not None:
+            time.sleep(0.2)
+        drl.cfg["limits"]["vibration_index"] = 1.2
+        last = drl.advisor.arm_log[-1]
+        with urllib.request.urlopen(drl.url + "/live", timeout=5) as r_:
+            screen = r_.read().decode("utf-8")
+    finally:
+        drl.stop()
+    # the downhole item wins; a feed with neither reads none
+    feed = R.Feed(cfg); feed.state.update({"hole_depth": 10500.0, "gamma": 60.0, "continuous_inc": 90.0, "vibration": 1.7}); feed.last_utc = time.time(); feed.connected = True
+    for k in range(30):
+        feed.window.append(float(k), torque=10 * (1 + 0.1 * _m.sin(k)), rpm=120.0, wob=25.0, hkld=175.0, spp=2800.0)
+    v_tool = A.Advisor.vibration_of(feed.snapshot())
+    feed.state["vibration"] = None
+    v_der = A.Advisor.vibration_of(feed.snapshot())
+    feed2 = R.Feed(cfg); feed2.state.update({"hole_depth": 10500.0, "gamma": 60.0}); feed2.last_utc = time.time(); feed2.connected = True
+    v_none = A.Advisor.vibration_of(feed2.snapshot())
+    adv2 = A.Advisor(cfg, shipped, feed2, A.Records(json.loads(json.dumps(cfg)) | {"output": {"dir": str(d / "rig2")}}))
+    rec2 = adv2.decide(feed2.snapshot())
+    decs = [json.loads(l) for l in open(d / "rig" / "decisions.jsonl", encoding="utf-8")]
+    c2 = {
+        "twin_rig": snap["state"].get("torque") is not None and snap["state"].get("hookload") is not None and snap["state"].get("vibration") is None and snap.get("vibration") is not None
+                    and snap["vibration"]["index"] > 0 and snap.get("window_n", 0) >= 10 and abs(snap["vibration"]["index"] - drl.feed.lat.vib) < 0.25,
+        "advisor": cur is not None and cur["context"]["vibration_source"] == V.SOURCE and cur["context"]["vibration"] > 0 and any("derived from the surface data" in r_ for r_ in cur["reasons"])
+                   and live["vibration"]["source"] == V.SOURCE and live["vibration"]["parts"]["kind"] in ("stick-slip", "lateral"),
+        "wins": v_tool[0] == 1.7 and v_tool[1] == "the downhole tool" and v_der[1] == V.SOURCE and 0 < v_der[0] < 1.0,
+        "none": v_none[0] == 0.0 and v_none[1].startswith("none") and rec2 is not None and any("vibration unread" in r_ for r_ in rec2["reasons"]),
+        "disarms": armed.get("ok") and last["event"] == "disarmed" and "vibration" in last["reason"] and "surface data" in last["reason"],
+        "records": any((x.get("context") or {}).get("vibration_source") == V.SOURCE for x in decs),
+        "screen": "from surface data" in screen and "downhole tool" in screen,
+        "refusal": win_refused,
+        "help": not H.check("driller") and "The vibration index from the feed" in (pkg / "help" / "driller.md").read_text(encoding="utf-8")
+                and "surface" in (pkg / "help" / "tutorial" / "29-driller-rig.md").read_text(encoding="utf-8"),
+    }
+    failed2 = [k for k, v in c2.items() if not v]
+    ok(not failed2,
+       "DY2 the twin as the rig publishes the surface torque, weight and hook load and no downhole index; the feed's window gives the derived index close to the "
+       "twin's own, the advisor reads it and says so in its reasons, the records and the screen; the downhole tool's item wins when it comes, a feed with neither "
+       "reads none and says so; the closed loop disarms on the derived index crossing the limit; a window too short is refused; the help and the tutorial say so"
+       + (f" [failed: {', '.join(failed2)}]" if failed2 else ""))
+    # -- DY3 GEA's side: the lateral file with the statistics, the replay over the limit, the card ---------------------------------------
+    ws = Workspace.create(str(d / "ws"), "Pad 3 vibration", actor="tester")
+    exp = E.selftest(str(d), 3000)
+    w = ws.add_well_file(exp["path"], display="Well EDR", actor="tester")
+    lat_csv = str(d / "lat.csv")
+    info = DL.lateral_from_edr(ws, w["id"], lat_csv)
+    head = Path(lat_csv).read_text(encoding="utf-8").splitlines()[0].split(",")
+    rec = DL.shadow(ws, w["id"], actor="tester")
+    sm = rec["summary"]
+    # the twin's lateral with and without the statistics
+    tw_csv = str(d / "tw.csv"); tw_no = str(d / "tw_no.csv")
+    tinfo = SH.twin_lateral(tw_csv, seed=5, act_fn=P.policy_act_fn(shipped)); SH.twin_lateral(tw_no, seed=5, act_fn=P.policy_act_fn(shipped), with_stats=False)
+    r_tw = SH.run(tw_csv, shipped, well="Twin 5"); r_no = SH.run(tw_no, shipped, well="Twin 5")
+    tv = dict(tinfo["true_vibration"]); mds = np_.array(sorted(tv))
+    tvv = np_.array([tv[m_] for m_ in mds])
+    def true_over(md_):                                           # the twin's own index averaged over the 30 ft the replay's window pooled
+        j0, j1 = int(np_.searchsorted(mds, md_ - 30.0)), int(np_.searchsorted(mds, md_, side="right"))
+        return float(tvv[j0:j1].mean()) if j1 > j0 else float("nan")
+    pairs = np_.array([(x["vibration"], true_over(x["md"])) for x in r_tw["decisions"] if x["vibration"] is not None])
+    pairs = pairs[np_.isfinite(pairs[:, 1])]
+    corr_tw = float(np_.corrcoef(pairs[:, 0], pairs[:, 1])[0, 1]) if len(pairs) > 10 else 0.0
+    md_text = Path(ws.reports_dir, rec["report"]["md"]).read_text(encoding="utf-8")
+    app_src = (pkg / "web" / "app.html").read_text(encoding="utf-8")
+    c3 = {
+        "lateral_file": all(c in head for c in DL.LATERAL_STATS) and info["vibration_rows"] >= 1000,
+        "over_limit": sm["vibration_in_record"] and sm["vibration_over_limit_pct"] is not None and 5.0 <= sm["vibration_over_limit_pct"] <= 40.0 and sm["vibration_mean"] > 0.3
+                      and sm["eased_when_over_pct"] is not None and sm["eased_when_over_pct"] >= 50.0,
+        "report": "stood over the limit" in md_text and "| Vib |" in md_text,
+        "twin_lateral": r_tw["summary"]["vibration_in_record"] and len(pairs) > 50 and corr_tw > 0.7 and float(np_.median(np_.abs(pairs[:, 0] - pairs[:, 1]))) < 0.12,
+        "without": not r_no["summary"]["vibration_in_record"] and r_no["summary"]["vibration_over_limit_pct"] is None and all(x["vibration"] is None for x in r_no["decisions"]),
+        "selftest_export": any(abs(float(r_.split(",")[12]) - 10.0) > 4.0 for r_ in Path(exp["path"]).read_text(encoding="utf-8").splitlines()[1:] if r_.split(",")[12] not in ("",)),
+        "card": "Vibration over limit" in app_src and "eased" in app_src,
+    }
+    failed3 = [k for k, v in c3.items() if not v]
+    ok(not failed3,
+       f"DY3 GEA's lateral file carries the surface channels' statistics per foot ({info['vibration_rows']} feet of them from the self-test export), the replay reads the "
+       f"stick-slip stretch over the limit at {sm['vibration_over_limit_pct'] or 0:.0f}% of the decisions and the advisor eases there {sm['eased_when_over_pct'] or 0:.0f}% of the "
+       f"time, the report says so; on the twin's lateral the replayed index tracks the twin's own (correlation {corr_tw:.2f}); a record without the statistics is unjudged; "
+       "the card carries the column" + (f" [failed: {', '.join(failed3)}]" if failed3 else ""))
+
+
 def main() -> int:
     print("GEA-Program - ACCEPTANCE SUITE (the product gate)")
     # a handle a job subprocess still holds at the end must not turn a finished gate into a traceback on Windows:
@@ -17142,6 +17316,7 @@ def main() -> int:
         section_dv_driller(tmp)
         section_dw_shadow(tmp)
         section_dx_third_dimension(tmp)
+        section_dy_vibration(tmp)
     if _FAILS:
         print(f"[ACCEPTANCE] {len(_FAILS)} FAILURES ({_PASS} passed):")
         for f in _FAILS:

{gea_program-0.80.0 → gea_program-0.81.0}/gea/driller_link.py

@@ -281,6 +281,11 @@ def wells_with_records(ws) -> List[dict]:
 # -- shadow mode: a drilled well of this workspace replayed through the advisor ---------------------------------------------
 
 LATERAL_COLUMNS = ('md_ft', 'tvd_ft', 'gamma_api', 'wob_klb', 'rpm', 'flow_gpm', 'rop_ft_hr', 'spp_psi', 'hours')
+# per foot, the surface channels' mean and RMS about it over the seconds since the foot before (since 0.81.0): what the
+# driller's vibration index is read off when the string had no downhole tool - the same names the driller's program reads
+LATERAL_STATS = ('torque_mean', 'torque_rms', 'rpm_mean', 'rpm_rms', 'wob_mean', 'wob_rms', 'hkld_mean', 'hkld_rms', 'spp_mean', 'spp_rms')
+_STAT_CH = {'torque': 'torque', 'rpm': 'rpm', 'wob': 'wob', 'hkld': 'hkld', 'spp': 'spp'}
+_STAT_MIN = 5                     # seconds of a foot at least; the index pools the feet of a decision
 
 
 def lateral_from_edr(ws, well_id: str, out_csv: str) -> dict:
@@ -296,7 +301,7 @@ def lateral_from_edr(ws, well_id: str, out_csv: str) -> dict:
     if not src or not E.is_edr(src):
         raise ValueError(f"{well_id} has no drilling-recorder export (an EDR CSV) under its sources")
     st = E.read(src)
-    ch = {k: E._ch(st, k) for k in ('hole', 'tvd', 'gamma', 'wob', 'rpm', 'flow', 'rop', 'spp', 'onb')}
+    ch = {k: E._ch(st, k) for k in ('hole', 'tvd', 'gamma', 'wob', 'rpm', 'flow', 'rop', 'spp', 'onb', 'torque', 'hkld')}
     hole = ch['hole']
     if hole is None or ch['tvd'] is None:
         raise ValueError('the export carries no hole depth or no interpolated TVD; the lateral cannot be placed')
@@ -308,32 +313,47 @@ def lateral_from_edr(ws, well_id: str, out_csv: str) -> dict:
     n = len(hole)
     rows = []
     seen = set(); g_acc = []
+    s_acc = {k: [] for k in _STAT_CH}
     for i in range(n):
         h = hole[i]
         if h is None or (isinstance(h, float) and (h != h)) or not keep_h[i]:
             continue
         if ch['gamma'] is not None and not (ch['gamma'][i] != ch['gamma'][i]):
             g_acc.append(float(ch['gamma'][i]))
+        for k, c in _STAT_CH.items():
+            v = _v(ch[c], i)
+            if v == v:                                               # not NaN
+                s_acc[k].append(v)
         foot = int(h)
         if foot in seen:
             continue
         seen.add(foot)
         tvd = ch['tvd'][i]
-        rows.append({'md_ft': float(h), 'tvd_ft': float(tvd) if not (tvd != tvd) else float('nan'),
-                     'gamma_api': float(sorted(g_acc)[len(g_acc) // 2]) if g_acc else float('nan'),
-                     'wob_klb': _v(ch['wob'], i), 'rpm': _v(ch['rpm'], i), 'flow_gpm': _v(ch['flow'], i), 'rop_ft_hr': _v(ch['rop'], i), 'spp_psi': _v(ch['spp'], i),
-                     'hours': float(secs[i]) / 3600.0})
-        g_acc = []
+        row = {'md_ft': float(h), 'tvd_ft': float(tvd) if not (tvd != tvd) else float('nan'),
+               'gamma_api': float(sorted(g_acc)[len(g_acc) // 2]) if g_acc else float('nan'),
+               'wob_klb': _v(ch['wob'], i), 'rpm': _v(ch['rpm'], i), 'flow_gpm': _v(ch['flow'], i), 'rop_ft_hr': _v(ch['rop'], i), 'spp_psi': _v(ch['spp'], i),
+               'hours': float(secs[i]) / 3600.0}
+        for k in _STAT_CH:
+            a = s_acc[k]
+            if len(a) >= _STAT_MIN:
+                m = sum(a) / len(a)
+                row[f'{k}_mean'] = m; row[f'{k}_rms'] = (sum((x - m) ** 2 for x in a) / len(a)) ** 0.5
+            else:
+                row[f'{k}_mean'] = float('nan'); row[f'{k}_rms'] = float('nan')
+        rows.append(row)
+        g_acc = []; s_acc = {k: [] for k in _STAT_CH}
     if len(rows) < 100:
         raise ValueError(f'the export yields only {len(rows)} feet of new hole; a lateral is thousands')
     rows.sort(key=lambda r: r['md_ft'])
     os.makedirs(os.path.dirname(out_csv), exist_ok=True)
+    cols = list(LATERAL_COLUMNS) + list(LATERAL_STATS)
     with open(out_csv, 'w', encoding='utf-8', newline='') as f:
-        w = _csv.DictWriter(f, fieldnames=list(LATERAL_COLUMNS)); w.writeheader()
+        w = _csv.DictWriter(f, fieldnames=cols); w.writeheader()
         for r in rows:
-            w.writerow({c: ('' if (isinstance(r[c], float) and r[c] != r[c]) or r[c] is None else f'{r[c]:.3f}') for c in LATERAL_COLUMNS})
+            w.writerow({c: ('' if (isinstance(r[c], float) and r[c] != r[c]) or r[c] is None else f'{r[c]:.3f}') for c in cols})
     rows.sort(key=lambda r: r['md_ft'])
     return {'rows': len(rows), 'source': src, 'md_from': rows[0]['md_ft'], 'md_to': rows[-1]['md_ft'], 'gamma_rows': sum(1 for r in rows if r['gamma_api'] == r['gamma_api']),
+            'vibration_rows': sum(1 for r in rows if r['torque_mean'] == r['torque_mean'] or r['wob_mean'] == r['wob_mean']),
             'seconds': int(n), 'excluded_rows': int((~keep_h).sum()), 'depth_events': {k: len(v) for k, v in de.items() if isinstance(v, list)}}
 
 

{gea_program-0.80.0 → gea_program-0.81.0}/gea/edr.py

@@ -748,8 +748,10 @@ def selftest(tmp: str, rows_per_section: int = 3000) -> dict:
                 if on:
                     depth += 600.0 / 3600.0                     # 600 ft/h while on bottom (a self-test cadence, not a rig's)
                 tvd = depth if depth < 2000.0 else 2000.0 + (depth - 2000.0) * 0.02   # a lateral past 2,000 ft
+                # a stretch of stick-slip in the lateral: the surface torque swinging ±60% with an eight-second period (since 0.81.0)
+                tq = 10.0 * (1.0 + 0.6 * math.sin(2 * math.pi * i / 8.0)) if (s == 2 and 1000 <= i < 2000 and on) else 10.0
                 row = [t.strftime('%Y/%m/%d'), t.strftime('%H:%M:%S'), f'{depth:.1f}', f'{depth - (0 if on else 30):.1f}', '600.00' if on else '0.00',
-                       '20.0' if on else '0.0', '60.00' if on else '0.00', '2500.00', '150.0', '400.00', '500.00', '50.00', '10.000', str(on),
+                       '20.0' if on else '0.0', '60.00' if on else '0.00', '2500.00', '150.0', '400.00', '500.00', '50.00', f'{tq:.3f}', str(on),
                        '-999.25' if s == 0 else f'{(45.0 if depth < 2300.0 else 115.0) + (i % 7):.2f}', '100', '0.00' if i % 500 == 0 else '45.00', '' if (i % 10 == 0) else f'{tvd:.2f}']
                 w.writerow(row); t += timedelta(seconds=1)
     st = read(p)

{gea_program-0.80.0 → gea_program-0.81.0}/gea/help/driller.md

@@ -2,12 +2,12 @@
 
 > A program on the rig PC that reads the rig's own feed and the pre-drill model, places the bit in the layer with a position filter, and, every 30 ft, recommends in the driller's units what to do next - a policy trained by reinforcement learning in a physics twin of the lateral - with the driller's answer, every command, and the records pulled into GEA.
 
-**The command**: on the rig PC, `GEA-Driller-0.80.0.tar.gz` from the release (or the kit's `installers` folder, fetched on the Audit / Update tab): unpack it and run `sudo sh install.sh` on Linux or `install.cmd` on Windows, once; edit its config - the EDR's WITS0 feed (`tcp`, the host and port; `serial`, the COM port), the pre-drill model (the target layer's top TVD at the heel, its thickness and dip, the gamma in, above and below, the deep-resistivity tool, the heel's MD and TVD), the tool's cap, the limits - and restart it. The driller's screen is at port 8790 of the rig PC: `http://192.168.1.60:8790/live`. It shows the section with the model's layer window, the hole drilled through it and - since 0.78.0 - the **position filter**'s band: where the layer is from the readings, as a geosteerer places it (a particle filter over the layer's offset from the model, its dip error and its thickness, moved every decision and kept to the guesses that explain the gamma and the deep-resistivity distance), with the probability the bit is in the layer, above or below it and the distance to the top and the base with its spread, sixty feet ahead; the agent reads the same estimate, and so does the textbook driller it is judged against. Then the recommendation in words - *Build +1.5°/100 ft (toolface up, 25% steering); 25 klb WOB, 120 rpm, 500 gpm* - with its reasons (what the deep-resistivity tool says, the gamma against the model's values, the model's bracket, the limits) and the confidence of each choice, the rig's numbers against the limits, and **Accept**, **Reject** or **Did something else…** with the operator's name. In GEA: the **Drill string** tab's card **GEA Driller** - the rig PC's address and the well, **Pull**: the records come in checked against their hashes, and the table says how many decisions, accepted, rejected, done otherwise, the hole under advice, the armed sections and the commands. **Open the driller's screen** opens the rig PC's screen from its address. Before there is a rig PC: **Start the twin as the rig** runs the driller's program on this computer with a scene drilling itself under the agent - **Open its screen** is the driller's screen with the twin behind it, labelled SIMULATION - and **Pull from it** brings its records in; **Stop it** closes them. **Shadow a drilled well** (since 0.79.0): a well of this workspace with a drilling-recorder export is replayed through the advisor - every 30 ft the agent sees what the rig had shown to that point and nothing past it, and its recommendation is set beside what the record did next: the build actually made over the following 90 ft, the weight, speed and flow used, and at each stretch the gamma marks as out of the layer, whether the advisor called the way back at the first reading. The report, **SHADOW MODE**, is under the well's reports with a drawing of the lateral against the layer; the layer model is read off the well's own gamma in hindsight and says so - and grades how well it fits the well (good, fair, poor: a well steered to a rock that is not the low gamma reads poor, and the agent's calls against a poor model mean little) - unless the site's pre-drill model is given: a file `wells\Well-30636033\driller\model.json` with the config's `model` block (the target layer's top TVD at the heel, its thickness and dip, the gamma in, above and below, the heel's MD and TVD) is used whenever it is there (`gea workspace --path C:\site --action driller-shadow --well Well-30636033`). The export is read on this computer and nothing of it leaves it. Agreement with the driller says the two would have done alike, not that either was right. **The third dimension** (since 0.80.0): the lateral has an azimuth. The config's model carries the plan's azimuth (`plan_azimuth_deg`; empty, the first survey's at the heel is taken), the layer's dip across the plan line (`cross_dip_deg`, positive deepening to the right), the corridor the hole may run in to the right and left of the plan line (`corridor_ft`, the lease line and the offset wells) and where the heel sits across it (`heel_offset_ft`); the feed's surveys and the continuous azimuth (WITS item 0832, or the config's mapping) place the bit by minimum curvature along the plan, right of its line and in depth, and the screen draws the plan view - the corridor as a band, the hole against the plan line - under the section. The recommendation gains the aim - where to point the azimuth, along the plan or 4° left or right of it, and the turn that asks from where the hole points: *Build +1.5°/100 ft and aim 4° right of the plan (azimuth 44.0°), turning right 2.0°/100 ft (toolface 53°, 42% steering)* - with the build and the turn held together inside the DLS limit, and **Did something else…** takes the aim, or the turn made instead; the position filter carries the cross dip and reads it only when the hole moves across the plan line, leaving the model's value standing until then. In the twin the layer is a surface, the faults have a strike, the tool walks, and a hole that leaves the corridor by 150 ft is lost; the agent is judged on the hole in the corridor as well as in the layer (`gea-driller evaluate` prints both). Shadow mode reads the record's `azimuth_deg` column when it has one and sets the turn the advisor would have asked beside the turn the record made; without it the record's turns are not judged, and the report says so. Over a cellular modem the rig PC joins GEA-VPN as a member of kind `driller` and GEA pulls from `http://10.77.0.4:8790`. The closed loop: `closed_loop.allowed` in the rig PC's config puts the switch on its screen; an operator arms it by name for one section of at most 500 ft (**Arm for this section**), every decision then goes to the downlink as a command, and the loop disarms itself on a stale feed, a crossed limit, the section's end or **Disarm now** - and this version's only downlink is the null one, which keeps every command on record and sends none, because no vendor's downlink protocol ships with it. From a terminal: `gea workspace --path C:\site --action driller-pull --box http://192.168.1.60:8790 --well SWD-1`; on the rig PC `gea-driller sim --seed 7 --pace 3 --port 8790`, `gea-driller evaluate --scenes 20`, `gea-driller train --seconds 600 --out policy.json`, `gea-driller selftest`.
+**The command**: on the rig PC, `GEA-Driller-0.81.0.tar.gz` from the release (or the kit's `installers` folder, fetched on the Audit / Update tab): unpack it and run `sudo sh install.sh` on Linux or `install.cmd` on Windows, once; edit its config - the EDR's WITS0 feed (`tcp`, the host and port; `serial`, the COM port), the pre-drill model (the target layer's top TVD at the heel, its thickness and dip, the gamma in, above and below, the deep-resistivity tool, the heel's MD and TVD), the tool's cap, the limits - and restart it. The driller's screen is at port 8790 of the rig PC: `http://192.168.1.60:8790/live`. It shows the section with the model's layer window, the hole drilled through it and - since 0.78.0 - the **position filter**'s band: where the layer is from the readings, as a geosteerer places it (a particle filter over the layer's offset from the model, its dip error and its thickness, moved every decision and kept to the guesses that explain the gamma and the deep-resistivity distance), with the probability the bit is in the layer, above or below it and the distance to the top and the base with its spread, sixty feet ahead; the agent reads the same estimate, and so does the textbook driller it is judged against. Then the recommendation in words - *Build +1.5°/100 ft (toolface up, 25% steering); 25 klb WOB, 120 rpm, 500 gpm* - with its reasons (what the deep-resistivity tool says, the gamma against the model's values, the model's bracket, the limits) and the confidence of each choice, the rig's numbers against the limits, and **Accept**, **Reject** or **Did something else…** with the operator's name. In GEA: the **Drill string** tab's card **GEA Driller** - the rig PC's address and the well, **Pull**: the records come in checked against their hashes, and the table says how many decisions, accepted, rejected, done otherwise, the hole under advice, the armed sections and the commands. **Open the driller's screen** opens the rig PC's screen from its address. Before there is a rig PC: **Start the twin as the rig** runs the driller's program on this computer with a scene drilling itself under the agent - **Open its screen** is the driller's screen with the twin behind it, labelled SIMULATION - and **Pull from it** brings its records in; **Stop it** closes them. **Shadow a drilled well** (since 0.79.0): a well of this workspace with a drilling-recorder export is replayed through the advisor - every 30 ft the agent sees what the rig had shown to that point and nothing past it, and its recommendation is set beside what the record did next: the build actually made over the following 90 ft, the weight, speed and flow used, and at each stretch the gamma marks as out of the layer, whether the advisor called the way back at the first reading. The report, **SHADOW MODE**, is under the well's reports with a drawing of the lateral against the layer; the layer model is read off the well's own gamma in hindsight and says so - and grades how well it fits the well (good, fair, poor: a well steered to a rock that is not the low gamma reads poor, and the agent's calls against a poor model mean little) - unless the site's pre-drill model is given: a file `wells\Well-30636033\driller\model.json` with the config's `model` block (the target layer's top TVD at the heel, its thickness and dip, the gamma in, above and below, the heel's MD and TVD) is used whenever it is there (`gea workspace --path C:\site --action driller-shadow --well Well-30636033`). The export is read on this computer and nothing of it leaves it. Agreement with the driller says the two would have done alike, not that either was right. **The third dimension** (since 0.80.0): the lateral has an azimuth. The config's model carries the plan's azimuth (`plan_azimuth_deg`; empty, the first survey's at the heel is taken), the layer's dip across the plan line (`cross_dip_deg`, positive deepening to the right), the corridor the hole may run in to the right and left of the plan line (`corridor_ft`, the lease line and the offset wells) and where the heel sits across it (`heel_offset_ft`); the feed's surveys and the continuous azimuth (WITS item 0832, or the config's mapping) place the bit by minimum curvature along the plan, right of its line and in depth, and the screen draws the plan view - the corridor as a band, the hole against the plan line - under the section. The recommendation gains the aim - where to point the azimuth, along the plan or 4° left or right of it, and the turn that asks from where the hole points: *Build +1.5°/100 ft and aim 4° right of the plan (azimuth 44.0°), turning right 2.0°/100 ft (toolface 53°, 42% steering)* - with the build and the turn held together inside the DLS limit, and **Did something else…** takes the aim, or the turn made instead; the position filter carries the cross dip and reads it only when the hole moves across the plan line, leaving the model's value standing until then. In the twin the layer is a surface, the faults have a strike, the tool walks, and a hole that leaves the corridor by 150 ft is lost; the agent is judged on the hole in the corridor as well as in the layer (`gea-driller evaluate` prints both). Shadow mode reads the record's `azimuth_deg` column when it has one and sets the turn the advisor would have asked beside the turn the record made; without it the record's turns are not judged, and the report says so. **The vibration index from the feed** (since 0.81.0): a rig without a downhole vibration tool left the agent blind to the stick-slip and the whirl it was trained to ease, and the closed loop's vibration limit could never trip. Now the rig PC reads an index off the surface channels every EDR sends: over the last minute (`rig.vibration_window_s`), the surface torque's RMS about its mean as a fraction of the mean - the measure the Drill string page calls the oscillation index - times root two for the amplitude, and the same of the weight on bit and the hook load; stick-slip is the torque amplitude over 0.4, lateral vibration the weight amplitude over 0.2 (the twin's scale, where 1.2 is the limit), and the index is the larger. The downhole tool's item (WITS 0830) is taken instead whenever it comes, and every decision records which it read: the tile on the screen says *downhole tool* or *from surface data, stick-slip*, the reasons say *vibration 1.35 derived from the surface data (stick-slip, the surface torque swinging ±54%) over the limit 1.2*, and the limit disarms the loop on either. A surface proxy, labelled; on the twin as the rig it tracks the twin's own index within a few hundredths. The lateral file GEA writes for shadow mode carries, per foot, the surface channels' mean and RMS over the seconds of that foot (`torque_mean`, `torque_rms`, `wob_mean`, `wob_rms`, `hkld_mean`, `hkld_rms`, `rpm_mean`, `rpm_rms`, `spp_mean`, `spp_rms`), the replay reads the index off them for every decision, and the report says how often it stood over the limit and how often the advisor asked for less weight or more speed there than the record used; a record without torque or weight statistics says so and the advisor sees none. Over a cellular modem the rig PC joins GEA-VPN as a member of kind `driller` and GEA pulls from `http://10.77.0.4:8790`. The closed loop: `closed_loop.allowed` in the rig PC's config puts the switch on its screen; an operator arms it by name for one section of at most 500 ft (**Arm for this section**), every decision then goes to the downlink as a command, and the loop disarms itself on a stale feed, a crossed limit, the section's end or **Disarm now** - and this version's only downlink is the null one, which keeps every command on record and sends none, because no vendor's downlink protocol ships with it. From a terminal: `gea workspace --path C:\site --action driller-pull --box http://192.168.1.60:8790 --well SWD-1`; on the rig PC `gea-driller sim --seed 7 --pace 3 --port 8790`, `gea-driller evaluate --scenes 20`, `gea-driller train --seconds 600 --out policy.json`, `gea-driller selftest`.
 
 **What it writes**: on the rig PC, `decisions.jsonl` (every observation, recommendation, confidence, reasons and answer), `commands.jsonl` (every arming, command and disarming with its reason) and `surveys.csv`, each with a `.sha256` beside it, and `manifest.json`. In GEA, `wells\SWD-1\driller\` holds the same files as pulled, `manifest.json` and `last_pull.json` with the summary; the audit lines `driller.pull`, `driller.sim_start`, `driller.sim_stop`. The twin as the rig writes under `field\sim-driller\data`.
 
 **The number to check**: on the rig PC's screen, the feed's age (a decision is made only on a live feed) and, in GEA's table, accepted against rejected and done otherwise - an agent whose advice is rejected more than taken is not helping, and the records say so. For the agent itself, `gea-driller evaluate` prints the policy against a textbook driller on twenty held-out twin scenes - the hole in the layer, the sweet spot, feet a day, dogleg, stuck pipe, losses - labelled SIMULATION; the self-test refuses a policy that does not beat the textbook.
 
-**What this page will not call a measurement**: the twin's figures are a simulation's, however many scenes, and say nothing of a real formation; a recommendation is the agent's reading of the feed, the model and the filter's estimate, not a survey; the filter's band is a probability, not a log, and the hole's position on its screen is projected from the surveys and the continuous inclination and azimuth, not measured at the bit, and its offset from the plan line inherits every survey's azimuth error; the hole-cleaning and balling the agent reasons from are the model's estimates; and "commands sent" is zero in this version by construction.
+**What this page will not call a measurement**: the twin's figures are a simulation's, however many scenes, and say nothing of a real formation; a recommendation is the agent's reading of the feed, the model and the filter's estimate, not a survey; the filter's band is a probability, not a log, and the hole's position on its screen is projected from the surveys and the continuous inclination and azimuth, not measured at the bit, and its offset from the plan line inherits every survey's azimuth error; the hole-cleaning and balling the agent reasons from are the model's estimates; the vibration index read off the surface data is a proxy for what a downhole tool would measure, calibrated on the twin, not on a string; and "commands sent" is zero in this version by construction.
 
 Related: `gea help drillstring`, `gea help recorder`, `gea help vpn`.

{gea_program-0.80.0 → gea_program-0.81.0}/gea/help/install.md

@@ -2,7 +2,7 @@
 
 > GEA-Program-Setup: the program installed for you like any Windows program - a window of its own, an icon in the notification area, Start-menu and desktop shortcuts, an Add/Remove Programs entry, upgrades in place - with no administrator rights and the site's data left where it is.
 
-**The command**: download the setup from the release on GitHub (`GEA-Program-Setup-0.80.0.exe` for this version) and run it. It installs for you alone, under `%LOCALAPPDATA%\Programs\GEA-Program`, and asks for the site workspace - the folder that holds the wells, reports, records, accounts and keys. An existing one such as `C:\site` is used exactly as it is, its name included; for a new one (by default `%LOCALAPPDATA%\GEA-Program\site`) it also asks the site's name, which heads every report, and makes the workspace with it (left empty, the workspace is named after its folder; an administrator renames the site in Administration's site settings). Then the Start menu's **GEA-Program** (and the desktop shortcut) starts the control panel when it is not running and opens it in a window of its own. A newer setup installs over the older one: it stops the control panel, replaces the program, keeps the workspace and the choices made before. For a site's software deployment: `GEA-Program-Setup-0.80.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"` (`/SITENAME` names a workspace the setup makes; one that exists keeps its own name). From a terminal: `gea launch` does what the shortcut does, `gea launch --selftest` says what it would do, `gea tray --selftest` checks the icon.
+**The command**: download the setup from the release on GitHub (`GEA-Program-Setup-0.81.0.exe` for this version) and run it. It installs for you alone, under `%LOCALAPPDATA%\Programs\GEA-Program`, and asks for the site workspace - the folder that holds the wells, reports, records, accounts and keys. An existing one such as `C:\site` is used exactly as it is, its name included; for a new one (by default `%LOCALAPPDATA%\GEA-Program\site`) it also asks the site's name, which heads every report, and makes the workspace with it (left empty, the workspace is named after its folder; an administrator renames the site in Administration's site settings). Then the Start menu's **GEA-Program** (and the desktop shortcut) starts the control panel when it is not running and opens it in a window of its own. A newer setup installs over the older one: it stops the control panel, replaces the program, keeps the workspace and the choices made before. For a site's software deployment: `GEA-Program-Setup-0.81.0.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /WORKSPACE="C:\site" /SITENAME="Pad 3" /TASKS="desktopicon"` (`/SITENAME` names a workspace the setup makes; one that exists keeps its own name). From a terminal: `gea launch` does what the shortcut does, `gea launch --selftest` says what it would do, `gea tray --selftest` checks the icon.
 
 **The window**: Microsoft Edge's app window (`msedge --app=`: the control panel with no tabs and no address bar, its own button on the taskbar, which shows the program's derrick and pins as GEA-Program, not as Edge), with a browser profile of its own (`%LOCALAPPDATA%\GEA-Program\window`, no extensions; the first time, Edge may say it signed that profile in to your Microsoft account - Got it), else Google Chrome's, else a tab in the default browser. Where the browser keeps no cookies (its settings or a policy block them), the sign-in page says so and the control panel holds the sign-in itself, in the window's address, until the window is closed. The control panel itself runs with no window of its own: `gea supervise` keeps it running in the background, starts it again when it asks for a restart, and writes everything it would have shown in a console - the start, the sign-ins, the jobs, a stop and why - to `records\console.log` in the workspace. No PowerShell or console window opens. The kit's `start-dashboard.cmd` still runs it in a console window, for a site that wants to watch it there.
 
@@ -18,7 +18,7 @@
 
 **The number to check**: Add/Remove Programs lists GEA-Program with the version you installed; `gea doctor --workspace C:\site` ends with `nothing blocks serving`; the Start menu's **Verify GEA-Program** runs the acceptance gate from the installation and ends with `[ACCEPTANCE] OK - N checks passed`. The release's build installs, upgrades and uninstalls the setup silently before it is published, with the control panel running, and checks the workspace untouched afterwards.
 
-**Signed**: when the publisher's code-signing certificate is configured for the build, the setup is signed with it (Authenticode, timestamped) and Windows names the publisher; until then it ships unsigned and Windows SmartScreen says "unknown publisher" (More info, then Run anyway). The build's provenance holds either way: `gh attestation verify GEA-Program-Setup-0.80.0.exe -R Daniel8Murphy0007/GEA-Program`. The uninstaller the setup leaves behind is Inno Setup's own and is not signed separately.
+**Signed**: when the publisher's code-signing certificate is configured for the build, the setup is signed with it (Authenticode, timestamped) and Windows names the publisher; until then it ships unsigned and Windows SmartScreen says "unknown publisher" (More info, then Run anyway). The build's provenance holds either way: `gh attestation verify GEA-Program-Setup-0.81.0.exe -R Daniel8Murphy0007/GEA-Program`. The uninstaller the setup leaves behind is Inno Setup's own and is not signed separately.
 
 **What this page will not call a measurement**: the icon's running or stopped is whether the control panel's port answers on this computer, read every three seconds - not whether every patch, job or report behind it is healthy (Home and the Verification page say that).
 

{gea_program-0.80.0 → gea_program-0.81.0}/gea/help/reader.md

@@ -4,7 +4,7 @@
 
 **The command**: Reports tab -> Signed dossiers -> **Download GEA Reader for your clients**, or `gea reader --workspace C:\site --out C:\site\GEA-Reader.html`. Send the file once, by any channel (email, a USB stick, the client's portal); send the site's key fingerprint separately - by phone, email or in the contract - as for any dossier. The client opens GEA-Reader.html, drops a dossier on it (or chooses it), and reads the verdict: **Valid** (signed with the site's key, or with a newer key the site's key handed over to), **Valid, but signed by a key you were not given**, or **Not valid** with the reason. Below the verdict: each check, the signer's fingerprint, the key hand-overs, and every file the dossier holds - a report opens in the page as it was signed, a PDF in the browser's own viewer, a table or a log as text, and any file can be saved. A dossier that lists source records by hash without carrying them lets the client choose their copies and checks each against its hash.
 
-**The program**: for a client who wants it installed, **GEA-Reader-Setup-0.80.0.exe** on the release page installs GEA Reader as a Windows program of its own, for the signed-in user, with no administrator rights and nothing of GEA-Program: GEA Reader in the Start menu and on the desktop with its own icon (a white page with a green seal, on blue) and its own taskbar button, and **Check with GEA Reader** on the right-click menu of .zip files (on Windows 11, under Show more options), which opens the dossier at once. It opens the same page in Microsoft Edge's app window with a browser profile of its own (`%LOCALAPPDATA%\GEA-Reader\window`), so a fingerprint the client saves - **Remember this fingerprint**, with whose it is - stays on that computer, and every later dossier signed with that key reads **Valid** with the name the client gave it. `GEA-Reader-portable-0.80.0.zip` is the same program to unzip and run (`GEA-Reader.cmd`). `python\python.exe -m gea_reader --selftest`, in the installed folder, checks the page, the icon, the taskbar identity and the hand-over of a dossier without opening a window.
+**The program**: for a client who wants it installed, **GEA-Reader-Setup-0.81.0.exe** on the release page installs GEA Reader as a Windows program of its own, for the signed-in user, with no administrator rights and nothing of GEA-Program: GEA Reader in the Start menu and on the desktop with its own icon (a white page with a green seal, on blue) and its own taskbar button, and **Check with GEA Reader** on the right-click menu of .zip files (on Windows 11, under Show more options), which opens the dossier at once. It opens the same page in Microsoft Edge's app window with a browser profile of its own (`%LOCALAPPDATA%\GEA-Reader\window`), so a fingerprint the client saves - **Remember this fingerprint**, with whose it is - stays on that computer, and every later dossier signed with that key reads **Valid** with the name the client gave it. `GEA-Reader-portable-0.81.0.zip` is the same program to unzip and run (`GEA-Reader.cmd`). `python\python.exe -m gea_reader --selftest`, in the installed folder, checks the page, the icon, the taskbar identity and the hand-over of a dossier without opening a window.
 
 **What it writes**: the one file, GEA-Reader.html (about 40 KB): the checks, written in the page's own script - Ed25519 (RFC 8032) in its own arithmetic, SHA-256 from the browser - and, when made from a workspace, the site's name and the fingerprints of every key it has signed with (the current one and each retired one from the key history: public halves only; the signing key never leaves `keys\`). The audit log records each download (`reader.download`) and each `gea reader` (`reader.write`) with the fingerprints the reader carried. The reader page writes nothing on the client's computer but the fingerprints a client saves (in the browser's storage for the page): it reads the zip it is given, in memory, and a saved copy goes where the client's browser saves downloads. The installed program also writes the page it opens to `%LOCALAPPDATA%\GEA-Reader\page` (with the dossier inside it when one was right-clicked; removed ten minutes later) and its right-click entry under the user's own registry keys, removed with the program.
 

{gea_program-0.80.0 → gea_program-0.81.0}/gea/help/recorder.md

@@ -2,7 +2,7 @@
 
 > GEA Recorder is the program on the pad: a Raspberry Pi in a sealed box that records the ground channels (geophones, accelerometers, electrode dipoles) through a 24-bit ADC and the rig's WITS0 feed, every sample on one GPS-disciplined clock, into hourly miniSEED files with a SHA-256 beside each and a manifest, and serves one status page on the pad network. Nothing to type: power it and it records. GEA pulls its files in and makes stations of them.
 
-**The command**: the **Seismic** tab, the card **Field recorder**: the box's address on the pad network (`http://192.168.1.50:8780` - the status page shows the address) or the folder of the USB mirror carried to the office, a station name if the site's is not wanted, then **Pull** (a job). GEA fetches the manifest, downloads every file it does not have, checks each against its SHA-256, and makes or updates two stations: the array of the ground-motion sensors (band 8-80 Hz, the sensors' positions from the box's config) and the electrode station (0.01-5 Hz); each sensor's hours are joined in order into one record, nothing re-sampled or filtered. Pull again later: only the new hours come across, and the stations are updated in place. From a terminal: `gea workspace --path C:\site --action field-pull --box http://192.168.1.50:8780`. On the box: `gea-recorder status`, `gea-recorder selftest`; `sudo sh kiosk.sh` once puts the live view full-screen on a monitor on the box's HDMI port from boot - RECORDING in green or what is wrong in red, the clock, the rig's depth, every channel's last minute and the ground sensors' spectrogram, nothing to press - and the same view is at `/live` on the box's page from any browser on the pad network; `sudo sh install.sh` once, from the release's `GEA-Recorder-0.80.0.tar.gz`; the box's README has the parts list, the wiring and the three chrony lines for the GPS clock.
+**The command**: the **Seismic** tab, the card **Field recorder**: the box's address on the pad network (`http://192.168.1.50:8780` - the status page shows the address) or the folder of the USB mirror carried to the office, a station name if the site's is not wanted, then **Pull** (a job). GEA fetches the manifest, downloads every file it does not have, checks each against its SHA-256, and makes or updates two stations: the array of the ground-motion sensors (band 8-80 Hz, the sensors' positions from the box's config) and the electrode station (0.01-5 Hz); each sensor's hours are joined in order into one record, nothing re-sampled or filtered. Pull again later: only the new hours come across, and the stations are updated in place. From a terminal: `gea workspace --path C:\site --action field-pull --box http://192.168.1.50:8780`. On the box: `gea-recorder status`, `gea-recorder selftest`; `sudo sh kiosk.sh` once puts the live view full-screen on a monitor on the box's HDMI port from boot - RECORDING in green or what is wrong in red, the clock, the rig's depth, every channel's last minute and the ground sensors' spectrogram, nothing to press - and the same view is at `/live` on the box's page from any browser on the pad network; `sudo sh install.sh` once, from the release's `GEA-Recorder-0.81.0.tar.gz`; the box's README has the parts list, the wiring and the three chrony lines for the GPS clock.
 
 **Before there is a Pi**: on the same card, **Start the simulated box**: the recorder's own program runs on this computer with its test signal in place of the ADC (a process of its own, its files under `field\sim-box\` in the workspace, its page on port 8781), **Open its monitor** shows the live screen the attendant will see, **Pull from it** brings its files in as stations, **Stop it** closes every file and lists them. **Open the box's monitor** opens any real box's live screen from its address. The kit and the setup install the recorder's program beside GEA for this; a pip install adds it with `pip install gea-recorder`. **From the office, over the internet**: GEA-VPN (`gea help vpn`, Administration) gives every box a private address the office pulls from (`http://10.77.0.3:8780`) through a tunnel from the pad's cellular modem; the box's zip from that card holds `vpn.sh`, run once on the Pi.
 

{gea_program-0.80.0 → gea_program-0.81.0}/gea/help/tutorial/01-install.md

@@ -5,10 +5,10 @@ Takes: 15 minutes
 > The program installed like any Windows program, with the site's folder chosen once.
 
 ## Before you start
-You need a Windows PC that will stay on while the site is watched (the office machine, or the doghouse PC), and the setup file for this version, `GEA-Program-Setup-0.80.0.exe`, from the release page on GitHub. No administrator rights are needed: the program installs for you alone.
+You need a Windows PC that will stay on while the site is watched (the office machine, or the doghouse PC), and the setup file for this version, `GEA-Program-Setup-0.81.0.exe`, from the release page on GitHub. No administrator rights are needed: the program installs for you alone.
 
 ## Steps
-1. Double-click `GEA-Program-Setup-0.80.0.exe`. If Windows asks whether to run it, choose **Run** - the setup is published by the site, not by a store.
+1. Double-click `GEA-Program-Setup-0.81.0.exe`. If Windows asks whether to run it, choose **Run** - the setup is published by the site, not by a store.
 2. The setup asks for the **site workspace**: the one folder that will hold the wells, the reports, the records, the accounts and the keys. For a new site keep the default or type `C:\site`. For a workspace that already exists, point at it - it is used exactly as it is, its name included.
 3. For a new workspace it asks the **site's name** (`Pad 3`). This name heads every report the program writes; an administrator can change it later in Administration, site settings.
 4. Tick the desktop shortcut and finish. The setup puts **GEA-Program** in the Start menu and an icon in the notification area by the clock.

{gea_program-0.80.0 → gea_program-0.81.0}/gea/help/tutorial/19-dossier-reader.md

@@ -8,7 +8,7 @@ Takes: 20 minutes
 1. On **Reports**, **Signed dossiers**: **Sign a dossier for the pad**, or one of the wells (the operator role). Tick *embed the source records* to carry the drilling records themselves rather than their hashes. The dossier is a zip: the reports as they stand, the declarations behind them, the audit log, the source records' hashes, the site's Ed25519 signature, and a checker inside (`verify_dossier.py`, plain Python).
 2. **Check** re-checks a dossier this site signed against the workspace as it now stands; a workspace that no longer matches a signed dossier raises an alert. *Check a dossier someone sent you* checks an uploaded one.
 3. **Download GEA Reader for your clients**: one HTML file. Send it to the client once by any channel - email, a USB stick, their portal. Send the site's **key fingerprint** separately - by phone, or in the contract - as for any dossier; the card shows it.
-4. The client opens `GEA-Reader.html` in any current browser, offline, and drops a dossier on it. The verdict: **Valid** (signed with the site's key, or a newer key the site's key handed over to), **Valid, but signed by a key you were not given**, or **Not valid** with the reason. Below it, every file the dossier holds: a report opens in the page as it was signed, a PDF in the browser's own viewer. A client who wants it installed, with a right-click **Check with GEA Reader** on dossiers, gets `GEA-Reader-Setup-0.80.0.exe` from the release page.
+4. The client opens `GEA-Reader.html` in any current browser, offline, and drops a dossier on it. The verdict: **Valid** (signed with the site's key, or a newer key the site's key handed over to), **Valid, but signed by a key you were not given**, or **Not valid** with the reason. Below it, every file the dossier holds: a report opens in the page as it was signed, a PDF in the browser's own viewer. A client who wants it installed, with a right-click **Check with GEA Reader** on dossiers, gets `GEA-Reader-Setup-0.81.0.exe` from the release page.
 5. **The key**: it lives in `keys\dossier_ed25519.json` in the workspace. The backup carries it; nothing else does; never send it. An administrator **rotates** it with a reason when a person who had access leaves; the old key's history rides in every later dossier so a reader of an old dossier still knows it was the site's.
 
 ## You know it worked when

{gea_program-0.80.0 → gea_program-0.81.0}/gea/help/tutorial/22-updates.md

@@ -8,7 +8,7 @@ Takes: 10 minutes
 1. Open **Audit / Update**, the card **The release**: the newest release on GitHub against the version running, with the three kits it carries - `GEA-Program-Setup`, `GEA-Reader-Setup` and `GEA-Recorder` - each with the SHA-256 GitHub recorded.
 2. Press **Fetch the kits** (the button names the version). A job brings them into the workspace's `installers\` folder, checks each against its recorded hash (a kit altered after that is not kept), and moves older kits to `installers\_older`. The card marks every kit on hand ✓.
 3. Press **Install now** (the button names the version). The program's setup runs silently from there with this workspace, and the reader's setup with it; the control panel stops for about a minute and is started again by a helper outside the program. Sign in again. The card now shows the new version running.
-4. The recorder's kit, `GEA-Recorder-0.80.0.tar.gz`, is in the same folder for the attendant to take to the box (lesson 25).
+4. The recorder's kit, `GEA-Recorder-0.81.0.tar.gz`, is in the same folder for the attendant to take to the box (lesson 25).
 5. On a computer that cannot reach GitHub, the setup from the release page installs over the old version the same way; the workspace is kept.
 
 ## You know it worked when

{gea_program-0.80.0 → gea_program-0.81.0}/gea/help/tutorial/25-install-recorder.md

@@ -5,10 +5,10 @@ Takes: 30 minutes
 > One script, one config file, one restart.
 
 ## Before you start
-The box assembled (lesson 24), the Pi on the pad network, and the release's `GEA-Recorder-0.80.0.tar.gz` - from the office's `installers\` folder (lesson 22) or the release page - copied to the Pi.
+The box assembled (lesson 24), the Pi on the pad network, and the release's `GEA-Recorder-0.81.0.tar.gz` - from the office's `installers\` folder (lesson 22) or the release page - copied to the Pi.
 
 ## Steps
-1. On the Pi, unpack the kit and run the installer once: `tar xzf GEA-Recorder-0.80.0.tar.gz`, `cd GEA-Recorder-0.80.0`, `sudo sh install.sh`. It makes `/opt/gea-recorder` (a Python environment of its own), writes the example config to `/etc/gea-recorder/config.json`, makes `/var/lib/gea-recorder`, enables SPI, enables the service to start at boot and runs the self-test.
+1. On the Pi, unpack the kit and run the installer once: `tar xzf GEA-Recorder-0.81.0.tar.gz`, `cd GEA-Recorder-0.81.0`, `sudo sh install.sh`. It makes `/opt/gea-recorder` (a Python environment of its own), writes the example config to `/etc/gea-recorder/config.json`, makes `/var/lib/gea-recorder`, enables SPI, enables the service to start at boot and runs the self-test.
 2. The clock: wire the GPS as lesson 24 says, then the three lines the README gives - `dtoverlay=pps-gpio,gpiopin=18` and `enable_uart=1` in `/boot/firmware/config.txt`, the two `refclock` lines in `/etc/chrony/chrony.conf` - `sudo apt install gpsd pps-tools`, and reboot. `chronyc tracking` then names PPS as the reference with an offset of microseconds.
 3. Edit the config: `sudo nano /etc/gea-recorder/config.json`. The site's name as the office spells it; the station id; the wellhead's latitude and longitude; each channel's ADC input, its id (`REF`, `S01`...), its kind (`geophone` or `electrode`) and its place in feet east and north of the wellhead; the ADC driver `ads1256` (`sim` records a test signal with no hardware); the rig feed - `rig.enabled`, the serial port or the TCP host and port the EDR offers; the mirror path for the USB stick.
 4. `sudo systemctl restart gea-recorder`. Open the box's page from any computer on the pad network: port 8780 of the box's address - `http://192.168.1.50:8780/` when that is its address. It shows the site, the station, RECORDING, the clock and what its time is worth, every channel's level, the files closed, the free space, the rig feed.

{gea_program-0.80.0 → gea_program-0.81.0}/gea/help/tutorial/28-driller-office.md

@@ -9,11 +9,11 @@ GEA Driller is a program for the rig PC. It reads the rig's own feed and the pre
 
 ## Steps
 1. Open **Drill string**; the card **GEA Driller** is at the bottom. Press **Start the twin as the rig**: the driller's own program runs on this computer with a scene drilling itself under the agent, one step every three seconds. Press **Open its screen**.
-2. Read the screen: the green band is the model's layer window, the blue line the hole from the surveys, the orange dot the bit, the dotted stub where the recommendation points, and the orange band where the position filter puts the layer from the readings - the tile beside it says how sure it is that the bit is in the layer and how far the top and the base are. Under the section, the plan view: looking down, the plan line across the middle, the corridor as a green band each side of it, the hole from the surveys' azimuths, and the stub of the turn the recommendation's aim asks for; the tile **off the plan line** says how far right or left the bit sits. The recommendation in words - the build or drop and the aim of the azimuth, with the turn it asks, as one toolface - with its reasons - what the deep-resistivity tool says when the scene has one, the gamma against the model's values, the model's bracket, the azimuth against the plan's and the offset in the corridor, the limits - and the confidence of each choice. The rig's numbers against the limits. The decisions so far, and whether they were answered.
+2. Read the screen: the green band is the model's layer window, the blue line the hole from the surveys, the orange dot the bit, the dotted stub where the recommendation points, and the orange band where the position filter puts the layer from the readings - the tile beside it says how sure it is that the bit is in the layer and how far the top and the base are. Under the section, the plan view: looking down, the plan line across the middle, the corridor as a green band each side of it, the hole from the surveys' azimuths, and the stub of the turn the recommendation's aim asks for; the tile **off the plan line** says how far right or left the bit sits. The recommendation in words - the build or drop and the aim of the azimuth, with the turn it asks, as one toolface - with its reasons - what the deep-resistivity tool says when the scene has one, the gamma against the model's values, the model's bracket, the azimuth against the plan's and the offset in the corridor, the limits - and the confidence of each choice. The rig's numbers against the limits - the vibration tile says where its index came from: the downhole tool, or read off the surface torque, weight and hook load when the string has none. The decisions so far, and whether they were answered.
 3. Type your name and press **Accept** on a recommendation; press **Reject** on the next; press **Did something else…** and record a build of +1.5°/100 ft aimed 4° left of the plan at 25 klb on a third. Each answer is on the record with your name; the twin drills on under the agent.
 4. The closed loop: **Arm for this section** to 300 ft further, confirm. The panel turns red: every decision is now a command, and the agent's panel says the null downlink kept it and sent nothing. **Disarm now**, or wait for the section's end - it disarms itself, and says why.
 5. Back in GEA, choose the well the records go under and press **Pull from it**: a job fetches the records, checks each against its SHA-256 and keeps them under the well. The table says how many decisions, accepted, rejected, done otherwise, the hole under advice, the armed sections and the commands; the last decisions are listed below. **Stop it** closes the twin's records.
-6. **Shadow a drilled well**: choose a well with a drilling-recorder export and press it. A job replays the drilled lateral through the advisor - at every 30 ft the agent sees only what the rig had shown to that point - and sets its recommendation beside what the record did next; the table says how often the steer agreed or opposed, the weight, speed and flow, and at each stretch the gamma marks as out of the layer whether the advisor called the way back at the first reading; the **SHADOW MODE** report under the well's reports has the drawing. Nothing of the export leaves this computer.
+6. **Shadow a drilled well**: choose a well with a drilling-recorder export and press it. A job replays the drilled lateral through the advisor - at every 30 ft the agent sees only what the rig had shown to that point - and sets its recommendation beside what the record did next; the table says how often the steer agreed or opposed, the weight, speed and flow, at each stretch the gamma marks as out of the layer whether the advisor called the way back at the first reading, and how often the vibration index read off the record's surface torque and weight stood over the limit and the advisor eased there; the **SHADOW MODE** report under the well's reports has the drawing. Nothing of the export leaves this computer.
 7. A real rig PC: its address in **The rig PC's address** (`http://192.168.1.60:8790`), the well, **Pull** - the same table. **Open the driller's screen** opens its screen from here. Over a modem, the rig PC joins GEA-VPN as a member of kind `driller` (lesson 23) and the address is its private one, `http://10.77.0.4:8790`.
 
 ## You know it worked when