A Lagrangian study on the structure and pathways of the Irminger Current
Bibliographic record
Abstract
The Irminger Current (IC), located over the western flank of the Reykjanes Ridge, is a contributor to the northward volume transport related to the Atlantic Meridional Overturning Circulation.Previous studies showed that the IC is associated with a region of enhanced eddy kinetic energy. Using high-resolution mooring data from 2014 – 2020 combined with satellite altimetry, a strong intensification in volume transport of the IC in August 2019 could be attributed to the presence of mesoscale eddies in the vicinity of the moorings. At this time, altimetry showed an anticyclone lingering next to a cyclone in the mooring array, which intensified northward velocities within the IC. This example shows that mesoscale variability can directly impact the transport variability of the IC.Further research presented here uses the high-resolution model POP (Parallel Ocean Program, 1/10°) to investigate the pathways of the IC up- and downstream of the mooring array. Here, the focus lies on determining the origin of waters feeding the IC and the role of mesoscale eddies in shaping the current and its pathways using Lagrangian particle tracking with the Ocean Parcels software. First results from a backtracking experiment reveal different origins for the water masses feeding the respective cores of the IC. Waters of the eastern core mostly originate from the eastern side of the Reykjanes Ridge. The western core appears to contain a substantial amount of waters from the interior Irminger Sea that partly recirculate from the Labrador Sea.Additionally, we explore the mesoscale variability within the whole eastern Irminger Sea to investigate the potential impact of mesoscale eddies on restratification in the central Irminger Sea. We focus on identifying the characteristics of variability along the ridge using the output of the Lagrangian particle tracking in POP. First results from a forward experiment show stronger mesoscale activity in the western core than the eastern core, which is in line with available mooring observations.
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.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 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".