On Mon, Sep 30, 2013 at 7:07 AM, ruiwang.sz wrote:
> Hi Peter,
>
> Thanks! I got it working by putting a suppressMessages() around the function
> call.
Great, but what I meant was just add this to your XML file to tell Galaxy
to ignore the stderr and only use the return code for deciding if there
Hi Peter,
Thanks! I got it working by putting a suppressMessages() around the
function call.
I might have some questions on how to generate output file names on the
fly...let me make some attempts
first. :-)
Best,
Rui
On Sun, Sep 29, 2013 at 10:54 PM, ruiwang.sz wrote:
> Hi Peter,
>
> Thanks
Hi Peter,
Thanks for the reply.
I checked the history view. I don't see anything when I clicked the "i"
icon and click the stderr link. However, here is what I see if I click the
little bug icon next to the "i":
Tool execution generated the following error message:
Loading required package: Ge
On Sun, Sep 29, 2013 at 8:47 PM, ruiwang.sz wrote:
> Hi Guys,
>
> I'm doing a very simple test about deseq2...there is a weird situation
> always happening:
>
> It looks like the deseq2 tool executed just fine, without any error, and the
> result files were created, but after the set_metadata, gal
Hi Guys,
I'm doing a very simple test about deseq2...there is a weird situation
always happening:
It looks like the deseq2 tool executed just fine, without any error, and
the result files were created, but after the set_metadata, galaxy always
'set dataset state to ERROR'.
The xml file for this
