I am trying to run the Unicycler assembler on a fastq paired-end dataset (groomed and joined or unjoined). The job just sits there with the message that it is waiting to run. However, after even 48 hours the job never starts. I have tried restarting the job, and I have tried using Trinity instead. I have used both the Unicycler and Trinity assemblers on this exact dataset in the past and the job started and completed in a matter of hours.My usage is at 50%, and other tools seem to work just fine so it appears that the problem is confined to the assemblers. Is anyone aware of problems that have cropped up with this set of tools?
Update - there was a problem on our side. It is now corrected. Queued Unicycler jobs will start as resources become available. Avoid stopping and restarting jobs or the earlier placement in the queue will be lost.
Thanks for reporting the problem! Jen, Galaxy team