marine-heatwave-utac
GenesisAeon Package 119 — real marine heatwave frequency, duration, and depth-penetration trends for Southeast Asia, plus a real, literature- reported coupling to El Nino and the Indian Ocean Dipole. 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.
Where this package came from
Built alongside el-nino-amplification-utac (P118) and
antarctic-ice-shelf-utac (P120) from a single broad DeepResearch pass
(2026-08-31). Checked directly against PACKAGE_REGISTRY.md: no
existing package covered marine heatwaves.
What's real here
- Gulakaram et al. (2026, JGR: Oceans) — marine heatwave frequency up 108% and duration up 63% in Southeast Asia (2003-2023 vs. 1982-2002); event rate rose from <2/year in the 1980s to 5/year by the 2010s.
- Depth penetration — surface-intensified warming reaches ~25m broadly; subsurface-intensified signals reach up to 131m in the tropical western Pacific but only 56m in the South China Sea — a real regional difference, not a single averaged depth.
- Climate mode coupling — the strongest recorded events (1998,
2015-2016) coincided with concurrent El Nino and positive Indian
Ocean Dipole phases, a real compounding-effect finding linking this
package to
el-nino-amplification-utac.
Deliberately not one-sided
depth_signal_is_spatially_uniform() returns False — the western
Pacific and South China Sea depth signals differ by more than a factor
of two; this package documents both rather than reporting one averaged
number.
Installation
pip install marine-heatwave-utac
Quick start
from marine_heatwave_utac import (
frequency_increase_pct,
duration_increase_pct,
depth_signal_is_spatially_uniform,
is_strongest_mhw_linked_to_multiple_climate_modes,
)
frequency_increase_pct() # 108.0
duration_increase_pct() # 63.0
depth_signal_is_spatially_uniform() # False -- the honesty check
is_strongest_mhw_linked_to_multiple_climate_modes() # True
License
Code: MIT. Documentation/data notes: see DISCLAIMER.md.
Citation
See CITATION.cff.
Metadata
Release files for marine-heatwave-utac 1.1.0
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 | |
|---|---|---|---|---|
| marine_heatwave_utac-1.1.0.tar.gz | 11.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| marine_heatwave_utac-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.6 kB
Release files / marine_heatwave_utac-1.1.0.tar.gz
| Download URL | marine_heatwave_utac-1.1.0.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5e7c85354ffc2087dfb9fa3ce3cfb55aea8243b196a7d43cae6c6e6dc75b0a38
|
|
BLAKE2b-256 checksum How to use checksums |
d00006d98313ba560df42a604c08f0848a1688d6c32706245911d5d44faf3f39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / marine_heatwave_utac-1.1.0-py3-none-any.whl
| Download URL | marine_heatwave_utac-1.1.0-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4020b69e8352e25a8836d47490b5176766fd3db14aca44c1ef49f0eb431c60c
|
|
BLAKE2b-256 checksum How to use checksums |
b5dc396586f8596ff3bd43f025738caecd98dd8b25569a6edcffba5e431683f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for marine-heatwave-utac 1.1.0
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.