MétaCan
Menu
Back to cohort

Where is the solar dynamo?

2013· article· en· W2088763449 on OpenAlex
Paul Charbonneau

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 Physics Conference Series · 2013
Typearticle
Languageen
FieldPhysics and Astronomy
TopicSolar and Space Plasma Dynamics
Canadian institutionsUniversité de Montréal
Fundersnot available
KeywordsDynamoTachoclineSolar dynamoPhysicsConvection zoneDynamo theoryConvectionMagnetic fieldGeophysicsMechanicsAstrophysicsComputational physicsClassical mechanics

Abstract

fetched live from OpenAlex

In this paper I review results from recent global magnetohydrodynamical numerical simulations of solar convection, as a springboard to address the question "Where is the solar dynamo". I first describe and contrast similarities and differences in the large-scale flows and magnetic fields such simulations can produce, with emphasis on polarity reversals (or lack thereof) in the large-scale magnetic components they generate. On the basis of these simulation results, I argue that some of the significant differences in the spatiotemporal evolution of the large-scale magnetic field can be traced to the competing effects of turbulent electromotive forces and induction by large-scale flows, whose mutual near-cancellation in the nonlinearly saturated regime leads to a high sensitivity to the numerical/physical treatment of small scales. Some of these recent simulation results also reopen the possibility that dynamo action driving the solar activity cycle may reside entirely within the convection zone, with the tachocline perhaps playing a lesser role than has been assumed in the last two decades. On the other hand, other subsets of simulations suggest that magnetohydrodynamical processes taking place within the tachocline may have a significant impact on timescales comparable to or longer than the primary cycle.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.349
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.009
GPT teacher head0.217
Teacher spread0.208 · 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