Question: Infinite Tophat Run
gravatar for Jonsson, Philip
6.2 years ago by
Jonsson, Philip10 wrote:
I am running Galaxy online, excuting TopHat on a fastq file, something which I previously have done without problems. This time, my data file is maybe double the size and does not seem to ever get done (I'm on the fourth day or so). Previously I have never experienced that this has taken more than 24 hrs. Any idea what could be going on? /Philip
galaxy • 852 views
ADD COMMENTlink modified 6.1 years ago by Jennifer Hillman Jackson25k • written 6.2 years ago by Jonsson, Philip10
gravatar for David PANG
6.1 years ago by
David PANG20
United States
David PANG20 wrote:
Hi, there, I just got two genome-wide Bisulfite sequences from BGI and start to analyze the data. I am trying to use Galaxy; but I find there is no such platform available. Does anybody know where I can find this kind platform at Galaxy or other places. Thanks David -- David PANG, Ph.D. Department of Plant and Soil Science, Texas Tech University Lubbock, TX 79409 Work: 806-742-5073(ext.263) FAX: 512-582-8568 Cell: 512-850-9169 Website
ADD COMMENTlink written 6.1 years ago by David PANG20
gravatar for Jennifer Hillman Jackson
6.1 years ago by
United States
Jennifer Hillman Jackson25k wrote:
Hi Philip, I'll reply to your bug report, but just for general information to others, the most common cause for delays is that the Galaxy main server is busy and/or the job itself large. Jobs can be queued ('grey') for up to a day when we are at peak usage. It is important to not stop/restart jobs at this stage, otherwise they move to the end of the queue again. Once running ('yellow'), a job such as Tophat has normally up to 72 hours to complete. How long a job will run depends on the type of job, the parameters used, and the size of the inputs. Should there be a job size issue, the job will error out, often indicating that it is too large to run on the public Main instance (and sometimes any instance) due to the parameters selected and the inputs. In these cases, the next step is reviewing the parameters and inputs, making adjustments, and then determining if a cloud solution with more resource (often memory) is a potential solution worth testing out. If jobs are urgent, a cloud or local solution is also an option, large or small. Which to choose depends on what resource you prefer or have access to: Occasionally there are other factors. Please feel free to write in, as you have done, with a bug report to check in and see if this is the case. Good question and I will be getting back to you shortly about your specific situation, Best, Jen Galaxy team -- Jennifer Jackson
ADD COMMENTlink written 6.1 years ago by Jennifer Hillman Jackson25k
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 168 users visited in the last hour