Howdy, Andrew,
One possibility is that there are more jobs on the cluster. I'm not
familiar enough with the galaxy interface to know if there's an easy
way to tell how much time the job sits on the cluster's queue waiting
and how much time the job is actually running.
Assuming there's no
Hi - is there a reason Lastz is very slow right now? I am mapping 2-3,000,
reads against a single, 11Kb, sequence and find that jobs are either returning
an error or taking 16-24hrs to get done. This time frame was more like 30
minutes two weeks ago. Is there a way to speed this up? Thanks in ad
2 matches
Mail list logo
