Skip to content
New issue

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

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

Already on GitHub? # to your account

Mean fragment size is short than read length #277

Open
xie186 opened this issue Jan 23, 2019 · 2 comments
Open

Mean fragment size is short than read length #277

xie186 opened this issue Jan 23, 2019 · 2 comments

Comments

@xie186
Copy link

xie186 commented Jan 23, 2019

Command line:

callpeak -f BAMPE -g mm -t IP.bam -c input.bam -n test--outdir macs2_outdir/

Version: 2.1.2

Read length is 150 bps. But the "#1 mean fragment size " is 94 bps by macs2

#1 mean fragment size is determined as 94 bp from treatment

Could someone help me explain this? Thanks.

@wwang-chcn
Copy link

That means the major part of fragment size in you sequencing library is short than 150bp. If you run fastqc for you reads, you will probably find a increase of adapter content on the 3'.

@xie186
Copy link
Author

xie186 commented Jan 25, 2019

Thanks for the reply @wwang-chcn.
This is the fastqc results:
image

It seems that there is no adapter contamination. I also checked the bam files generated. The reads were well aligned with "150M".

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

No branches or pull requests

2 participants