Hi @seschmedes!
Iâm very sorry this is causing you trouble. This was something we added this morning to help filter out samples that are reported to have been taken before 2020 (we think itâs likely a year typo - 2002 is given!). The addition is that the argument --min-date 2019-10-01 is sent to augur filter.
This should work - but I believe the ability to take --min-date arguments in the YYYY-MM-DD format was something added to augur filter only in the last few months!
Can you try updating augur on your computer/cluster and re-running? I hope this should solve the problem.
However, I imagine you are not the only one who will run into this - thank you for reporting it! I will change the minimum date into a float so that this wonât impact any other users running slightly older versions of augur!
No problem! Sorry for the inconvenience. And thanks again for letting us know - Iâll be updating this to be a number instead, so that it doesnât impact others in the same way!
Welcome @Francis! The details about what went wrong with each step of the workflow (usually) get stored in the logs/ directory. For example, to find out what went wrong with the first filter command you posted, you can inspect the contents of the file logs/filtered.txt. If the contents of this file do not make sense, though, please share the contents here and we can help try to interpret it.
I noted above that usually we log all output from the workflow, but the subsample rule that you shared in your second post above has been an exception where we were not logging the output. We have just fixed this issue, so if you pull (or copy) the latest contents of the ncov repository and re-run your workflow, you should find information to help you debug the error in logs/subsample_north-america_usa_country.txt. As with the filter error above, please share the contents of the subsample log here, if you would like some help interpreting the output.
[quote=âFrancis, post:8, topic:137, full:trueâ]
Hi @jlhudd, Thanks for the prompt response,
I could run until 20 of 69 (29%)⌠then this error comes upâŚ
ERROR: All samples have been dropped! Check filter rules and metadata file format.
[Wed Oct 14 12:16:16 2020]
Error in rule subsample:
jobid: 57
output: results/asia/sample-global.fasta
shell:
augur filter --sequences results/masked.fasta --metadata data/skmc_metadata.tsv --include defaults/include.txt --exclude-where 'region=asia' --priority results/asia/proximity_region.tsv --group-by country year month --sequences-per-group 4 --output results/asia/sample-global.fasta 2>&1 | tee
(one of the commands exited with non-zero exit code; note that snakemake uses bash strict mode!)
-3 sequences were dropped during filtering
0 of these were dropped because of âcountry!=unitedarabemiratesâ
0 of these were dropped because of subsampling criteria
3 sequences were added back because they were in defaults/include.txt
89 sequences have been written out to results/asia_unitedarabemirates/sample-country.fasta
[Wed Oct 14 12:16:16 2020]
Finished job 51.
20 of 69 steps (29%) done
Shutting down, this might take some time.
Exiting because a job execution failed. Look above for error message
Complete log: /Users/francis/ncov/.snakemake/log/2020-10-14T121547.593524.snakemake.log
When I check the log, some of the logs are empty
subsample_regions_global.txt
mask
diagnostics
aggregate_alignments
recency_asia
recency_global
recency_asia_unitedarabemirates
is this error due to the global data, sample rule or metadata format?
Your support is highly appreciated