MétaCan
Menu
Back to cohort
Record W2077860053 · doi:10.1029/2009je003413

Convective vortices and dust devils at the Phoenix Mars mission landing site

2010· article· en· W2077860053 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueJournal of Geophysical Research Atmospheres · 2010
Typearticle
Languageen
FieldPhysics and Astronomy
TopicPlanetary Science and Exploration
Canadian institutionsGeological Survey of CanadaYork University
Fundersnot available
KeywordsVortexMars Exploration ProgramAtmospheric sciencesOrbiterGeologyEddyConvectionNoonPolar vortexEnvironmental scienceMeteorologyPhysicsTurbulenceAstrobiologyAstronomy

Abstract

fetched live from OpenAlex

The Phoenix Mars Lander detected a larger number of short (∼20 s) pressure drops that probably indicate the passage of convective vortices or dust devils. Near‐continuous pressure measurements have allowed for monitoring the frequency of these events, and data from other instruments and orbiting spacecraft give information on how these pressure events relate to the seasons and weather phenomena at the Phoenix landing site. Here 502 vortices were identified with a pressure drop larger than 0.3 Pa occurring in the 151 sol mission (L s 76 to 148). The diurnal distributions show a peak in convective vortices around noon, agreeing with current theory and previous observations. The few events detected at night might have been mechanically forced by turbulent eddies caused by the nearby Heimdal crater. A general increase with major peaks in the convective vortex activity occurs during the mission, around L s = 111. This correlates with changes in midsol surface heat flux, increasing wind speeds at the landing site, and increases in vortex density. Comparisons with orbiter imaging show that in contrast to the lower latitudes on Mars, the dust devil activity at the Phoenix landing site is influenced more by active weather events passing by the area than by local forcing.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.505
Threshold uncertainty score0.397

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.031
GPT teacher head0.321
Teacher spread0.291 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it