8000 Feature Request: call peaks for each replicate (diffbind), not only the merged data · Issue #367 · nf-core/atacseq · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Feature Request: call peaks for each replicate (diffbind), not only the merged data #367
Open
@lindenb

Description

@lindenb

Description of feature

Hi all, I've been asked to run diffbind on our ATACseq data; Unless I'm wrong diffbind requires a samplesheet with each replicate and, for each replicate a BAM and a peaks/bed: https://bioconductor.org/packages/release/bioc/vignettes/DiffBind/inst/doc/DiffBind.pdf

> samples
SampleID Tissue Factor Condition Treatment Replicate
1 BT4741 BT474 ER Resistant Full-Media 1
2 BT4742 BT474 ER Resistant Full-Media 2
3 MCF71 MCF7 ER Responsive Full-Media 1
4 MCF72 MCF7 ER Responsive Full-Media 2
5 MCF73 MCF7 ER Responsive Full-Media 3
6 T47D1 T47D ER Responsive Full-Media 1
7 T47D2 T47D ER Responsive Full-Media 2
8 MCF7r1 MCF7 ER Resistant Full-Media 1
9 MCF7r2 MCF7 ER Resistant Full-Media 2
10 ZR751 ZR75 ER Responsive Full-Media 1
11 ZR752 ZR75 ER Responsive Full-Media 2

bamReads ControlID bamControl
1 reads/Chr18_BT474_ER_1.bam BT474c reads/Chr18_BT474_input.bam
2 reads/Chr18_BT474_ER_2.bam BT474c reads/Chr18_BT474_input.bam
3 reads/Chr18_MCF7_ER_1.bam MCF7c reads/Chr18_MCF7_input.bam
4 reads/Chr18_MCF7_ER_2.bam MCF7c reads/Chr18_MCF7_input.bam
5 reads/Chr18_MCF7_ER_3.bam MCF7c reads/Chr18_MCF7_input.bam
6 reads/Chr18_T47D_ER_1.bam T47Dc reads/Chr18_T47D_input.bam
7 reads/Chr18_T47D_ER_2.bam T47Dc reads/Chr18_T47D_input.bam
8 reads/Chr18_TAMR_ER_1.bam TAMRc reads/Chr18_TAMR_input.bam
9 reads/Chr18_TAMR_ER_2.bam TAMRc reads/Chr18_TAMR_input.bam
10 reads/Chr18_ZR75_ER_1.bam ZR75c reads/Chr18_ZR75_input.bam
11 reads/Chr18_ZR75_ER_2.bam ZR75c reads/Chr18_ZR75_input.bam

Peaks PeakCaller
1 peaks/BT474_ER_1.bed.gz bed
2 peaks/BT474_ER_2.bed.gz bed
3 peaks/MCF7_ER_1.bed.gz bed
4 peaks/MCF7_ER_2.bed.gz bed
5 peaks/MCF7_ER_3.bed.gz bed
6 peaks/T47D_ER_1.bed.gz bed
7 peaks/T47D_ER_2.bed.gz bed
8 peaks/TAMR_ER_1.bed.gz bed
9 peaks/TAMR_ER_2.bed.gz bed
10 peaks/ZR75_ER_1.bed.gz bed
11 peaks/ZR75_ER_2.bed.gz bed

but, as far as I understand (Am i wrong ?) the peak calling is only generated for the merged data, so i would be nice to have an option to generate the peaks for each replicate. (Unless there is a cool nf-project that is able to find the differential peaks between two ATACSeq conditions, but I have not found it )

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0