glacier-buffer-replacement-utac
GenesisAeon Package 100 — companion to glacier-buffer-utac (P99, the loss side). This package covers the replacement/mitigation side: Artificial Glacier Buffer Replacement (AGBR). Deliberately has no UTAC/CREP/AFET bridge — see DISCLAIMER.md.
For a plain-language explanation of the same topic (German, no jargon, written for general audiences), see WHITEPAPER.md.
Two explicit confidence tiers
- Core (
reservoir,mar,evaporation,mass_balance): real, peer-reviewed findings independently re-verified 2026-08-10 via direct paper/DOI lookup — not just copied from the originating DeepResearch report. - Optional / speculative (
peatland,rrf): weakly sourced or literally unpublished figures, kept because they were part of the original discussion. Always exposed with an explicit warning constant (PEATLAND_WEAK_SOURCE_WARNING,RRF_NOT_PEER_REVIEWED_WARNING).
What's real here (core)
- Farinotti, Pistocchi & Huss (2016, Environmental Research Letters): an optimally sited dam/reservoir strategy could offset up to 65% of the projected end-of-century summer-runoff change in the European Alps — a real, verified ceiling, not a guarantee.
- Steffen et al. (2022, Earth Surface Dynamics): 683 potential new Swiss proglacial lakes, 1.16 km³ total potential volume — but only ~10% realized by 2050 and ~48% by 2100 under a middle-of-the-road scenario.
- Fabbri et al. (2021, Swiss Journal of Geosciences): real Lake Brienz
sedimentation rates (3.0 cm/yr average, up to 4.7 cm/yr near deltas) —
the physical limiter on how long a proglacial reservoir stays useful.
v1.1.0 adds a second, mass-balance-based sedimentation model,
sediment_volume_loss_from_mass_input_m3(): given a sediment mass input rate (kg/yr), converts it to a volume-loss rate via a bulk sediment density of ~2200 kg/m³ (attributed to the same Steffen et al. 2022 source as the proglacial-lake figures, though this specific density value wasn't independently re-verified — see DISCLAIMER.md). - Ochoa-Tocachi et al. (2019, Nature Sustainability) and Jodar et al. (2022, Science of the Total Environment): two real, operating Managed Aquifer Recharge systems (Peruvian amunas, Spanish acequias de careo) — 45-day mean retention, +92% aquifer recharge respectively.
- Jin et al. (2023, Nature Sustainability) and Ilgen et al. (2024, Hydrological Sciences Journal): floating-solar evaporation mitigation, up to 49.7% at the Aswan High Dam's 90%-coverage case study.
- The core mass-balance argument (
mass_balance.py): full replacement of a glacier's hydrological buffer is physically impossible — a network can only redistribute existing water in time, never create new water.full_replacement_is_possible()always returnsFalse.
What's optional/speculative here
peatland.py: a storage-capacity range that mixes a weak (legal document) citation with a non-Alpine (Brazilian tropical peat) measurement — flagged, not load-bearing.rrf.py: the "Resilience Replacement Factor" and its three named scenarios, inherited from the originating AI DeepResearch report with no primary citation for the formula itself. Every function carriesRRF_NOT_PEER_REVIEWED_WARNING.
Quickstart
pip install glacier-buffer-replacement-utac
from glacier_buffer_replacement_utac import (
theoretical_mitigation_ceiling,
full_replacement_is_possible,
SWISS_ALPS_LAKE_POTENTIAL,
amuna_retention_days_mean,
aswan_case_study,
ALL_SCENARIOS,
RRF_NOT_PEER_REVIEWED_WARNING,
)
print(theoretical_mitigation_ceiling()) # 0.65 -- Farinotti et al. 2016
print(full_replacement_is_possible()) # False, always
print(SWISS_ALPS_LAKE_POTENTIAL)
print(amuna_retention_days_mean()) # 45
print(aswan_case_study()["evaporation_reduction_pct"]) # 49.7
print(RRF_NOT_PEER_REVIEWED_WARNING)
for scenario in ALL_SCENARIOS:
print(scenario.name, scenario.rrf_range)
Development
pip install -e ".[dev]"
pre-commit install
ruff check src tests
mypy src
pytest
Citation
See CITATION.cff and .zenodo.json.
Metadata
Release files for glacier-buffer-replacement-utac 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| glacier_buffer_replacement_utac-1.1.1.tar.gz | 23.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| glacier_buffer_replacement_utac-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.3 kB
Release files / glacier_buffer_replacement_utac-1.1.1.tar.gz
| Download URL | glacier_buffer_replacement_utac-1.1.1.tar.gz |
|---|---|
| Size | 23.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91fd145fb3019ac7c38e4eb394e1d850b4cb14378b6b625e856f39dd482e30d4
|
|
BLAKE2b-256 checksum How to use checksums |
19edd70017a65ea5d6d9e77ffac71328d1e360975fce08cb3368a9f9d3618689
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / glacier_buffer_replacement_utac-1.1.1-py3-none-any.whl
| Download URL | glacier_buffer_replacement_utac-1.1.1-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8812027670fb841c131aa1c3f3dbbfd8b0b094706c277c582411e56665e0716a
|
|
BLAKE2b-256 checksum How to use checksums |
ff7b7b48690ce4d3132169377ce196d5846181ed3b498e1036fce38125fe6f4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for glacier-buffer-replacement-utac 1.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.