MétaCan
Menu
Back to cohort

Measuring nightmare and bad dream frequency: impact of retrospective and prospective instruments

2008· article· en· W2170571870 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 Sleep Research · 2008
Typearticle
Languageen
FieldNeuroscience
TopicSleep and Wakefulness Research
Canadian institutionsUniversité de Montréal
Fundersnot available
KeywordsNightmareDreamChecklistNarrativeRetrospective cohort studyRecallPsychologyProspective cohort studyMedicinePsychiatrySurgeryCognitive psychologyLiteratureArt

Abstract

fetched live from OpenAlex

Studies on nightmare frequency have yielded inconsistent results. We compared the frequency of nightmares and bad dreams obtained with retrospective methods (annual and monthly estimates) and with two types of prospective measures (narrative and checklist logs). Four hundred and eleven participants completed retrospective estimates of nightmare and bad dream frequency and recorded their dreams in either narrative or checklist logs for 2-5 weeks. When measured prospectively with narrative logs, nightmare frequency was marginally higher than the 1-year estimate (P = 0.057) but not significantly different from the 1-month estimate (P > 0.05). Prospective bad dream frequency was significantly greater than the two retrospective estimates (ps < 0.0005). There were no significant differences in the frequency of nightmares and bad dreams reported prospectively with narrative versus checklist logs (ps > 0.05). However, checklist logs yielded a significantly greater number of everyday dreams per week (P < 0.0001). Taken together, the results provide partial support for the idea that when compared to daily logs, retrospective self-reports significantly underestimate current nightmare and bad dream frequency. Prospective studies of dream recall and nightmare frequency should take into account the type of log used, its duration, and the participants' level of motivation over time.

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.002
metaresearch head score (Gemma)0.002
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.049
Threshold uncertainty score0.501

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.001
Scholarly communication0.0000.001
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.133
GPT teacher head0.371
Teacher spread0.238 · 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