differential-tad-analysis

Identify differential TADs by comparing normalized Hi-C matrices with HiCExplorer.

12|3|Updated Nov 4, 2025
One-click install
npx skills add https://github.com/BIsnake2001/ChromSkills --skill differential-tad-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: differential-tad-analysis
Source: https://github.com/BIsnake2001/ChromSkills/tree/main/20_toolBased.differential-tad-analysis
Command: npx skills add https://github.com/BIsnake2001/ChromSkills --skill differential-tad-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify differential TADs between two conditions by comparing normalized Hi-C matrices with HiCExplorer's hicDifferentialTAD to reveal significantly altered chromatin domains.

Core Features & Use Cases

  • Normalize Hi-C matrices from two conditions for fair comparison.
  • Compute differential TADs using HiCExplorer and output BED/GFF/TAD score reports.
  • Visualize differential interactions and map changes onto contact maps for interpretation.

Quick Start

Provide target and control sample names, genome assembly, and Hi-C data paths to begin the differential TAD workflow.

Frequently Asked Questions about differential-tad-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect differential TADs between two conditions from Hi-C data?

Differential TADs are detected by comparing normalized Hi-C matrices from two conditions using HiCExplorer's hicDifferentialTAD. The workflow identifies statistically significant changes in chromatin domains and exports BED, GFF, and TAD score reports.

What inputs are required for differential TAD analysis with HiCExplorer?

Differential TAD analysis requires two Hi-C or mcool files representing target and control conditions, a genome assembly, a chosen resolution, and output directories for normalization, TAD calling, and plots.

Do I need to define TADs before running differential TAD analysis?

Yes, TADs must already be defined for the target condition before detecting differential TADs. The workflow assumes prior TAD calling to detect statistically significant changes between the two conditions.

Can I visualize differential interactions on contact maps using this workflow?

Yes, the workflow visualizes differential interactions and maps changes onto contact maps. This helps interpret the statistically significant chromatin domain alterations between the two conditions.

What file formats are exported when computing differential TADs?

Computing differential TADs exports BED, GFF, and TAD score reports. These files capture the normalized matrix comparisons and statistically significant chromatin changes detected by HiCExplorer.

Why does my differential TAD workflow require matrix normalization?

Matrix normalization is required to ensure a fair comparison between two Hi-C conditions. Normalizing the matrices before calling differential TADs prevents bias in detecting statistically significant chromatin changes.