Reconstruction and analysis of the Chukchi Sea circulation in 1990–1991
Bibliographic record
Abstract
The Chukchi Sea (CS) circulation reconstructed for September 1990 to October 1991 from sea ice and ocean data is presented and analyzed. The core of the observational data used in this study comprises the records from 12 moorings deployed in 1990 and 1991 in U.S. and Russian waters and two hydrographic surveys conducted in the region in the fall of 1990 and 1991. The observations are processed by a two‐step data assimilation procedure involving the Pan‐Arctic Ice‐Ocean Modeling and Assimilation System (employing a nudging algorithm for sea ice data assimilation) and the Semi‐implicit Ocean Model [utilizing a conventional four‐dimensional variational (4D‐var) assimilation technique]. The reconstructed CS circulation is studied to identify pathways and assess residence times of Pacific water in the region; quantify the balances of volume, freshwater, and heat content; and determine the leading dynamical factors configuring the CS circulation. It is found that in 1990–1991 (high AO index and a cyclonic circulation regime) Pacific water transiting the CS toward the Canada basin followed two major pathways, namely via Herald Canyon (Herald branch of circulation, 0.23 Sv) and between Herald Shoal and Cape Lisburne (central branch of circulation and Alaskan Coastal Current, 0.32 Sv). The annual mean flow through Long Strait was negligible (0.01 Sv). Typical residence time of Pacific water in the region varied between 150 days for waters entering the CS in September and 270 days for waters entering in February/March. Momentum balance analysis reveals that geostrophic balance between barotropic pressure gradient and Coriolis force dominated for most of the year. Baroclinic effects were important for circulation only in the regions with large horizontal salinity gradients associated with the fresh Alaskan and Siberian coastal currents and the Cape Lisburne and Great Siberian polynyas. In the polynyas, the baroclinic effects were due to strong salinification and convection processes associated with sea ice formation.
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| 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".