Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sorting issue #177

Open
mpalatucci opened this issue May 18, 2022 · 1 comment
Open

sorting issue #177

mpalatucci opened this issue May 18, 2022 · 1 comment

Comments

@mpalatucci
Copy link

Hi all I was hoping to find help here.

I am doing some ATAC_Seq analysis.

I am trying to compare peak callers Genrich (atac-seq specific) and MACS2 for the same dataset
From what I have read, because I'm dealing with paired end reads, it makes the most sense to sort my final bam files by name. In addition, Genrich requires you to sort the bam files by name for the peak calling.

Due to the sorting by name, I'm running into issues with differential peak calling with diffbind, which requires the bam files to be sorted by coordinates.

soo... I have a couple questions i'm hoping to receive some clarification on:

  1. is it ok if my bam files for diffbind are sorted by coordinate but my peaks were called by name sorting?
  2. are there any discrepancies this differential sorting of bam and peak files may cause that I should be aware of ?

any help greatly appreciated!

@brentp
Copy link
Owner

brentp commented May 19, 2022

In order to use mosdepth, your data must be coordinate sorted. I don't know about peak calling, that would depend on the tool that's used for that application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants