QIIME 2 2020.6 is now available!

The QIIME 2 2020.6 release is now available! Thanks to everyone involved for their hard work!

As a reminder, our next planned QIIME 2 release is scheduled for August 2020 (QIIME 2 2020.8), but please stay tuned for updates.

Check out the QIIME 2 2020.6 docs for details on installing the latest QIIME 2 release, as well as tutorials and other resources. Get in touch on the QIIME 2 Forum if you run into any issues!

Virtual machine builds will be available sometime within the next week - watch this topic thread for an update!

:exclamation: BREAKING CHANGES

  • q2-diversity
    • core_metrics_phylogenetic: The n_jobs parameter has been renamed n_jobs_or_threads to accommodate a speedy new implementation of unifrac now being used
    • core_metrics & core_metrics_phylogenetic: The phrase observed_features is replacing observed_otus, as “observed features” better describes the different ways in which users work with non-taxonomic features in QIIME 2 (an OTU is a feature, but a feature isn’t necessarily an OTU)
    • core_metrics & core_metrics_phylogenetic: n_jobs and n_jobs_or_threads no longer accept zero or negative integers as arguments. Users should pass auto to those parameters to use all available physical cores

Highlights of the release:

  • QIIME 2 Framework
    • @thermokarst, @andrewsanchez, and @David-Rod worked up further developing the Usage API, which will allow plugin developers to showcase usage examples of their plugin actions, in an interface agnostic way! :star2:
      This included:
      • Enabling source tracking of initialized data
      • Adding a method to initialize data collections
    • @thermokarst improved some of the developer documentation in the test harness. :champagne:
    • @Oddant1 increased level of validation of filenames to prevent creation of artifacts with incorrectly named data files.
  • docs
    • @ChrisKeefe showed us how to peek at an Artifact in the Moving Pictures Tutorial :face_with_raised_eyebrow:
    • @ChrisKeefe added a section to the Importing Tutorial for multiplexed fastq files with barcodes in sequences. :icecream:
    • @ChrisKeefe clarified the behaviors of qiime tools view and q2view :fork_and_knife:
    • @thermokarst added Native installation instructions for Windows users leveraging the Windows Subsystem for Linux :robot:
    • @thermokarst added some rough guidelines for selecting an installation method that best fits your computational needs :rose:
    • @thermokarst added examples of q2-demux's subsampling and sample filtering tools to the Atacama tutorial :goal_net:
    • @Oddant1 Changed the wording of the suggestion to use the vega editor for the q2-longitudinal volatility plot to reflect the current implementation
    • Several small typos were fixed, including one by @hmaru (GH)! :keyboard:
    • @thermokarst overhauled the User Docs hosting infrastructure.
  • data-resources
    • @Nicholas_Bokulich also added SILVA 138 release sequence and taxonomy files formatted for use with QIIME 2. Data were prepared and formatted using RESCRIPt (co-developed with @SoilRotifer)! See that tutorial for more details on how these files were generated, and a pipeline to reproduce this process! :robot:
    • @Nicholas_Bokulich added new pre-trained classifiers for Greengenes 13_8 release and SILVA 138 release (the latest versions of both), trained using scikit-learn 0.23.1. These classifiers were built and tested in a new way, using RESCRIPt! :construction_worker_man:
  • q2cli
    • @thermokarst fixed up an error message: a tiny typo can cause a surprising amount of confusion! :building_construction:
    • @andrewsanchez merged in the first iteration of the Usage API CLI driver :racing_car:. This should be considered as sort of “pre-release,” for developers until the Usage API and usage examples are a bit more mature. Stay tuned for much more action in this realm in future releases!
  • QIIME 2 Studio
    • @andrewsanchez fixed a bug that cropped up when trying to import data! :bug:
  • q2-feature-classifier
    • @cherman2 (GH) helped remind us why we don’t have multithreading options for the blast classifier - thanks for the research and code comments! :orange_heart:
    • @adamovanja (GH) added a trim-right option to the extract-reads action, allowing simulated reads to be trimmed at the 3’ ends. This is useful for, e.g., emulating trimming options of reads coming from q2-dada2, to generate optimally trimmed reference sequences for classifier training as described here. Thank you adamovanja for fixing this issue, and @Sean_McKenzie for bringing it to our attention! :green_heart:
    • @Nicholas_Bokulich improved the docs for extract-reads :eyeglasses:!
    • @Nicholas_Bokulich trained new feature-classifiers using scikit-learn 0.23.1 :nerd_face:
  • q2-phylogeny
    • @ebolyen added a new method, robinson-foulds, for comparing two phylogenetic trees! :christmas_tree:
  • q2-composition
    • @thermokarst fixed a bug in ancom! The visualization had a propensity for (accidentally) attempting to divide by zero - never a good plan! :bug:
    • @Oddant1 Removed the link to the vega editor on the ancom plot pending a rework of the plot for vega 5
  • q2-cutadapt
    • @Oddant1 and @thermokarst added support for demultiplexing mixed-orientation single-indexed reads. :man_cartwheeling:
  • q2-feature-table
    • @David-Rod added some usage examples to the merge method! :potable_water:
    • @jwdebelius added a new method for re-naming features or samples in a table :haircut_woman:
    • @thermokarst fixed a bug that caused summarize visualizations to sometimes display distorted column widths :straight_ruler:
    • @Oddant1 Removed the link to the vega editor on the summarize plot pending a rework of the plot for vega 5
  • q2-alignment
    • @gregcaporaso added a new action, mafft-add, which allows for the addition of unaligned sequences to an existing alignment :heavy_plus_sign:
  • q2-quality-filter
    • @thermokarst merged q-score and q-score-joined into the same method (q-score), and deprecated the q-score-joined method. This method will be removed in the fall 2020 release of QIIME 2. :leaves:
  • q2-quality-control
    • @Nicholas_Bokulich (aka Doc Bok) added a new filter_reads method that supports filtering SampleData[SequencesWithQuality] and SampleData[PairedEndSequencesWithQuality] artifacts (a.k.a. FASTQ sequence data) by alignment to a reference database. How might you use this? To filter human reads and other non-target (or junk) sequences prior to denoising or dereplication.
    • @gwarmstrong transitioned alpha_phylogenetic and alpha_rarefaction to use Stacked Faith, a speed- and memory-optimized implementation previous available in alpha_phylogenetic_alt. alpha_phylogenetic_alt will be removed in the next release.:racehorse:
  • q2-diversity
    • @patrickimran (GH) added a new jensenshannon beta diversity metric! :pie:
    • @ChrisKeefe wired up q2-diversity-lib to perform alpha- and beta-diversity calculations for core-metrics and core-metrics-phylogenetic. See Breaking Changes above for related API changes.
    • @Oddant1 fixed a bug allowing 0 variance numerical columns to slip past the filter in bioenv causing errors.
  • q2-diversity-lib
    • @ChrisKeefe - this :new: plugin calculates alpha- and beta-diversity measures, expands the number of available semantic types where appropriate, and provides measure-specific citation information.
  • q2-types
    • @thermokarst added new transformers for working with per-sample-sequences in fun and interesting ways (dev alert!) :chart:
    • @gregcaporaso added more aligned sequence transformers. :robot:
  • q2-vsearch
    • @thermokarst fixed up a performance bug in the cluster-features-closed-reference method, resulting in potentially significant speedups for some use-cases. :racing_car:
    • @angrybee (gh) added an awesome new visualizer fastq_stats for distilling single-end or paired-end sequences into FASTQ file statistics using vsearch!:crossed_swords:
    • @Oddant1 added the ability for all vsearch methods to accept sequences shorter than 32nt
    • @Oddant1 set --fasta_width 0 on invoked vsearch commands to prevent fasta records from being split across multiple lines
  • q2-longitudinal
    • @Oddant1 removed the link to the vega editor from the volatility plot pending a rework of the plot for vega 5
  • q2-demux
    • @Oddant1 and @thermokarst reworked summarize visualization to better inform the user of missing reads
  • q2-dada2
    • @benjjneb added pseudo-pooling to all DADA2 workflows, allowing users to increase sensitivity to rare variants in samples, particularly singletons, as long as they were observed in other samples independently.
    • @ebolyen squashed a bug where feature-tables containing only one feature were being mis-diagnosed as empty. :honeybee:
  • q2-sample-classifier
  • q2-emperor
    • @yoshiki and @antgonza updated to the latest release of Emperor 1.0.1 :penguin: :partying_face: .
    • @yoshiki fixed an issue where biplot arrows would incorrectly show while visualizing a parallel plot.
    • @fedarko fixed an issue where continuous and divergent colormaps would be partially used in categorical data.
    • @fedarko fixed a bug with sorting numeric and non-numeric values.
    • @yoshiki fixed an issue where axes settings wouldn’t load correctly from the Python API.
    • @fedarko and @yoshiki updated various dependencies.
    • Added the ability to select a group of samples and save the sample names to the users’ clipboard. To do this, users need to hold shift and select the samples they are interested in:

Happy QIIMEing! :sunflower:


FYI: the link to the Naive Bayes classifier trained on Silva 138 99% OTUs full-length sequences gives a 404 error.

Nevertheless, thanks for the new 2020.6 version!


Thanks @Mechah! I think the URL is fixed now - please let us know if you run into any more issues. Thanks!


Yahoo! VMs are hot and fresh out of the oven:



1 Like

The alpha rarefaction graph still utilising metric “observed-otus”, is that normal?

Hi @Yin_Hui_Cheok!

Yes! Please see the changelog, above:

We started replacing the phrase “observed OTUs” with “observed features”, however the work isn’t yet complete.

Dear QIIME2 developers,

Thank you so much for all of your great work!

I just have a simple question for this version please: does this version support filtering features based on their relative frequencies?

Many thanks!

Congratulations QIIME2 developers

1 Like

Hi @fgara! Not directly, but, you can do a little bit of manual arithmetic to figure out the threshold, if you wish to filter by relative frequency. I believe there are a few examples floating around here on the forum.