glacier-buffer-utac
GenesisAeon Package 99 — real glacial hydrological buffer ("peak water") and downstream buffer-loss cascade science. 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.
What's real here
- Huss & Hock (2018, Nature Climate Change): "peak water" — glacier runoff rises, peaks, then declines as ice mass shrinks; the decline removes a real hydrological buffer against summer/drought low water.
- Cauvy-Fraunie et al. (2016, Nature Communications): experimental 31% flow reduction → 6.5x (±1.8) benthic fauna density increase within 2 weeks; 14–16 months to recover; an 11% glacier-cover threshold for abrupt algal/herbivore biomass shifts (33-site field survey).
- Milner et al. (2017, PNAS): synthesis review of glacier shrinkage propagating into downstream hydrology, sediment and biogeochemistry.
- Dunkle et al. (2025, Ecology): loss of meltwater desynchronizes previously asynchronous glacier-/snow-/rain-fed stream resource dynamics.
- Xuan et al. (2026, Earth's Future): wetland glacier-meltwater dependence is spatially heterogeneous — strong near the glacier margin, fading with distance.
- The full glacier → wetland → vegetation → fauna cascade is honestly represented as a literature-supported hypothesis network, not a single measured causal chain — see DISCLAIMER.md.
Quickstart
pip install glacier-buffer-utac
from glacier_buffer_utac import (
ALL_CASCADE_STAGES,
is_below_glacier_cover_threshold,
buffer_sensitivity_multiplier,
recovery_time_months_range,
)
for stage in ALL_CASCADE_STAGES:
print(stage.name, "--", stage.mechanism)
print(is_below_glacier_cover_threshold(8.0)) # True
print(buffer_sensitivity_multiplier(0.3)) # 3.33... -- more sensitive as ice shrinks
print(recovery_time_months_range()) # (14, 16)
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-utac 1.0.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_utac-1.0.1.tar.gz | 14.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| glacier_buffer_utac-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.3 kB
Release files / glacier_buffer_utac-1.0.1.tar.gz
| Download URL | glacier_buffer_utac-1.0.1.tar.gz |
|---|---|
| Size | 14.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7fa0e0e1ef954061395818200375be536a67d6b8ba9f3828f7ef7c5a10d4c9d0
|
|
BLAKE2b-256 checksum How to use checksums |
8b50612c5f1c5001d1a5a64cee1964dc72f666edba65242631c7acac56bded38
|
| 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_utac-1.0.1-py3-none-any.whl
| Download URL | glacier_buffer_utac-1.0.1-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
25596ac33e3b807f4f12682083e0704c0219933d0021f96db0f3c7652d07994d
|
|
BLAKE2b-256 checksum How to use checksums |
282529bbf108d4bd7bec8ed82402a457958b5ec206e7468769ed28697dfa1aca
|
| 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-utac 1.0.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.