You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Once the new version of Augur is out, will these at least need to use --no-default-rules, or will they be OK because their custom rules will essentially include the default rules as they fetch (a similar version of) the defaults and use them as custom rules?
Once the new version of Augur is out, will these at least need to use --no-default-rules, or will they be OK because their custom rules will essentially include the default rules as they fetch (a similar version of) the defaults and use them as custom rules?
They should be okay because their custom rules still include the ncov-ingest rules that will override the default Augur rules.
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: