-
Notifications
You must be signed in to change notification settings - Fork 458
NEWS For End of 2025 Release. #1969
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
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -1,5 +1,106 @@ | ||||||||||||||||||||||||||||||||||||||
| Noteworthy changes in release a.b | ||||||||||||||||||||||||||||||||||||||
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||||||||||||||||||||||||||||||||||||||
| Updates | ||||||||||||||||||||||||||||||||||||||
| ------- | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| * Consolidate and simplify SAM header parsing. This considerably speeds up | ||||||||||||||||||||||||||||||||||||||
| parsing files with many SQ lines. | ||||||||||||||||||||||||||||||||||||||
| (PR #1947. PR #1953 fixes oss-fuzz issues 444492071, 444492076, 444547724, | ||||||||||||||||||||||||||||||||||||||
| 444490034) | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| * Switch from strtol to hts_str2uint in mod parsing for speed increase. | ||||||||||||||||||||||||||||||||||||||
| (PR #1957. Thanks to Chris Wright) | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| * Add UMI support to FASTQ input and output. See samtools/samtools#2270. | ||||||||||||||||||||||||||||||||||||||
| (PR #1960, fixes samtools/samtools#2259. Requested by Poshi) | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| * Removed direct access to htsFile struct members in some sample functions. | ||||||||||||||||||||||||||||||||||||||
| (PR #1963, fixes #1961. Reported by John Marshall) | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| * Add support for VCFv4.4 / VCFv4.5 "Number=" fields. | ||||||||||||||||||||||||||||||||||||||
| (PR #1874) | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| * Improved operation of filters that work with header data. Filter expressions | ||||||||||||||||||||||||||||||||||||||
| such as rname, mrname, rnext and library were not working well with iterators. | ||||||||||||||||||||||||||||||||||||||
| (PR #1959) | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| * Add Type to the INFO/FORMAT sanity check. This produces a warning on | ||||||||||||||||||||||||||||||||||||||
| incorrect Type usage. | ||||||||||||||||||||||||||||||||||||||
| (PR #1967, fixes #1937 and samtools/bcftools#2431. | ||||||||||||||||||||||||||||||||||||||
| Reported by Jukka Matilainen) | ||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
| * S3 reading code now reads in `chunks` to minimise S3 reading length when | ||||||||||||||||||||||||||||||||||||||
| doing a range request. Also this combines the reading, writing and | ||||||||||||||||||||||||||||||||||||||
| authorisation code into a single file. | ||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
| * S3 reading code now reads in `chunks` to minimise S3 reading length when | |
| doing a range request. Also this combines the reading, writing and | |
| authorisation code into a single file. | |
| * S3 reading code now reads in "chunks" to limit the amount of data read (and | |
| therefore egress costs) from the object store when doing a range request. | |
| Also this combines the reading, writing and authorisation code into a single | |
| file. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * Recognise the tabix comment character (-c) when reading records. | |
| * Make tabix skip comments (-c) wherever they occur, not just at the start of | |
| the file. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * Fix embed_ref=2 on SEQ * and MD:Z tag. The combination of no sequence and | |
| MD:Z with embed_ref=2 caused the slice extents to be miscalculated. | |
| * Fix embed_ref=2 on SEQ * and MD:Z tag. The combination of no sequence and | |
| MD:Z with embed_ref=2 caused the slice extents to be miscalculated, | |
| causing invalid CRAM output to be written. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be in the Updates section, as it's a fairly significant change in behaviour. This came out a bit long, but I think it's important to highlight exactly what changed here.
| * Internally store phase in VCF4.4 format irrespective of input file format. | |
| This should prevent problems when dealing with different VCF versions. | |
| * HTSlib 1.22 changed the VCF reader so that it stored GT prefixed phasing | |
| information, but only for files specifying `fileformat=VCFv4.4` or higher. | |
| This caused problems when merging files with different versions, so the | |
| VCF reader will now store prefixed phasing information irrespective of | |
| the VCF version listed in the file headers. For files up to VCFv4.3, the | |
| first phasing bit will be set if all other alleles are phased, and cleared | |
| otherwise (following the rules for VCFv4.4 onwards where no explicit | |
| phasing symbol is present). This will also happen when reading BCF. | |
| When accessing GT data, it is no longer safe to assume that the phasing | |
| is set to zero even if the file reports a version earlier than VCFv4.4. | |
| Interfaces such as `bcf_gt_allele()` should always be used to access | |
| GT allele data. | |
| For compatibility, prefixed phasing will be stripped when writing VCF | |
| files with version 4.3 or earlier. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * Prevent the dropping of in-flight decode jobs when seeking in | |
| cram_next_slice(). | |
| * Fix bug where multi-threaded CRAM iterators could drop long alignments | |
| starting significantly before, but overlapping, the region of interest. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this should count as a bug? The description looked a bit vague, this might be better: