You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The record counter field in both the container (§ 7 "Container header structure") and slice headers (§ 8.5 "Slice header block") is described to be a "1-based sequential index of records in the file/stream."
However, current implementations write 0-based values, e.g., htslib:
I would expect the record counters to be 1 and 3 if they were to be 1-based. Is the description in the spec incorrect, or is the field missing a more thorough explanation on how its supposed to be tracked?
The text was updated successfully, but these errors were encountered:
zaeleus
changed the title
cram: Questionable record counter field description
cram: Record counter field description is possibly off-by-one
Feb 4, 2025
This is in regard to CRAM format specification (version 3.1) (2024-09-04).
The record counter field in both the container (§ 7 "Container header structure") and slice headers (§ 8.5 "Slice header block") is described to be a "1-based sequential index of records in the file/stream."
However, current implementations write 0-based values, e.g., htslib:
I would expect the record counters to be 1 and 3 if they were to be 1-based. Is the description in the spec incorrect, or is the field missing a more thorough explanation on how its supposed to be tracked?
The text was updated successfully, but these errors were encountered: