I need some quick clarification about –f BAMPE vs. –f BAM in mac2 callpeak. Does the bampe use a specific bampe format that is fundamentally different from bam? As an example, do –f bam and –f bampe formats differ in a similar manner to standard BED vs. the BEDPE that bedtools defined? Or does the –f bampe option search for both paired-end fragments based on various flags (such as those defined in SAM)? From a number of posts I have seen on this discussion group, the –f bampe option apparently does the latter, and uses flags to associate 2 reads contained in a single bam file to a peak. Am I interpreting this correctly?
I have tried both –f bam and –f bampe on my paired-end chipSeq data. Both work fine, and I really like the –f bampe option. I just want to verify I am doing the peak calls correctly
Thanks in advance for any help and input!
Chris
Here are snippets some of the earlier discussions that make me believe the –f bampe uses standard bam format for paired-end data, as opposed to requiring a special bampe format:
BAMPE in MACS2, original post 10/2/13
“# Command line: callpeak -t /media/Data/Storage/FILE.bam --format BAMPE”
Inquiry about Pair-end ChIP-seq data mapping:, original post 5/21/12
“To use pair-end support, try command like: macs2 callpeak -f BAMPE ...”
--
You received this message because you are subscribed to the Google Groups "MACS announcement" group.
To unsubscribe from this group and stop receiving emails from it, send an email to macs-announcem...@googlegroups.com.
To post to this group, send email to macs-ann...@googlegroups.com.
Visit this group at http://groups.google.com/group/macs-announcement.
For more options, visit https://groups.google.com/d/optout.
posSorted | nameSorted |
18804 | 18804 |
32194 | 34648 |
9011 | 9011 |
51321 | 58742 |
25191 | 27453 |
41777 | 44672 |