-
Notifications
You must be signed in to change notification settings - Fork 0
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
Incorrect peakcalling #7
Comments
Hi Kévin, Sam |
Another potential reason: did you specify chrom sizes in this run? It can limit what reads to use for peak calling. |
Hi Sam, Here the command-line :
Here the .o file : Loading f-seq2/2.0.3
|
Is your data paired-end? If so, can you make sure it is in bedpe format? |
Yes ! It works ! Sorry I thought the BEDPE format was similar to the BED format! Thanks ! |
Hello,
Another big problem when using f-seq2:
Are these known problems?
When I use f-seq1, the calls are done correctly.
Half of the chromosome not processed by fseq2 :

Abnormal peaks on fseq2:

Thanks,
Kévin
The text was updated successfully, but these errors were encountered: