Filter Fastq

Question: Filter Fastq

5.6 years ago by

Hi, We have two Filter FASTQ jobs running on the Galaxy public server. Both jobs have been running for more than four days. This seems like an excessive amount of runtime. Do Filter FASTQ jobs normally take this long to run? Richard

galaxy • 782 views

ADD COMMENT • link •

modified 5.6 years ago by Jennifer Hillman Jackson ♦ 25k • written 5.6 years ago by Casey,Richard • 40

5.6 years ago by

Jennifer Hillman Jackson ♦ 25k

United States

Jennifer Hillman Jackson ♦ 25k wrote:

Hi Richard, The public Main Galaxy server has been very busy lately. To let you know, the size of the job will not determine when a job will start, only the time it was started/queued with respect to other user's jobs also queued and in less common circumstances the specific type of job (that requires a particular cluster node type - this was not the case for your job). How long a job executes (will be in the "yellow" running state) is related to the size of the inputs, the type of job, and parameters. I see that these have now failed with a cluster error - please re-run the failed jobs one more time. If you continue to have problems, please submit one of the error datasets as a bug report, leaving all inputs/outputs undeleted. http://wiki.galaxyproject.org/Support#Reporting_tool_errors Very sorry that this was causing confusion. And thanks Peter for the help! Jen Galaxy team -- Jennifer Hillman-Jackson Galaxy Support and Training http://galaxyproject.org

ADD COMMENT • link written 5.6 years ago by Jennifer Hillman Jackson ♦ 25k

5.6 years ago by

Peter Cock • 1.4k

European Union

Peter Cock • 1.4k wrote:

On Thu, May 9, 2013 at 12:27 PM, Casey,Richard Which FASTQ filtering tool exactly are you referring too? The one called "Filter FASTQ reads by quality score and length" in the left hand column, tool ID fastq_filter? How big were the input files? Peter

ADD COMMENT • link written 5.6 years ago by Peter Cock • 1.4k

Yes, it's the "Filter FASTQ reads by quality score and length" in left-hand pane. There were actually four separate runs on four datasets. Two of them finished in about a day but the other two have been running for about 4 days. The input files range in size from 6GB - 11GB Today, the two 4-day jobs both aborted with error message: Job output not returned by PBS: the output datasets were deleted while the job was running, the job was manually dequeued or there was a cluster error. Richard

ADD REPLY • link written 5.6 years ago by Casey,Richard • 40

Please log in to add an answer.

Similar posts • Search »