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

Are output coordinates one or zero-based? #55

Open
rauldiul opened this issue Nov 18, 2021 · 3 comments
Open

Are output coordinates one or zero-based? #55

rauldiul opened this issue Nov 18, 2021 · 3 comments

Comments

@rauldiul
Copy link

Hi!

Thank you for your work!!

I have a simple question: the epic2 output comes in BED-similar format, however, I'm not sure if the output is really 0-based. When I do peak calling, if I check the minimum peak size obtained (which should be equal to the --bin-size argument), by doing End - Start, I get 1 bp less than --bin-size.

E.g. when peak calling with default parameters, the minimum peak size I observe is 199 bp. Thus, to get 200 bp, I would have to do End - Start + 1, which is compatible with the output being 1-based instead of 0-based.

Could you confirm this?

thanks for your help!

@endrebak
Copy link
Member

I just followed what SICER did. 0-199, 200-499 etc. This means that the start is 0-based and the end is 1-based

@endrebak
Copy link
Member

:)

@rauldiul
Copy link
Author

Thanks for the response!
But then (and sorry for the misguided/ignorant question), does that mean that the window sizes are actually 199 bp wide?
I was trying to compare them to the UCSC coordinate systems where 0-start + 1-end means the end coordinate is excluded from the intervals. But maybe the meaning here is different or I am (probably) confused.

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