james hadfield

> I'm assuming "treat things independently" means something like this [...] Not quite. As per the [linked example](https://github.com/nextstrain/avian-flu/pull/106) I mean something like: ```sh augur merge --metadata A=A.tsv B=B.tsv --output-metadata merged.tsv...

Thanks Gytis ⭐️ An auspice implementation would be desirable as it would allow us to group subtrees interactively based on any non-continuous trait which is set on internal branches (i.e....

@frogsquire That would be great! Might be worth posting periodic screenshots or questions here for @evogytis and I ensure it's along the lines we were envisaging. Thanks :)

Thanks for the update! I've been looking at https://github.com/nextstrain/auspice/compare/master...frogsquire:1008-split-by-state (and checked it out locally to test). If you could submit a PR to auspice (it's no problem being in an...

> it seems to me we will still need some kind of an offset between each subtree and the next Yes, I think so. This could be achieved within the...

[Related commit message](https://github.com/nextstrain/nextstrain.org/commit/5f3e82e81c2229c62f3a965dcc809a8f61e0d679)

Nice! Auspice uses a bunch of class methods that are removed in React 18 (at least, [that's my understanding from these release notes](https://legacy.reactjs.org/blog/2018/03/29/react-v-16-3.html)) which is why I've been holding off...

Rebased onto master & moved this forward a little bit. `auspice build` and `auspice develop` work well for me locally. CI only failing due to bundlesize & linting. > Auspice...

> 2 – builds.yaml override with necessity of `default` This is essentially the solution I came to for `avian-flu`. It felt a little cumbersome sometimes, but overall I think works...

> **Expected behavior** > augur mask should fail loudly if the user provides a VCF with more than one chromosome with an error message explaining that only one chromosome is...