Closed holtjma closed 3 years ago
Hi @holtjma
Probably one sample that has a rare and complicated genotype caused the error. Could you try the latest master branch and see if it would work (the sample would probably get a no-call but hopefully there is no more program error)?
Thanks, Xiao
Yes, that did stop the crash and it generated a no-call. Any ideas on figuring out the no-call?
Would it be possible to send me the json output file for that sample?
Yep, I sent them to your email (I think it's the correct address from a previous issue).
Hi Matt,
Could you check if the latest master branch fixes this sample?
Thanks, Xiao
Yes, it's reporting *13+*4/*9
now, which I think is equivalent to what you indicated via email. If so, I think you can close this one. Will this be in a released version soon?
Great. Just made a new release.
Hello,
We've been using Cyrius-1.0 for a while and came across and error recently. I updated to v1.1 and the error is persisting. The command we're using is:
And the output is as follows:
Let me know if you need any additional information from me!