Using the HepaCometChip Assay for Broad‐Spectrum DNA Damage Analysis
Bibliographic record
Abstract
Exposure to DNA damaging agents can lead to mutations that cause cancer. The liver is particularly vulnerable because it contains high levels of Cytochrome P450 enzymes that can convert xenobiotics into DNA reactive metabolites that form potentially carcinogenic bulky DNA adducts. As such, current requirements for preclinical testing include in vivo testing for DNA damage in the liver, which often requires many animals. Given that efforts are underway in many countries to reduce or eliminate the use of animals in research, there is a critical need for fast and robust in vitro tests to discern whether xenobiotics or potential pharmaceutical agents can damage the hepatocyte genome. One possible approach is to leverage the alkaline comet assay, which is used to assess genotoxicity based on the ability of damaged DNA to become free to migrate toward the anode during electrophoresis. The comet assay, however, has several limitations. The assay is (i) slow and (ii) vulnerable to experimental noise, (iii) it is difficult to detect bulky DNA adducts since they do not directly affect DNA migration, and (iv) cell types typically used do not have robust metabolic capacity. To address some of these concerns, we have developed the "HepaCometChip" (a.k.a. the HepaRG CometChip), wherein metabolically competent cells are incorporated into a higher throughput CometChip platform. Repair trapping is used to increase sensitivity for bulky lesions: undetectable bulky lesions are converted into repair intermediates (specifically, single-strand breaks) that can be detected with the assay. Here, we describe a protocol for performing the HepaCometChip assay that includes handling and dosing of HepaRG cells and performing the CometChip assay. With its higher throughput, ability to capture metabolic activation, and sensitivity to bulky lesions, the HepaCometChip offers a potential alternative to the use of animals for genotoxicity testing. © 2022 The Authors. Current Protocols published by Wiley Periodicals LLC. Basic Protocol 1: HepaRG cell culturing and dosing Basic Protocol 2: CometChip assay.
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.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.008 | 0.007 |
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".