-
Notifications
You must be signed in to change notification settings - Fork 0
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
Remove use of ncov-ingest geolocation rules #17
Comments
Once the new version of Augur is out, will these at least need to use |
They should be okay because their custom rules still include the ncov-ingest rules that will override the default Augur rules. |
Remove the use of the ncov-ingest geolocation rules since Augur now uses the built-in geolocation rules by default. Depends on the release of <nextstrain/augur#1745> Part of larger migration nextstrain/public#17
Remove the use of the ncov-ingest geolocation rules since Augur now uses the built-in geolocation rules by default. Depends on the release of <nextstrain/augur#1745> Part of larger migration nextstrain/public#17
Remove the use of the ncov-ingest geolocation rules since Augur now uses the built-in geolocation rules by default. Depends on the release of <nextstrain/augur#1745> Part of larger migration nextstrain/public#17
Remove the use of the ncov-ingest geolocation rules since Augur now uses the built-in geolocation rules by default. Depends on the release of <nextstrain/augur#1745> Part of larger migration nextstrain/public#17
Remove the use of the ncov-ingest geolocation rules since Augur now uses the built-in geolocation rules by default. Depends on the release of <nextstrain/augur#1745> Part of larger migration nextstrain/public#17
Remove the use of the ncov-ingest geolocation rules since Augur now uses the built-in geolocation rules by default. Depends on the release of <nextstrain/augur#1745> Part of larger migration nextstrain/public#17
Remove the use of the ncov-ingest geolocation rules since Augur now uses the built-in geolocation rules by default. Depends on the release of <nextstrain/augur#1745> Part of larger migration nextstrain/public#17
Remove the use of the ncov-ingest geolocation rules since Augur now uses the built-in geolocation rules by default. Depends on the release of <nextstrain/augur#1745> Part of larger migration nextstrain/public#17
Once
augur curate apply-geolocation-rules
uses built-in default rules (nextstrain/augur#1744 + nextstrain/augur#1745), we can remove the use of ncov-ingest geolocation rules from pathogen ingest workflows.TODOs
Based on GitHub search
We can prioritize updating the pathogen-repo-guide, docs, zika, and mpox
Other pathogens can be updated later as needed
The text was updated successfully, but these errors were encountered: