Releases: nextstrain/auspice
Releases · nextstrain/auspice
Auspice 2.61.2
- Bugfix: Fix errors where the tree wouldn't correctly update certain properties (#1907)
- Bugfix: Fix incorrect parsing of root-node dates of 0-99 CE (#1909)
- Bugfix: Fix an out-of-sync bug in the Entropy panel where the tooltip text would remain "Shannon entropy" and not update to "Num changes observed" (the value was correct). (#1906)
Auspice 2.61.1
- Bugfix: Restore shift-click behaviour for branches on the tree (#1901)
Auspice 2.61.0
- Error boundaries added for all panels (tree, map etc) so that in the case of uncaught errors we'll now show an error message rather than crashing Auspice. Hopefully these are never observed in production! (#1897)
- Bugfix: Auspice would crash in some situations when the entropy panel was scrolled back into view (bug introduced in v2.60.0). (#1898)
Internal / development changes
- Convert the tree component (and related tree-parsing functions) to TypeScript (#1864)
Auspice 2.60.0
- Performance improvement: We no longer attempt to animate actions on trees with over 4000 tips which results in more responsive interactions. (#1880)
- Performance improvement: We no longer recompute the entropy data (which can be expensive) when the entropy panel is toggled off or off-screen. (#1879)
- Bugfix: narrative slide changes which removed a filter would not work as expected in some cases (#1883)
Internal / development changes
Auspice 2.59.1
- Moved the "Focus on Selected" toggle next to the "Show confidence intervals" toggle.
(#1875)
Auspice 2.59.0
- Added an experimental "Focus on Selected" toggle in the sidebar.
When focusing on selected nodes, nodes that do not match the filter will occupy less vertical space on the tree.
Only applicable to rectangular and radial layouts.
(#1373)
Auspice 2.58.0
- Fix bug where drag-and-drop metadata columns were no longer included as tip labels (#1845)
- Fixed a bug where internal node names were sometimes omitted from the branch info modal (arrived at via shift-clicking on a branch).
They are now always displayed irrespective of the selected tip label.
(#1849) - Added URL params for measurements panel controls: m_collection, m_display, m_groupBy, m_overallMean, m_threshold, and mf_*.
See docs for more details. (#1848)
Auspice 2.57.0
- Remove hardcoded color scale for LBI (#1842)
- Any
node_attr
in the tree can be used as a tip label, as well as the special-cases of strain-name and "none".
Previously we only allowed valid colorings.
(#1668) - The specified tip label is surfaced more prominently within the the on-hover info boxes & on-click modals.
(#1668) - Temporal colour scales can now use YYYY-MM-DD values (previously only numeric dates were allowed).
Ambiguous (YYYY-MM-XX, YYYY-XX-XX) dates are allowed and the midpoint of the range will be used to choose the colour.
(#1832, #1836) - Parsing and error handling for URL query-encoded dates (
dmin
,dmax
,animate
) has been improved.
(#1832) - Div-only trees (i.e. no timetree) now hide the date / animation sections in the sidebar.
(#1834) - Improvements to how we use React within the measurements panel (should not result in any user-facing changes).
(#1838)
Auspice 2.56.1
- Fix bug where app crashed if measurements JSON did not define thresholds (#1802)
- Fix bug where measurements display did not honor the default
measurements_display
(#1802) - Only display download-JSON button if the dataset name can be parsed from pathname (#1804)
- Fix bug where measurements panel did not display means for measurements that had an "undefined" coloring (#1827)
- Measurement panel's x-axis min/max values are now limited by visible measurements (#1827)
Auspice 2.56.0
- We now use the reported confidence / entropy values to change the saturation of tips (circles) on the tree, which matches the behaviour seen for branches. If there is no (or very little) uncertainty in these nodes then the tips will appear the same as seen in previous versions of Auspice. (#1796)
- We no longer show the "second tree" sidebar dropdown when there are no available options. The possible options are defined by the charon/getAvailable API response and as such vary depending on the server in use. (#1795)