-
Notifications
You must be signed in to change notification settings - Fork 11
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
Latest alignment to Pathogen repo guide and add frequency panel #88
Merged
Merged
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
7d57914
Ingest: Re-align to pathogen-repo-guide
j23414 a494822
Ingest: Infer URL column from genbank accession for node call out
j23414 57a8457
Use authors and full_authors fields
j23414 1a168b5
Ingest: change `genbank_accession` to `accession`
j23414 cca844c
Rename phylogenetic/config to phylogenetic/defaults
j23414 a56685a
Phylogenetic: Change `genbank_accession` to `accession`
j23414 4acba65
Automatically drop is_lab_host=true records during phylogenetic workflow
j23414 65520e5
Add frequencies panels
j23414 1b6424b
Tip frequency strain ID must match the displayed strain ID in the fin…
j23414 b8b2fa3
Drop set_final_strain_name.py
j23414 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I was curious what was going on here, so I took a look. There is mismatch in the strain id used in the main JSON and the frequencies JSON so Auspice cannot link the strains to their frequencies.
Since the main JSON is getting it's strain name set to the
display_strain_field
infinal_strain_name
, the frequencies JSON needs to use the same field here: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.
Ah, the underlying issue was correct, but the suggestion caused CI to fail. This because the newick tree uses the accession as id so it cannot be matched with the metadata strain.
Separately discussed with @j23414 to remove
set_final_strain_name.py
as suggested in nextstrain/public#5 so that both use the accession as the strain id.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.
Just logging that @joverlee521 and I chatted that augur frequencies takes
tree.json
file, which is ID'd onaccession
to match against themetadata.tsv
file. Ergo, it might be time to removeset_final_strain_name.py
so that both the main JSON and the frequencies JSON use the accession as the strain id.I'll make the changes and re-run tests, thanks!
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.
Nice debugging! Whenever things look strange in Auspice I'd suggest first checking the console logs which often contain useful information (i.e. the browser's developer console when viewing Auspice). In this case it had hundreds of warnings logged - perhaps Jover did just this?
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.
Ah, good to know that Auspice warns about this! I didn't look at the console logs, I was just inspecting the frequencies JSON and noticed the strain names were all accessions.