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

bug found? #49

Open
olechnwin opened this issue Mar 11, 2020 · 1 comment
Open

bug found? #49

olechnwin opened this issue Mar 11, 2020 · 1 comment

Comments

@olechnwin
Copy link

I was running idr on rep1 and rep2 and found out some of the output for rep2 do not match the rep2 narrowPeak file.
I'm copying one of the offending line below. As you can see, the rep2 end location and summit info are not correct. While the rep1 info are correct. This makes me worry about the results. I'm hoping someone can respond. Thanks!
idr file:
chr7 29413398 29416918 . 1000 . -1 213.82509 -1 2529 2.46 2.73 29413398 29416918 620.03809 2548 29413672 29416512 213.82509 702

and here is the associated peak in rep2 narrowPeak
chr7 29413672 29414923 rep2 2138 . 20.03013 213.82509 209.88286 676

FYI, the associated peak in rep1 narrowPeak is correct.
chr7 29413398 29416918 rep1 6200 . 25.59149 620.03809 615.40747 2548

@olechnwin
Copy link
Author

olechnwin commented Mar 12, 2020

Ok. I may have found why the discrepancies.
The reason why I cannot find the rep2 peak with exactly the same location was because there are several rep2 peaks that overlap in this region. Although, I wasn't able the find exactly the same location (they are off by 7 bp) after merging all those rep2 peaks that overlap, I'm now thinking that this may not a bug as it may have some other overlapping peaks that I somehow missed.

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

1 participant