MétaCan
Menu
Back to cohort
Record W2476677144 · doi:10.5964/jnc.v2i2.17

The relationship between problem size and fixation patterns during addition, subtraction, multiplication, and division

2016· article· en· W2476677144 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Numerical Cognition · 2016
Typearticle
Languageen
FieldMathematics
TopicCognitive and developmental aspects of mathematical skills
Canadian institutionsCarleton University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsOperandSubtractionDivision (mathematics)ArithmeticMultiplication (music)Fixation (population genetics)MathematicsComputer scienceCombinatorics

Abstract

fetched live from OpenAlex

Eye-tracking methods have only rarely been used to examine the online cognitive processing that occurs during mental arithmetic on simple arithmetic problems, that is, addition and multiplication problems with single-digit operands (e.g., operands 2 through 9; 2 + 3, 6 x 8) and the inverse subtraction and division problems (e.g., 5 – 3; 48 ÷ 6). Participants (N = 109) solved arithmetic problems from one of the four operations while their eye movements were recorded. We found three unique fixation patterns. During addition and multiplication, participants allocated half of their fixations to the operator and one-quarter to each operand, independent of problem size. The pattern was similar on small subtraction and division problems. However, on large subtraction problems, fixations were distributed approximately evenly across the three stimulus components. On large division problems, over half of the fixations occurred on the left operand, with the rest distributed between the operation sign and the right operand. We discuss the relations between these eye tracking patterns and other research on the differences in processing across arithmetic operations.

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.006
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.298
Threshold uncertainty score0.751

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.006
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.000
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.039
GPT teacher head0.303
Teacher spread0.264 · 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