Tags: kkoziara/htslib
Tags
Noteworthy changes in release 1.5 (21st June 2017) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Added a new logging API: hts_log(), along with hts_log_error(), hts_log_warn() etc. convenience macros. Thanks go to Anders Kaplan for the implementation. (samtools#499, samtools#543, samtools#551) * Added a new file I/O option "block_size" (HTS_OPT_BLOCK_SIZE) to alter the hFILE buffer size. * Fixed various bugs, including compilation issues samtools/bcftools#610, samtools/bcftools#611 and robustness to corrupted data samtools#537, samtools#538, samtools#541, samtools#546, samtools#548, samtools#549, samtools#554.
Noteworthy changes in release 1.4.1 (8th May 2017) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This is primarily a security bug fix update. * Fixed SECURITY issue with buffer overruns with malicious data. (samtools#514). * S3 support for non Amazon AWS endpoints. (samtools#506) * Support for variant breakpoints in bcftools. (samtools#516) * Improved handling of BCF NaNs. (samtools#485) * Compilation / portability improvements. (samtools#255, samtools#423, samtools#498, samtools#488) * Miscellaneous bug fixes (samtools#482, samtools#521, samtools#522, samtools#523, samtools#524). * Sanitise headers (samtools#509)
Relase 1.4 (13 March 2017)
* Incompatible changes: several functions and data types have been changed
in this release, and the shared library soversion has been bumped to 2.
- bam_pileup1_t has an additional field (which holds user data)
- bam1_core_t has been modified to allow for >64K CIGAR operations
and (along with bam1_t) so that CIGAR entries are aligned in memory
- hopen() has vararg arguments for setting URL scheme-dependent options
- the various tbx_conf_* presets are now const
- auxiliary fields in bam1_t are now always stored in little-endian byte
order (previously this depended on if you read a bam, sam or cram file)
- index metadata (accessible via hts_idx_get_meta()) is now always
stored in little-endian byte order (previously this depended on if
the index was in tbi or csi format)
- bam_aux2i() now returns an int64_t value
- fai_load() will no longer save local copies of remote fasta indexes
- hts_idx_get_meta() now takes a uint32_t * for l_meta (was int32_t *)
* HTSlib now links against libbz2 and liblzma by default. To remove these
dependencies, run configure with options --disable-bz2 and --disable-lzma,
but note that this may make some CRAM files produced elsewhere unreadable.
* Added a thread pool interface and replaced the bgzf multi-threading
code to use this pool. BAM and CRAM decoding is now multi-threaded
too, using the pool to automatically balance the number of threads
between decode, encode and any data processing jobs.
* New errmod_cal(), probaln_glocal(), sam_cap_mapq(), and sam_prob_realn()
functions, previously internal to SAMtools, have been added to HTSlib.
* Files can now be accessed via Google Cloud Storage using gs: URLs, when
HTSlib is configured to use libcurl for network file access rather than
the included basic knetfile networking.
* S3 file access now also supports the "host_base" setting in the
$HOME/.s3cfg configuration file.
* Data URLs ("data:,text") now follow the standard RFC 2397 format and may
be base64-encoded (when written as "data:;base64,text") or may include
percent-encoded characters. HTSlib's previous over-simplified "data:text"
format is no longer supported -- you will need to add an initial comma.
* When plugins are enabled, S3 support is now provided by a separate
hfile_s3 plugin rather than by hfile_libcurl itself as previously.
When --enable-libcurl is used, by default both GCS and S3 support
and plugins will also be built; they can be individually disabled
via --disable-gcs and --disable-s3.
* The iRODS file access plugin has been moved to a separate repository.
Configure no longer has a --with-irods option; instead build the plugin
found at <https://github.com/samtools/htslib-plugins>.
* APIs to portably read and write (possibly unaligned) data in little-endian
byte order have been added.
* New functions bam_auxB_len(), bam_auxB2i() and bam_auxB2f() have been
added to make accessing array-type auxiliary data easier. bam_aux2i()
can now return the full range of values that can be stored in an integer
tag (including unsigned 32 bit tags). bam_aux2f() will return the value
of integer tags (as a double) as well as floating-point ones. All of
the bam_aux2 and bam_auxB2 functions will set errno if the requested
conversion is not valid.
* New functions fai_load3() and fai_build3() allow fasta indexes to be
stored in a different location to the indexed fasta file.
* New functions bgzf_index_dump_hfile() and bgzf_index_load_hfile()
allow bgzf index files (.gzi) to be written to / read from an existing
hFILE handle.
* hts_idx_push() will report when trying to add a range to an index that
is beyond the limits that the given index can handle. This means trying
to index chromosomes longer than 2^29 bases with a .bai or .tbi index
will report an error instead of apparantly working but creating an invalid
index entry.
* VCF formatting is now approximately 4x faster. (Whether this is
noticable depends on what was creating the VCF.)
* CRAM lossy_names mode now works with TLEN of 0 or TLEN within +/- 1
of the computed value. Note in these situations TLEN will be
generated / fixed during CRAM decode.
* CRAM now supports bzip2 and lzma codecs. Within htslib these are
disabled by default, but can be enabled by specifying "use_bzip2" or
"use_lzma" in an hts_opt_add() call or via the mode string of the
hts_open_format() function.
HTSlib patch release 1.3.2: bin bug fix, RTLD_GLOBAL plugins * Corrected bin calculation when converting directly from CRAM to BAM. Previously a small fraction of converted reads would fail Picard's validation with "bin field of BAM record does not equal value computed" (SAMtools issue samtools#574). * Plugins can now signal to HTSlib which of RTLD_LOCAL and RTLD_GLOBAL they wish to be opened with -- previously they were always RTLD_LOCAL.
HTSlib release 1.3.1: bug fix release, notably error checking * Improved error checking and reporting, especially of I/O errors when writing output files (samtools#17, samtools#315, PR samtools#271, PR samtools#317). * Build fixes for 32-bit systems; be sure to run configure to enable large file support and access to 2GiB+ files. * Numerous VCF parsing fixes (samtools#321, samtools#322, samtools#323, samtools#324, samtools#325; PR samtools#370). Particular thanks to Kostya Kortchinsky of the Google Security Team for testing and numerous input parsing bug reports. * HTSlib now prints an informational message when initially creating a CRAM reference cache in the default location under your $HOME directory. (No message is printed if you are using $REF_CACHE to specify a location.) * Avoided rare race condition when caching downloaded CRAM reference sequence files, by using distinctive names for temporary files (in addition to O_EXCL, which has always been used). Occasional corruption would previously occur when multiple tools were simultaneously caching the same reference sequences on an NFS filesystem that did not support O_EXCL (PR samtools#320). * Prevented race condition in file access plugin loading (PR samtools#341). * Fixed mpileup memory leak, so no more "[bam_plp_destroy] memory leak [...] Continue anyway" warning messages (samtools#299). * Various minor CRAM fixes. * Fixed documentation problems samtools#348 and samtools#358.
HTSlib release 1.3, plugins, libcurl, CRAM v3.0, bug fixes * Files can now be accessed via HTTPS and Amazon S3 in addition to HTTP and FTP, when HTSlib is configured to use libcurl for network file access rather than the included basic knetfile networking. * HTSlib can be built to use remote access hFILE backends (such as iRODS and libcurl) via a plugin mechanism. This allows other backends to be easily added and facilitates building tools that use HTSlib, as they don't need to be linked with the backends' various required libraries. * fai_build() and samtools faidx now accept initial whitespace in ">" headers (e.g., "> chr1 description" is taken to refer to "chr1"). * tabix --only-header works again (was broken in 1.2.x; samtools#249). * HTSlib's configure script and Makefile now fully support the standard convention of allowing CC/CPPFLAGS/CFLAGS/LDFLAGS/LIBS to be overridden as needed. Previously the Makefile listened to $(LDLIBS) instead; if you were overriding that, you should now override LIBS rather than LDLIBS. * Fixed bugs samtools#168, samtools#172, samtools#176, samtools#197, samtools#206, samtools#225, samtools#245, samtools#265, samtools#295, and samtools#296.
PreviousNext