Challenges and advances for huntingtin detection in cerebrospinal fluid: in support of relative quantification
Bibliographic record
Abstract
) gene above a critical threshold of ~35 repeats resulting in expression of mutant HTT (mHTT). A promising treatment approach being tested in clinical trials is HTT lowering, which aims to reduce levels of the mHTT protein. Target engagement of these therapies in the brain are inferred using antibody-based assays to measure mHTT levels in the cerebrospinal fluid (CSF), which is frequently reported as absolute mHTT concentration based on a monomeric protein standard used to generate a standard curve. However, patient biofluids are a complex milieu of different mHTT protein species, suggesting that absolute quantitation is challenging, and a single, recombinant protein standard may not be sufficient to interpret assay signal as molar mHTT concentration. In this study, we used immunoprecipitation and flow cytometry (IP-FCM) to investigate different factors that influence mHTT detection assay signal. Our results show that HTT protein fragmentation, protein-protein interactions, affinity tag positioning, oligomerization and polyglutamine tract length affect assay signal intensity, indicating that absolute HTT quantitation in heterogeneous biological samples is not possible with current technologies using a single standard protein. We also explore the binding specificity of the MW1 anti-polyglutamine antibody, commonly used in these assays as a mHTT-selective reagent and demonstrate that mHTT binding is preferred but not specific. Furthermore, we find that MW1 depletion is not only incomplete, leaving residual mHTT, but also non-specific, resulting in pull down of some wildtype HTT protein. Based on these observations, we recommend that mHTT detection assays report only relative mHTT quantitation using normalized arbitrary units of assay signal intensity, rather than molar concentrations, in the assessment of central nervous system HTT lowering in ongoing clinical and preclinical studies, and that MW1-depletion not be used a method for quantifying wildtype HTT protein.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.023 | 0.016 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.003 | 0.002 |
| Research integrity | 0.003 | 0.006 |
| Insufficient payload (model declined to judge) | 0.002 | 0.003 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".