Closed erinyoung closed 1 year ago
Hey @erinyoung! Thanks for reporting this issue. This is happening due to there not being a reference for Paenibacillus urinalis in the assembly ratio database. We knew this was inevitably going to happen, but thought it was guarded against. We'll work on getting the pipeline to properly react in this situation. This specific isolate also brought up a new scenario where NOTHING in the ANI database passes the reporting thresholds. We'll have to dig into this one after clearing up the first issue.
Closing this ticket. The issue was resolved by updating the sketch file database used for ANI. Other improvements to handling low/missing species have been added to the v2.1.0-dev branch and will be available when that branch becomes a stable release.
Describe the bug
phoenix fails when calculating assembly error for sample 2022CK-00833
Impact
To Reproduce The fastq files for this isolate can found on the SRA with accession SRR23080371
Expected behavior No error?
Screenshots Error is pasted above.
Logs If applicable, please attach logs to help describe your problem. These would be the
.command.err
,.command.out
,.command.sh
and/or the.nextflow.log
files associated with the run/process that failed. The.nextflow.log
file is in directory you ran the pipeline from. The.command.XXX
files are found in<directory you ran pipeline from>/work/XX/xxxxxxxxxxxxxx
here the x and X are a random string of letters/numbers associated with the process. As the pipeline runs on CLI you will see the beginning of these strings to the left of the process that is running.I have attached the files here. I have changed their names so that they can be uploaded in github issues (i.e. no files starting with '.' and I changed the extension). command.log.txt command.out.txt command.run.txt command.sh.txt command.trace.txt command.begin.txt command.err.txt
Additional context Add any other context about the problem here. If you have done any internet sleuthing already please link to any relevant posts on the topic.