Releases: RasmussenLab/vamb
Releases Β· RasmussenLab/vamb
v4.1.3
v4.1.2
v4.1.2
- Fix a bug in src/create_fasta.py
- Bugfix: Make seeding the RNG work from command line
- Bump compatible Cython version
v4.1.1
v4.1.1
- Create tmp directory in parsebam if needed for pycoverm (issue # 167)
v4.1.0
v4.1.0
- Allow setting the RNG seed from command line
- Fix typo in output AAE_Z cluster names. They are now called e.g. "aae_z_1"
instead of "aae_z1" - Clean up the directory structure of Avamb workflow.
- Fix the CheckM2 dependencies to allow CheckM2 to be installed
- Allow the Avamb workflow to be run on Slurm clusters
- Fix issue #161: Mismatched refhash when spaces in FASTA headers
v4.0.1
v4.0.0
Vamb 4.0.0
Version 4 is a thorough rewrite of major parts of Vamb that has taken more than a year.
Vamb now ships with with an upgraded dual variational autoencoder (VAE) and
adversatial autoencoder (AAE) model, usable in a CheckM based workflow.
The code quality and test suite has gotten significant upgrades, making Vamb
more stable and robust to bugs.
Vamb version is slightly faster and produces better bins than v3.
The user interface has gotten limited changes.
Breaking changes
- The official API of Vamb is now defined only in terms of its command-line
interface. This means that from now on, Vamb can freely change and modify its
internal functions, even in minor releases or patch releases.
If you are using Vamb as a Python package, it means you should precisely
specify the full version of Vamb used in order to ensure reproducibility. - Benchmark procedure has been changed, so benchmark results are incompatible
with results from v3. Benchmarking is now considered an implementation detail,
and is not stable across releases. - Vamb no longer outputs TNF, sequence names and sequence lengths as .npz files.
Instead, it produces acomposition.npz
that contains all this information
and more.
As a consequence command-line options--tnfs
,--names
and--lengths
have been removed, and replaced with the single--composition
option. - The output .npz array
rpkm.npz
has been changed in a backwards incompatible
way. From version 4, the content of the output .npz files are considered an
implementation detail. - The depths input option
--jgi
has been removed. To use depths computed by
an external program, construct an instance of theAbundance
class from your
depths and save it using its.save
method to anrpkm.npz
file.
(though read the Notable changes section below).
New features
- Vamb now included an optional AAE model along the VAE model.
Users may run the VAE model, where it behaves similarly to v3, or run the mixed
VAE/AAE model, in which both models will be run on the same dataset. - The Snakemake workflow has been rehauled, and how defaults to using
the VAE/AAE combined model, using CheckM to dereplicate. - Vamb is now more easily installed via pip:
pip install vamb
. We have fixed
a bunch of issues that caused installation problems. - By default, Vamb gzip compresses FASTA files written using the
--minfasta
flag.
Notable other changes
- Using the combined VAE-AAE workflow, the user can get significantly better bins.
- Vamb now uses
CoverM
internally to calculate abundances. This means it is
significantly faster and more accurate than before.
Thus, we no longer recommend users computing depths with MetaBAT2's JGI tool. - Lots of bugfixes may have changed Vamb's behaviour in a backwards incompatible
way for certain edge cases. For example, FASTA identifiers are now required to
match the name specification in the SAM format to ensure the identifiers are
the same in FASTA and BAM files.
v3.0.9
v3.0.9
- Update pytorch to 1.13
- Fix bug when GPU clustering where a tensor was on GPU instead of CPU
v3.0.8
Update version in workflow and add mincontigs flag to cmd_benchmark.py
v3.0.7
Version 3.0.7
Update compability to allow installation on Conda
v3.0.6
Fix bug when creating FASTA files.