Skip to content

Releases: nextstrain/augur

16.0.3

28 Jul 13:51

Choose a tag to compare

16.0.3 (6 July 2022)

Bug Fixes

  • filter: Move register_arguments to the top of the module for better readability #995. (@victorlin)
  • filter: Fix a regression introduced in 16.0.2 that caused grouping with subsampled max sequences and force-included strains to fail in a data-specific way #1000. (@huddlej)

16.0.2

01 Jul 17:55

Choose a tag to compare

16.0.2 (30 June 2022)

Bug Fixes

  • The entropy panel was unavailable if mutations were not translated #881. This has been fixed by creating an additional annotations block in augur ancestral containing (nucleotide) genome annotations in the node-data #961 (@jameshadfield)
  • ancestral: WARNINGs to stdout have been updated to print to stderr #961 (@jameshadfield)
  • filter: Explicitly drop date/year/month columns from metadata during grouping. #967 (@victorlin)
    • This fixes a bug #871 where augur filter would crash with a cryptic ValueError if year and/or month is a custom column in the input metadata and also included in --group-by.
  • filter: Fix duplicates that may appear in metadata when using --include/--include-where with subsampling #986 (@victorlin)

6.3.0

13 Feb 23:40

Choose a tag to compare

Features

  • Augur refine, ancestral and traits now use the
    upgraded TreeTime v0.7
    This should have a number of under-the-hood improvements.
    See PR 431
  • ancestral: New options to either --keep-ambiguous or --infer-ambiguous. If using
    --infer-ambiguous the previous behavior will be maintained in which tips with N will have
    their nucleotide state inferred. If using --keep-ambiguous, these tips will be left as N.
    With this upgrade, we are still defaulting to --infer-ambiguous, however, we plan to swap
    default to --keep-ambiguous in the future. If this distintion matters to you, we would suggest
    that you explicitly record --keep-ambiguous / --infer-ambiguous in your build process.
    Also part of PR 431
  • traits: Allow input of --weights which references a .tsv file in the following format:
    division	Hubei	10.0
    division	Jiangxi	1.0
    division	Chongqing	1.0
    
    where these weights represent equilibrium frequencies in the CTMC transition model. We imagine the
    primary use of user-specified weights to correct for strong sampling biases in available data.
    See PR 443

Bug fixes

  • Improvements to make shell scripts run more easily on Windows.
    See PR 437

6.2.0

13 Feb 23:40

Choose a tag to compare

Features

  • refine: Include --divergence-units option to distinguish between mutations
    and mutations-per-site. Keep mutations-per-site as default behavior.
    See PR 435

Bug fixes

  • utils: Support v2 auspice JSONs in json_to_tree utility function.
    See PR 432

6.1.1 (17 December 2019)

Bug fixes

  • frequencies: Fix bug in string matching for weighted frequencies introduced in
    v6.1.0. See PR 426.

6.1.1

17 Dec 19:22

Choose a tag to compare

6.1.1 (17 December 2019)

Bug fixes

  • frequencies: Fix bug in string matching for weighted frequencies introduced in
    v6.1.0. See PR 426.

6.1.0

17 Dec 19:21

Choose a tag to compare

6.1.0 (13 December 2019)

Features

  • export: Include --description option to pass in a Markdown file with dataset
    description. This is displays in Auspice in the footer. For rationale,
    see Auspice issue 707 and
    for Augur changes see PR 423.

Bug fixes

  • frequencies: Fix weighted frequencies when weight keys are unrepresented.
    See PR 420.

6.0.0

11 Dec 00:36

Choose a tag to compare

6.0.0 (10 December 2019)

Overview

Version 6 is a major release of augur affecting many augur commands. The format
of the exported JSON (v2) has changed and now merges the previously separate
files containing tree and meta information. To maintain backward compatibility,
the export command was split into export v1 (old) and export v2 (new).
Detailed release notes are provided in the augur documentation on
read-the-docs
.
For a migration guide, consult
migrating-v5-v6.

Major features / changes

  • export: Swap from a separate _tree.json and _meta.json to a single
    "unified" dataset.json output file
  • export: Include additional command line options to alleviate need for Auspice
    config
  • export: Include option for reference sequence output
  • export: Move to GFF-style annotations
  • export: Validate exported JSONs against schema
  • ancestral: Allow output of FASTA and JSON files
  • import: Include import beast command to import labeled BEAST MCC tree
  • parse: Include --prettify-fields option to cleanup metadata fields
  • Documentation improvements

Minor features / changes

  • colors.tsv: Allow whitespace, but insist on tab delimiting
  • lat_longs.tsv: Allow whitespace, but insist on tab delimiting
  • Remove code for old "non-modular" augur, old "non-modular" builds and Python
    tests
  • Improve test builds
  • filter: More interpretable output of how many sequences have been filtered
  • filter: Additional flag --subsample-seed to seed the random number generator
    and thereby make subsampling reproducible
  • sequence-traits: Numerical output as originally intended, but required an
    Auspice bugfix
  • traits: Explanation of what is considered missing data & how it is interpreted
  • traits: GTR models are exported in the output JSON for better accountability &
    reproducibility

5.4.1

11 Dec 00:37

Choose a tag to compare

5.4.1 (12 November 2019)

Bug fixes

  • export v1: Include --minify-json option that was mistakenly not included in PR 398.
    See PR 409

5.4.0

11 Dec 00:39

Choose a tag to compare

5.4.0 (7 November 2019)

Features

  • frequencies: Include --minimal-clade-size-to-estimate command line option.
    See PR 383
  • lbi: Include --no-normalization command line option.
    See PR 380

Compatibility fixes

  • export: Include v1 subcommand to allow forwards compatibiliy with Augur v6 builds.
    See PR 398

Bug fixes

  • export: Include warning if using a mismatched v6 translate file.
    See PR 392
  • frequencies: Fix determination of interval for clipping of non-informative pivots

5.3.0

11 Dec 00:40

Choose a tag to compare

5.3.0 (9 September 2019)

Features

  • export: Improve printing of error messages with missing or conflicting author
    data. See issue 274
  • filter: Improve printing of dropped strains to include reasons why strains were
    dropped. See PR 367
  • refine: Add support for command line flag --keep-polytomies to not resolve
    polytomies when producing a time tree.
    See PR 345

Bug fixes

  • Catch and throw error when there are duplicate strain names.
    See PR 356
  • Fix missing annotation of "parent" attribute for the root node
  • Run shell commands with more robust error checking.
    See PR 350
  • Better handling of rerooting options for trees without temporal information.
    See issue 348

Data

  • Small fixes in geographic coordinate file