Skip to content

Releases: bbuchfink/diamond

DIAMOND v2.0.5

19 Nov 16:54
f6f72eb
Compare
Choose a tag to compare
  • Fixed an issue that could cause high memory use in frameshift alignment mode.

DIAMOND v2.0.4

30 Aug 12:42
Compare
Choose a tag to compare
  • Fixed a bug that could cause the --max-target-seqs/-k, --ext-chunk-size and --file-buffer-size options not to function correctly on macOS.

DIAMOND v2.0.3

29 Aug 09:39
Compare
Choose a tag to compare
  • Added a new sensitivity mode that is between the default mode and the sensitive mode in sensitivity (option --mid-sensitive).
  • Added counters for total number of reference blocks, shapes and index chunks to the status messages.
  • Fixed a bug (persisting since v2.0.2) that could cause secondary HSPs within one target not to be reported if the --max-hsps option was used with a non-default setting.
  • Fixed a bug that could cause an invalid error message with regard to the database format in certain cases.
  • The --no-self-hits option is no longer supported in blastx mode.
  • Changed the semantics of the --no-self-hits option to check for equality of both sequence and sequence id, independent of the computed alignment.
  • The selection of the top hit when using --top will respect the identity, coverage and no-self-hits filter settings (does not apply when frameshift alignment is enabled).
  • The inclusion criterion for --top is applied to the bit score instead of the raw score and is no longer affected by integer rounding (does not apply when frameshift alignment is enabled).
  • Improved the accuracy of the ranking heuristic.
  • Added the options --ext-chunk-size and --no-ranking to control the ranking heuristic.

DIAMOND v2.0.2

05 Aug 17:47
Compare
Choose a tag to compare
  • Fixed a bug (persisting since v2.0.0) that could cause incomplete results in blastx mode.
  • Reduced the use of temporary disk space.
  • Fixed an issue that could cause long runtimes when using the --taxon-list option.

DIAMOND v2.0.1

01 Aug 14:25
Compare
Choose a tag to compare
  • Added feature for using the tool in a distributed computing environment. (See here for details: http://www.diamondsearch.org/index.php?pages/distributed_computing/)
  • Fixed an issue that could cause increased memory usage and runtimes in certain cases.
  • Fixed a bug that could cause a crash when using --comp-based-stats 0.
  • Fixed a bug that could cause a crash for small input files in certain cases.
  • Fixed a bug that could cause filtering hits for identity or range cover not to function correctly when using the tabular format without traceback being enabled.
  • Added warning messages to recommend block size parameters based on system RAM.

DIAMOND v2.0.0

24 Jul 12:25
Compare
Choose a tag to compare
  • Added the sensitivity modes --very-sensitive and --ultra-sensitive. Both modes are designed for finding distant hits of <40% identity with a sensitivity similar to BLAST, with the ultra-sensitive mode being the slightly more sensitive mode.
  • The --block-size/-b parameter is set to 0.4 and the --index-chunks/-c parameter is set to 1 by default
    in the new sensitivity modes.
  • Improved performance.
  • Added the option --ext with possible values banded-fast and banded-slow to adjust band setup for Smith
    Waterman extensions (new default is banded-fast for the default and sensitive mode, and banded-slow otherwise).
  • Added automatic disabling of alignment traceback if not required by the user-defined output fields in tabular
    output format.
  • Changed the default value of the --max-hsps parameter (the maximum number of HSPs per target sequence to report for each query) to 1.
  • Changed the default value of the --freq-sd parameter from 10 to 20 for the sensitive mode.
  • Fixed a compiler error on FreeBSD.

DIAMOND v0.9.36

30 Jun 12:20
Compare
Choose a tag to compare
  • Fixed a bug that could cause makedb to produce invalid database files when using taxonomy features.
  • Fixed a bug that could cause a crash when running in query-indexed mode.

WARNING: This version contains a serious bug that can cause incomplete results in blastx mode. Using it is not recommended.

DIAMOND v0.9.35

20 Jun 11:53
Compare
Choose a tag to compare
  • Fixed a bug in diamond view that would cause high memory usage and erroneous output.
  • Reduced the use of temporary disk space.
  • Fixed a database compatibility issue with big endian architectures.
  • Fixed a bug that would cause a crash for query sequences shorter than 5 letters in blastx mode.
  • Fixed a bug that would cause a crash when using a FASTA file as database parameter in blastx mode.
  • Added support for the following new ranks in the NCBI taxonomy: biotype, clade, forma specialis, genotype, isolate, morph, pathogroup, serogroup, serotype, strain, subvariety.

WARNING: This version contains a serious bug that can cause incomplete results in blastx mode. Using it is not recommended.

DIAMOND v0.9.34

07 Jun 15:41
Compare
Choose a tag to compare
  • Fixed a compiler error for native builds.
  • Fixed a compiler error for GCC 4.8.
  • Fixed a compiler error when support for SSSE3 was enabled without support for SSE4.1.
  • Implemented asynchronous loading of seed hits.

WARNING: This version contains a serious bug that can cause incomplete results in blastx mode. Using it is not recommended.

DIAMOND v0.9.33

01 Jun 13:52
Compare
Choose a tag to compare
  • Improved performance and sensitivity.
  • Increased use of temporary disk space.
  • Implemented support for the AVX2 instruction set.
  • Fixed a bug on big-endian architectures.
  • Fixed bugs for compilers with unsigned char.
  • Fixed compiler errors for generic builds.
  • Added compatibility of database files between little and big endian architectures.
  • Fixed various issues related to Illegal instruction errors on macOS.
  • Added option --file-buffer-size to set the size of the I/O buffers and set the default value to 64 MB.

Edit: fixed portability issue in the attached Linux binary.

WARNING: This version contains a serious bug that can cause incomplete results in blastx mode. Using it is not recommended.