--- Begin Message ---
Hi All,
I setup galaxy in my local system successfully and I was able to install
tools from ToolShed.
My requirement:
Assume that multiple galaxy instances are running on different systems.
Both the ToolShed will be able to access a private repository(with
custom/installed
--- Begin Message ---
Hi folks,
I am trying to integrate some of my local Perl scripts into a downloaded
instance of Galaxy. So far the script with a simple "in_file to out_file"
format worked great, but I am having problems understanding how to treat
scripts with multiple output files that share
For various reasons, I installed a Homebrew of python instead of the system
version on OSX 10.9.2.
Now, when galaxy initializes, it isn't looking in the right location for
eggs (or they aren't placed in the right spot on my system). I was able to
manually install several of the eggs and the galaxy
Hi all,
Following the instruction on
https://wiki.galaxyproject.org/Admin/Config/ApacheProxy to use Apache as proxy
for Galaxy, I got stuck to put directives into the configuration file.
The steps I took include:
1. install apache2: sudo apt-get install apache2
2. ins
Hi,
This is mainly a message to Carlos and Eric who volunteered to get
involved with my Debian packaging, but of course any other help will
also be appreciated. If either of you can spare time now it is a good
moment to do so.
I've been working on my package stuff over the last couple of weeks a
Hi Peter,
running and editing results in that error.
Ciao,
Bjoern
Am 24.03.2014 16:41, schrieb Peter Cock:
When do you see this error? When importing the workflow,
running it, editing it?
Peter
On Mon, Mar 24, 2014 at 2:45 PM, Björn Grüning
wrote:
Hi,
anyone saw that error already and has
Hello Michael,
Environment variables properly defined in a tool's associated
tool_dependencies.xml file contained in an installed Tool Shed repository
should be available to the tool's environment at runtime. Do you have an
example where you are not seeing this?
Greg Von Kuster
On Mar 21, 20
When do you see this error? When importing the workflow,
running it, editing it?
Peter
On Mon, Mar 24, 2014 at 2:45 PM, Björn Grüning
wrote:
> Hi,
>
> anyone saw that error already and has a fix or workaround?
> It happens with:
>
> http://toolshed.g2.bx.psu.edu/view/peterjc/secreted_protein_wo
Hi,
anyone saw that error already and has a fix or workaround?
It happens with:
http://toolshed.g2.bx.psu.edu/view/peterjc/secreted_protein_workflow
http://toolshed.g2.bx.psu.edu/view/galaxyp/proteomics_rnaseq_splice_db_workflow
Error - : 'NoneType' object has no
attribute 'iteritems'
UR
What are the configuration steps required for allowing a local Galaxy
installation to be restarted without affecting currently running jobs? I have
Galaxy using DRMAA to submit jobs onto a backend cluster. I thought that
enable_job_recovery = True should allow this, but in a few tests I have f
Hello Bjorn,
Thank you for your response. Indeed, I do want to have the stdout, but I
don't want it to show up in the history item. I will try the suggestion to
print 10 empty lines at the beginning of stdout.
Greetings,
Hans
On Mon, Mar 24, 2014 at 11:18 AM, Björn Grüning
wrote:
> Hi Hans,
>
Hi Hans,
you can remove the entire stdout if you want, but that is probably not
what you want. An other hack I can imagine is to insert 10 empty lines
at the beginning of stdout.
Ciao,
Bjoern
Am 24.03.2014 10:40, schrieb Hans van Leeuwen:
Hi,
Currently if there is anything written to stdou
Hi,
Currently if there is anything written to stdout it is also shown in the
expanded history item of the job (in the right hand history panel). Is
there a way to suppress that? I searched for a possible solution but could
not find anything.
Thank you,
Best regards,
Hans van Leeuwen
___
13 matches
Mail list logo
