MétaCan
Menu
Back to cohort
Record W2925707131 · doi:10.1177/0333102418815503

Genetics of cluster headache

2019· review· en· W2925707131 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

VenueCephalalgia · 2019
Typereview
Languageen
FieldMedicine
TopicMigraine and Headache Studies
Canadian institutionsXenon Pharmaceuticals (Canada)
Fundersnot available
KeywordsCluster headacheMedicineGeneticsFamily medicinePsychiatryMigraineBiology

Abstract

fetched live from OpenAlex

Background Cluster headache is the most severe primary headache disorder. A genetic basis has long been suggested by family and twin studies; however, little is understood about the genetic variants that contribute to cluster headache susceptibility. Methods We conducted a literature search of the MEDLINE database using the PubMed search engine to identify all human genetic studies for cluster headache. In this article we provide a review of those genetic studies, along with an overview of the pathophysiology of cluster headache and a brief review of migraine genetics, which have both been significant drivers of cluster headache candidate gene selection. Results The investigation of cluster headache genetic etiology has been dominated by candidate gene studies. Candidate selection has largely been driven by the pathophysiology, such as the striking rhythmic nature of the attacks, which spurred close examination of the circadian rhythm genes CLOCK and HCRTR2. More recently, unbiased genetic approaches such as genome-wide association studies (GWAS) have yielded new genetic avenues of interest including ADCYAP1R1 and MME. Conclusions The majority of candidate genes studied for cluster headache suffer from poor reproducibility. Broader genetic interrogation through larger unbiased GWAS, exome, and whole genome studies may provide more robust candidates, and in turn provide a clearer understanding of the causes of cluster headache.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.717
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.0030.001
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.122
GPT teacher head0.402
Teacher spread0.280 · 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