-
Notifications
You must be signed in to change notification settings - Fork 176
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
cram: Define coordinate system for alignment positions #810
Comments
It looks to be semi-defined. For alignment coordinate sorded data it is defined to be a delta against the container start coordinate. Although not explicitly defined, a delta implies 0 as being equal. So we coordinate sorted data we see this:
With unsorted data, we have "AP => 0" in the container header which turns off the deltas. Then we store AP verbatim instead of using deltas, and at that point we do indeed store 1-based coordinates. This is a good thing given unmapped data causes negative values, which was something I always disliked in BAM!
I'll amend the text to be explicit. The other places coordinates are used is in the PNEXT field. These too are 1-based, or 0 for unused.
At least it's consistently 1 based. Phew! |
This is in regard to CRAM format specification (version 3.1) (2024-09-04).
The coordinate system used for alignment positions is undefined. In practice, alignment positions are 1-based.
The text was updated successfully, but these errors were encountered: