MétaCan
Menu
Back to cohort

Task‐dependent differences in subjective fatigue scores

2005· article· en· W2007877124 on OpenAlex
Susan Richter, Karel Maršálek, Christiane Glatz, A. Gundel

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 Sleep Research · 2005
Typearticle
Languageen
FieldPsychology
TopicSleep and Work-Related Fatigue
Canadian institutionsTransport Canada
Fundersnot available
KeywordsVigilance (psychology)Sleep deprivationPsychologyTask (project management)Test (biology)AudiologyMental fatigueChecklistSleep lossCognitionCognitive psychologyMedicineApplied psychologyPsychiatryEngineering

Abstract

fetched live from OpenAlex

The aim of the present study was to evaluate time-on-task effects on subjective fatigue in two different tasks of varying monotony during night-time testing (20:00 to 4:00 hours) in a sleep deprivation intervention. The experiment included eight test runs separated by breaks of approximately 20 min. Twenty healthy volunteers performed a driving simulator and the Mackworth clock vigilance task in four of the test runs each. Sequence of tasks was varied across subjects. Before and after each task, subjective sleepiness was assessed by means of the Karolinska sleepiness scale and subjective fatigue was rated on the Samn-Perelli checklist. Fatigue and sleepiness significantly increased over the course of the night. Both tasks led to an increase in fatigue and sleepiness across test runs. However, this time-on-task effect was larger in the vigilance than in the driving simulator task. It is important to note that fatigue and sleepiness in one test run were not influenced by the task performed in the preceding test run, that is there were no cross-over effects. The results suggest that time-on-task effects superimpose circadian and sleep-related factors affecting fatigue. They depend on the monotony of the task and can be quantified by means of a design including separate test runs divided by breaks.

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.003
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: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.284
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.002
Insufficient payload (model declined to judge)0.0020.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.129
GPT teacher head0.420
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