1
1
# Changelog
2
2
3
- ## Unreleased - v4.0.0-DEV
4
- Version 4 is a thorough rewrite of major parts of Vamb.
3
+ ## v4.0.1
4
+ * Fix Random.choice for Tensor on Python 3.11. See issue #148
5
+
6
+ ## v4.0.0
7
+ Version 4 is a thorough rewrite of major parts of Vamb that has taken more than a year.
8
+ Vamb now ships with with an upgraded dual variational autoencoder (VAE) and
9
+ adversatial autoencoder (AAE) model, usable in a CheckM based workflow.
5
10
The code quality and test suite has gotten significant upgrades, making Vamb
6
11
more stable and robust to bugs.
7
- Vamb version is slightly faster and produces slightly better bins than v3.
8
- The user interface has only gotten slight changes.
12
+ Vamb version is slightly faster and produces better bins than v3.
13
+ The user interface has gotten limited changes.
9
14
10
15
### Breaking changes
11
16
* The official API of Vamb is now defined only in terms of its command-line
@@ -14,11 +19,8 @@ The user interface has only gotten slight changes.
14
19
If you are using Vamb as a Python package, it means you should precisely
15
20
specify the full version of Vamb used in order to ensure reproducibility.
16
21
* Benchmark procedure has been changed, so benchmark results are incompatible
17
- with results from v3.
18
- In v3, a complete bin was defined as the total set of covered basepairs in any
19
- contig from the input assembly. In v4, it's defined as the genome of origin,
20
- from where contigs are sampled.
21
- This new procedure is more fair, more intuitive and easier to compute.
22
+ with results from v3. Benchmarking is now considered an implementation detail,
23
+ and is not stable across releases.
22
24
* Vamb no longer outputs TNF, sequence names and sequence lengths as .npz files.
23
25
Instead, it produces a ` composition.npz ` that contains all this information
24
26
and more.
@@ -33,15 +35,18 @@ The user interface has only gotten slight changes.
33
35
(though read the Notable changes section below).
34
36
35
37
### New features
38
+ * Vamb now included an optional AAE model along the VAE model.
39
+ Users may run the VAE model, where it behaves similarly to v3, or run the mixed
40
+ VAE/AAE model, in which both models will be run on the same dataset.
41
+ * The Snakemake workflow has been rehauled, and how defaults to using
42
+ the VAE/AAE combined model, using CheckM to dereplicate.
36
43
* Vamb is now more easily installed via pip: ` pip install vamb ` . We have fixed
37
44
a bunch of issues that caused installation problems.
38
- * Added new flag: ` --noencode ` . With this flag, Vamb stops after producing the
39
- composition and depth outputs, and does not encode nor cluster.
40
- This can be used to produce the input data of Vamb to other clustering models.
41
45
* By default, Vamb gzip compresses FASTA files written using the ` --minfasta `
42
46
flag.
43
47
44
- ### Notable changes
48
+ ### Notable other changes
49
+ * Using the combined VAE-AAE workflow, the user can get significantly better bins.
45
50
* Vamb now uses ` CoverM ` internally to calculate abundances. This means it is
46
51
significantly faster and more accurate than before.
47
52
Thus, we no longer recommend users computing depths with MetaBAT2's JGI tool.
0 commit comments