-
Notifications
You must be signed in to change notification settings - Fork 21
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
bed file #14
Comments
hi @xiucz thanks for this report! cnvkit outputs a 1-based copy number segment format from the documentation here: on the page you linked we run this to convert the 1-based coordinates from cnvkit to 0-based to match the bed file
So at this point WGS_Tumor_merged_sorted_mrkdup_bqsr.cns remains 1-based but WGS_Tumor_merged_sorted_mrkdup_bqsr.2.cns is now 0-based I often refer to this biostarts post when doing these coordinate conversions we the run bedtools intersect on the 0-based bed file and the 0-based segment file. so at this point bedtools intersect is working on two 0-based files so everything I think should be fine Let me know if you disagree or if i've misunderstood the issue you've presented |
Hi,
This step, I agree with you, and the result file And I have one more suggestion, rename ".2.annotated.cns" to ".annotated.bed", this will be more clearly to know the coordination system of the file for newers. Thank you. |
Hi,
In this part, it writes
I know that bed file is 0-based but cns file is also 0-based(mimused by 1). But it seems that we should plus 1 to the start of every recode in the result cns file? Because the CNS format is 1-based.
Thanks for your reply.
The text was updated successfully, but these errors were encountered: