GrapHi-C: Graph-based visualization of Hi-C Datasets
Bibliographic record
Abstract
Abstract Background Hi-C is a proximity-based ligation reaction used to detect regions of the genome that are close in 3D space (or “interacting”). Typically, results from Hi-C experiments (whole-genome contact maps) are visualized as heatmaps or Circos plots. While informative, these visualizations do not intuitively represent the complex organization and folding of the genome in 3D space, making the interpretation of the underlying 3D genomic organization difficult. Our objective was to utilize existing tools to generate a graph-based representation of a whole-genome contact map that leads to a more intuitive visualization. Methodology Whole-genome contact maps were converted into graphs where each vertex represented a genomic region and each edge represented a detected or known interaction between two vertices. Three types of interactions were represented in the graph: linear, intra-chromosomal ( cis -), and inter-chromosomal ( trans -) interactions. Each edge had an associated weight related to the linear distance (Hi-C experimental resolution) or the associated interaction frequency from the contact map. Graphs were generated based on this representation scheme for whole-genome contact maps from a fission yeast dataset where yeast mutants were used to identify specific principles influencing genome organization (GEO accession: GSE56849). Graphs were visualized in Cytoscape with an edge-weighted spring embedded layout where vertices and linear interaction edges were coloured according to their corresponding chromosome. Results The graph-based visualizations (compared to the equivalent heatmaps) more intuitively represented the effects of the rad21 mutant on genome organization. Specifically, the graph based visualizations clearly highlighted the loss of structural globules and a greater intermingling of chromosomes in the mutant strain when compared to the wild-type. The graph-based representation and visualization protocol developed here will aid in understanding the complex organization and folding of the genome.
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.009 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.006 | 0.005 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.034 | 0.005 |
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".