Hi,
I used the SAM to FASTQ tool to divide78 lines of Illimina paired end
sequences in SAM format to FASTQ format. The read 2 data set works fine, and
I used the FASTQ masker and then FASTQ to FASTA tools.
I went to repeat those steps with the the read 1 data set. It errors with:
Error
Hi,
The main page (analyze data) keeps coming back with a message saying error
getting history updates from the server: bad gateway and is not performing any
jobs. It has been doing it since this morning my time (so about 5 hours).
Cheers,
Megan
Hi Jen,
Thank you for the information regarding the FastQ information. It was really
helpful.
Lately, I have been getting the following error: Error getting history update
from this server- Bad Gateway. This occurred after I tried to reupload some
pre-aligned/ and indexed BAM files from NCBI
John,
Could you create a pull request with your changes from the branch in github?
I'll accept them and then commit my additions and changes. Today is the
freeze so I'd like to get this in to the next release.
Thanks,
---nate
On May 17, 2013, at 11:21 AM, John Chilton wrote:
Hey All,
Hello Peter,
Sorry for the delay on this - I was out of the lab last Friday.
On May 17, 2013, at 10:16 AM, Peter Cock wrote:
Hi Greg,
Do you guys have a rough plan for when inter-ToolShed dependencies
will be supported?
There is a bunch of work to do between now an the GCC to prepare for
Done.
On the topic of the freeze, if Dannon's change requiring all metadata
to be set externally is going to be included I would suggest someone
looking at build_command_line in runners/__init__.py.
On Mon, May 20, 2013 at 2:47 PM, Greg Von Kuster g...@bx.psu.edu wrote:
Hello Peter,
Sorry for the delay on this - I was out of the lab last Friday.
On May 17, 2013, at 10:16 AM, Peter Cock wrote:
Hi Greg,
Do you guys have a rough plan for when inter-ToolShed dependencies
will be
On May 19, 2013, at 11:41 PM, Fields, Christopher J wrote:
I've been seeing this error popping up quite a bit recently (we're using
Torque 3.0.5), which is giving a general 'cluster failure' Galaxy error on
jobs:
galaxy.jobs.runners.pbs WARNING 2013-05-19 18:56:44,073 (10588)
Hi Megan,
This issue is now resolved on the public Main instance. Thanks for
reporting the problem,
Jen
Galaxy team
On 5/19/13 8:44 PM, Megan Wilson wrote:
Hi,
The main page (analyze data) keeps coming back with a message saying
error getting history updates from the server: bad gateway
Hi Zain,
On 5/19/13 1:35 PM, Zain A Alvi wrote:
Hi Jen,
Thank you for the information regarding the FastQ information. It was
really helpful.
Lately, I have been getting the following error: Error getting
history update from this server- Bad Gateway. This occurred after I
tried to
On May 20, 2013, at 9:45 AM, Nate Coraor n...@bx.psu.edu
wrote:
On May 19, 2013, at 11:41 PM, Fields, Christopher J wrote:
I've been seeing this error popping up quite a bit recently (we're using
Torque 3.0.5), which is giving a general 'cluster failure' Galaxy error on
jobs:
On May 20, 2013, at 3:31 PM, Fields, Christopher J wrote:
On May 20, 2013, at 9:45 AM, Nate Coraor n...@bx.psu.edu
wrote:
On May 19, 2013, at 11:41 PM, Fields, Christopher J wrote:
I've been seeing this error popping up quite a bit recently (we're using
Torque 3.0.5), which is giving a
Hi,
After the latest upgrade (april), I'm having issues when starting
(batch) workfows. Sometimes, it seems that step dependencies are not
stored correctly, leading to some steps being started too soon, without
prior datasets being completed. Specifically, for some workflows, some
of the
13 matches
Mail list logo
