Skip to main content

carbon-sinks-utac

GenesisAeon CI Python 3.11+ License: MIT DOI

GenesisAeon Package 59 — combines two real, independent 2025/2026 corrections to global natural carbon sink capacity, plus a SPECULATIVE UTAC/CREP sink-stress bridge (this package's own, not established science — 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

  • Global Carbon Budget 2025 (ESSD 18, 3211, 2026): 2024 totals — 11.6 GtC/yr anthropogenic emissions, 3.4 GtC/yr ocean sink, 1.9 GtC/yr land sink, 7.9 GtC/yr atmospheric growth (with the GCB's own disclosed ~1.6 GtC/yr budget imbalance).
  • Ocean sink correction (2025, real, upward): "Asymmetric bubble-mediated gas transfer enhances global ocean CO2 uptake", Nature Communications 16, 10595 (2025) — Plymouth Marine Laboratory & GEOMAR. Finds ocean CO2 uptake ~15% higher (average 1991-2020) than conventional estimates once bubble-transfer asymmetry is accounted for.
  • Land sink correction (2026, real, downward): O'Sullivan, M. et al., "An improved approach to estimate the natural land carbon sink", npj Climate and Atmospheric Science 9, 29 (2026). Finds the 2015-2024 decadal land sink is ~20% smaller than previously estimated (3.00 → 2.42 PgC/yr), because older models assumed fixed pre-industrial land cover.

Why both corrections, not just one

A package reporting only the negative land-sink correction would itself be an unbalanced, overly pessimistic picture — exactly the kind of "compounding crisis" overstatement this ecosystem's citation-accuracy discipline exists to catch. sink_revision.py computes the net effect of both real corrections together. The honest finding: crediting the real ocean-sink upgrade does not flip the overall picture positive — the land-sink correction is larger, so the net revision to estimated natural sink capacity is still a reduction, just a smaller one than looking at the land correction alone would suggest.

What's SPECULATIVE

utac_bridge.py maps a "sink-efficiency deficit" (how far current sink efficiency sits below a reference value) onto a UTAC steepness beta, using the same K / driver convention used elsewhere in the ecosystem. Unlike amoc-utac or amazon-utac, there is no established bistable tipping-point threshold for "carbon sink collapse" in the cited literature — this bridge is this package's own untested framework choice, not a re-derivation of a validated result.

Quickstart

pip install carbon-sinks-utac
from carbon_sinks_utac import CarbonSinksUTAC, compute_net_sink_revision

print(compute_net_sink_revision().summary())

sys = CarbonSinksUTAC()
result = sys.run_cycle()
print(result["net_revision_summary"])

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 carbon-sinks-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)

Source distribution for carbon-sinks-utac 1.0.1
File Size Uploaded Provenance
carbon_sinks_utac-1.0.1.tar.gz 15.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for carbon-sinks-utac 1.0.1
File Interpreter ABI Platform
carbon_sinks_utac-1.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 26.2 kB

Release files / carbon_sinks_utac-1.0.1.tar.gz

Download URL carbon_sinks_utac-1.0.1.tar.gz
Size 15.4 kB
Tags Source
SHA-256 checksum
How to use checksums
2c0e064b52bfb55c3bb2ab6f99c940efbca713e92de05e124261dc67aa309d69
BLAKE2b-256 checksum
How to use checksums
093d4aaaa97e050bb41a767453f6fa2134256adc827f4cccfd2f75eece8132e5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / carbon_sinks_utac-1.0.1-py3-none-any.whl

Download URL carbon_sinks_utac-1.0.1-py3-none-any.whl
Size 10.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
35e056ab74409a3904a072676a68313dbcba1731d534c8367d7cb5948568fe85
BLAKE2b-256 checksum
How to use checksums
06e44824772ba09b6f2382a7ce5555460874ee3c7a191e817e8a539f818fe3af
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Security for carbon-sinks-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.

Release history Release notifications | RSS feed

This release

1.0.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page