hic-loop-calling

Detect chromatin loops from Hi-C data using cooltools and output BEDPE files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chromatin loop detection from Hi-C data is complex and multi-step, requiring input validation, coordinate harmonization, data extraction, and loop identification. This skill automates a reproducible workflow to detect loops from Hi-C data stored in .mcool/.cool/.hic formats, delivering loop calls and preparation views for visualization.

Core Features & Use Cases

  • End-to-end loop calling workflow starting from processed Hi-C inputs.
  • Harmonizes chromosome names to the "chr" convention and generates chromosome-arm views for downstream analyses.
  • Extracts contact matrices at a user-selected resolution and outputs BEDPE loop calls alongside supporting view files.
  • Use case: starting from a .mcool file, call loops at 5 kb resolution and produce ${sample}_loop_calling/loops/${sample}_loops_5000.bedpe plus temporary view files for IGV.

Quick Start

Provide sample name, genome assembly, and Hi-C data path (.mcool/.cool/.hic) to run the loop-calling workflow and generate outputs.

Frequently Asked Questions about hic-loop-calling

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

FAQPage Schema
How do I detect chromatin loops from mcool or hic files?

Detect chromatin loops from mcool or hic files by providing a sample name, genome assembly, and data path to automate extraction and loop calling. The workflow outputs BEDPE loop calls and supporting view files.

Can I call Hi-C loops at a specific resolution with cooltools?

You can call Hi-C loops at a specific resolution with cooltools by specifying a loop-resolution input. The workflow extracts contact matrices at your chosen resolution and generates BEDPE loop files.

Why does my Hi-C loop calling fail due to chromosome name formats?

Hi-C loop calling can fail due to inconsistent chromosome names, so this workflow harmonizes chromosome names to the "chr" convention. This standardization ensures proper coordinate matching during contact matrix extraction and loop calling.

Do I need to generate chromosome-arm view files for Hi-C loop detection?

You do not need to manually generate chromosome-arm view files for Hi-C loop detection. The workflow automatically generates these temporary view files for downstream analysis and visualization in IGV.

What is the best way to automate BEDPE loop calling from processed Hi-C data?

The best way to automate BEDPE loop calling from processed Hi-C data is using an end-to-end workflow that validates inputs, harmonizes coordinates, extracts matrices, and runs loop calling. This delivers reproducible BEDPE loop calls and view artifacts.

Does this loop calling workflow support cool and hic formats besides mcool?

This loop calling workflow supports cool and hic formats besides mcool. It accepts processed Hi-C inputs in .mcool, .cool, or .hic formats to produce BEDPE loop calls and temporary view files.