An exemplary case of a bromine explosion event linked to cyclone development in the Arctic
Bibliographic record
Abstract
Intense, cyclone-like shaped plumes of tropospheric bromine monoxide (BrO) are regularly observed by GOME-2 on board the MetOp-A satellite over Arctic sea ice in polar spring. These plumes are often transported by high-latitude cyclones, sometimes over several days despite the short atmospheric lifetime of BrO. However, only few studies have focused on the role of polar weather systems in the development, duration and transport of tropospheric BrO plumes during bromine explosion events. The latter are caused by an autocatalytic chemical chain reaction associated with tropospheric ozone depletion and initiated by the release of bromine from cold brine-covered ice or snow to the atmosphere. In this manuscript, a case study investigating a comma-shaped BrO plume which developed over the Beaufort Sea and was observed by GOME-2 for several days is presented. By making combined use of satellite data and numerical models, it is shown that the occurrence of the plume was closely linked to frontal lifting in a polar cyclone and that it most likely resided in the lowest 3 km of the troposphere. In contrast to previous case studies, we demonstrate that the dry conveyor belt, a potentially bromine-rich stratospheric air stream which can complicate interpretation of satellite retrieved tropospheric BrO, is spatially separated from the observed BrO plume. It is concluded that weather conditions associated with the polar cyclone favoured the bromine activation cycle and blowing snow production, which may have acted as a bromine source during the bromine explosion event.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".