Closed rdenise closed 1 year ago
I thought I had fixed this bug. I'll look into it. Can you share the data with me? It would be really helpful.
Would you happen to have an email address I can send you the fasta file?
I found the underlying problem and will push a fix shortly. The error happened when the score calibration was executed on a sample where proviruses were not identified.
That said, I had to use a different dataset to find the issue because geNomad did find a provirus in your data. This shouldn't happen if we used the same parameters. I'll follow up by email.
I encountered the following error when running genomad score_calibration:
I was running the following command:
I am using genomad version 1.3.2 installed using conda.
I can provide the fasta file ZSM005_contigs.filtered.sorted.fasta if it would be helpful in troubleshooting this error.