-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update usage of "accession" as the ID column #161
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for following up on this! Really nice to see the simplification!
The only request I have is to update the min_augur_version
in the main Snakefile.
7f38daa
to
4d8c515
Compare
2b57ce5
to
67c3312
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The output of the pathogen-repo-CI looks as expected.
I've only left some minor non-blocking comments.
Thanks for the review @joverlee521! I'll take some of your suggestions. I also just checked, and this PR suffers from the same issue of missing the |
Ah, thanks @victorlin for pointing out the I think there's additional bugs in |
Ah, also just realized that the construct-recency-from-submission-date script also uses |
To test that the new Augur changes address the issue here, I created a Docker image with the unreleased Augur changes, updated CI here to use that, and uploaded the CI result's Auspice JSONs to a personal repo to be viewed through nextstrain.org/community. Here are the results:
(2) is missing tip attributes as expected. (3) is the same as (1) but missing Submission Recency, due to @joverlee521's note in the previous comment. |
c10fde8
to
5b1b4ae
Compare
Ok, the force-push above fixed the Submission Recency problem. These are the new results:
(2) is what we should expect once the Augur changes are released and 0b9059e is fixed up. I think it looks comparable to master/85d33b0/docker. |
5b1b4ae
to
da64839
Compare
Snakefile
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Preview links for da64839's PR-triggered CI run results:
Both of these should be comparable to master/85d33b0/docker.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working through the hidden bugs in Augur to get this working!
The phylogenetic build changes and the CI output LGTM.
The only requested change is the one error that I flagged.
Add a note where it should be kept.
Retrieving config that is required should be done using the bracket syntax. Retrieving config with .get should always be done with a default value.
There was useful information on why "accession" is used over "strain" in the docstring of update_example_data. Update that rule to use the strain_id_field config, and move the context to every config file that sets strain_id_field as "accession". Don't set defaults when retrieving strain_id_field so "accession" is only set on the config level.
New options in Augur 22.2.0 allow usage of this column as the ID column across all subcommands that read metadata. For this workflow in particular, the metadata file can now be used as-is. This removes the need for a modified copy of the metadata. It also allows specifying an original metadata column "strain" as the display strain field, rather than a column "strain_original" generated during the Snakemake workflow.
da64839
to
927ad6c
Compare
Description of proposed changes
Improvements and clarifications around the choice of "accession" as the ID column in this repo. See commit messages.
Related issue(s)
Checklist