Closed volcano1998 closed 1 year ago
Something is wrong if it's stuck on step call_merge_haplotypes
for that long. That rule just concatenates merged variant calls and writes them into a file. If you have output from the rule (I have snakemake push mine into a cluster log), are there any error messages? You can kill and restart the pipeline, it will pick up from where it left off unless something upstream changed (i.e. if the timestamp on the assembly FASTAs changed, the whole pipeline will re-run).
Hi thank you! I'm now using another server(which I believe is more powerful) to run PAV, it finished in < 2days. So I guess it could be due to the server's capability. Now I submit the rest of PAV job to the other server too, hopefully they won't be stuck again. I will keep you updated!!
Thank you again!
Was the second run successful, or was it still hanging?
Hi, after that I was busy with other stuff so did not pay much attention to the running. Just checked it: I was able to finish running 2 CLR libraries within 2 days. Still have one CLR library job which was timed out (time limit was set to 2 days), so I resubmitted the job and see how it will be.
I will keep you updated about the last one.
Thank you for checking!
Hi dear author, I'm running PAV on our university's cluster (slurm). Library is Pacbio CLR, I gave 500G mem and 30 cpus to run it, but it is running for more than 9 days and I still can not see the result. I ran PAV on Pacbio Hifi reads assembly before and it took less than 4 hours. Any thoughts on how should I accelerate it?
I think it is stuck there for 7 days. I ran PAV on other libraries(CLR), same issue.
Any thoughts?