Supraglacial Lake Fate Is Knowable Long Before the Season Ends

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2608.30113v1 Announce Type: new Abstract: A supraglacial lake on the Greenland Ice Sheet ends its melt season in one of four ways: it drains rapidly through a hydrofracture, drains slowly across the surface, refreezes in place, or is buried by late-season snowfall. Which one occurs decides whether the meltwater reaches the ice bed. Satellite classifiers recover the outcome accurately but only after the season closes, and how much of a season each outcome actually requires has never been measured. We measure it directly: holding the representation and the classifier fixed, we truncate the input at $14$ cutoffs from 1 May to 31 December, retrain at each, and record the earliest cutoff at which each outcome's per-class $F_1$ reaches a fixed target. The outcomes resolve in a consistent order, two of them months early: rapid drainage by 15 July and slow drainage by 1 August, $92$ and $75$ days ahead of the earliest date a full-season pipeline can be computed at all, with buried and refreeze following at $44$ and $30$ days. Five further learners, from a majority-class floor and $54$ summary statistics to a trigger-based early classifier, leave the ordering intact: every learner that produces a per-class trajectory reproduces it despite end-of-season accuracies differing by up to $18$ percentage points, and it survives leave-one-basin-out evaluation, though not the substitution of machine labels for expert ones in an unseen season. Every feature we compute at day $t$ reads only days up to $t$, at a cost of at most $1.3$ percentage points. A monitoring system should …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2608.30113
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.