Skip to content
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

Fix phylo input #40

Merged
merged 3 commits into from
Apr 15, 2024
Merged

Fix phylo input #40

merged 3 commits into from
Apr 15, 2024

Conversation

joverlee521
Copy link
Contributor

@joverlee521 joverlee521 commented Apr 11, 2024

Description of proposed changes

I missed this in review of #38.
The phylogenetic workflow was still pulling from old S3 URLs
and not the ingest workflow output data.

Checklist

  • Checks pass

I missed this in review of #38.
The phylogenetic workflow was still pulling from old S3 URLs
and not the ingest workflow output data.

This commit corrects the S3 URL to the ingest output files and updates
the `strain_id_field` config param to use the appropriate ID column
from the ingest output.
@joverlee521 joverlee521 force-pushed the fix-phylo-input branch 2 times, most recently from c73dde5 to a42192d Compare April 11, 2024 23:35
@joverlee521
Copy link
Contributor Author

Triggered trial phylogenetic workflow run with

gh workflow run phylogenetic.yaml --ref fix-phylo-input -f trial_name=fix-phylo-input

@j23414
Copy link
Contributor

j23414 commented Apr 12, 2024

Thank you for working on this! I'll be curious how you solve the problem of adding an "Accession URL". The accession is important for investigating outliers in the tree or getting to the full GenBank entry.

Screenshot 2024-04-12 at 9 16 27 AM

I'd been using a post-processing script in zika: https://github.com/nextstrain/zika/blob/9892009b95ea802f288142734614e29f00212922/phylogenetic/scripts/set_final_strain_name.py#L6-L15

But I think you mentioned there may be a more straightforward method: nextstrain/zika#32

@joverlee521
Copy link
Contributor Author

joverlee521 commented Apr 12, 2024

Thank you for working on this! I'll be curious how you solve the problem of adding an "Accession URL". The accession is important for investigating outliers in the tree or getting to the full GenBank entry.

I'd been using a post-processing script in zika: https://github.com/nextstrain/zika/blob/9892009b95ea802f288142734614e29f00212922/phylogenetic/scripts/set_final_strain_name.py#L6-L15

But I think you mentioned there may be a more straightforward method: nextstrain/zika#32

Thanks for bringing this up @j23414, I totally forgot about this issue.
I've fixed it with 8acbbca 71f52b9. Let me know if you have any questions!

@joverlee521
Copy link
Contributor Author

Hmm, CI failing is a separate issue due to installation of the Conda runtime failing.

@joverlee521
Copy link
Contributor Author

I'll wait to merge this on Monday so I can monitor for anything unexpected.

I'll probably drop 5c85067 before merging since I'm working on a better way to split out ingest/phylogenetic GH Action workflows in https://github.com/nextstrain/zika/tree/reusable-workflows

Match the ingest outputs to use `genbnak_accession` column.
Include the `genbank_accession` as a separate field in the exported
metadata so that it can be searched in the Auspice filter input
and so Auspice automatically generates a URL for the GenBank accession.
@joverlee521 joverlee521 marked this pull request as ready for review April 15, 2024 17:56
@joverlee521 joverlee521 requested a review from a team April 15, 2024 17:56
@joverlee521 joverlee521 merged commit c81b01e into main Apr 15, 2024
32 checks passed
@joverlee521 joverlee521 deleted the fix-phylo-input branch April 15, 2024 17:56
@joverlee521
Copy link
Contributor Author

Manually deleted cache and triggered a new run of ingest-to-phylogenetic so that the live builds are actually using the ingested data.

j23414 added a commit that referenced this pull request May 21, 2024
Updates the links of the FASTA and metadata in the phylogenetic README.
This probably should have been part of the previous PR:

#40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants