Closed JoshLoecker closed 3 years ago
I have been able to alleviate the issue by setting the --t
option to 1. Obviously, this is not optimal as it does not use the maximum number of threads, but it does narrow down the issue slightly.
Hi Josh,
Any chance you could share the file where this happens? If not, could you provide more of the output printed to the terminal before the error occurs? This would help on how to best deal with the empty sequence error.
@ksahlin, oops. Sorry about that. Here is a link to the fastq I am using: https://pastebin.com/15kNuA0V
Additionally, here is the full terminal output of the command: https://pastebin.com/n0K2T5BF
Shoot, it says that the fastq link expired. I got the output file though. Any chance you could send the reads again?
@ksahlin Hmm, not sure why that happened. Here is a new link: https://pastebin.com/GHdq8xfN
@ksahlin I can't seem to get this link to work either. Here is a different website: https://controlc.com/16e2b9d0
Ok, great that worked. Thanks!
Alright, I fixed it and the new version (0.0.6.1) is available on PyPI and here on Github. Thanks for the report!
I am getting this error within the
multiprocessing.pool.RemoteTraceback
library. I am running the following commandAnd I am receiving this error