Closed thsyd closed 5 years ago
Yes, the job exceed the default wall time, which is 1 hr. See the FAQ: https://canu.readthedocs.io/en/latest/faq.html#how-do-i-run-canu-on-my-slurm-sge-pbs-lsf-torque-system. You can add a gridOptions="-l walltime=24:00:00"
as an example to request 24 hrs.
Hi, I hope it's ok for me to ask for some guidance. I'm assembling an apox 5gb bacterial genome. Input Nanopore rapid barcoding kit, run on Minion. Deepbinner -> albacore -> porechop (trim only). Approximately 50x coverage. nano stats:
using canu 1.8 installed last week in conda via the bioconda repository. by
canu -version gives
Submitting to our HPC (running a unix based system) code exerpt below (initally run with 12 threads and 20gb RAM. The second time I increased to 28 threads and 120gb RAM to see if the error was due to running out of memory)
Canu.out:
I restarted canu by submitting the same job as before. Same error.
The final line of utgovl_ATCC25285.canu.ont.o22434458-2 (below) indicates the problem, yes? "PBS: job killed: walltime 3631 exceeded limit 3600"
I do not suppose that its the total walltime that is exeeded. The job is ended quite quickly. What is the best way to ask for more walltime for the jobs submitted as part of the unitigging step. Do I set it though gridOptions
or
gridOptionsCNS ?
Remove this text before submitting your issue!