A fix for these warnings is in revision 6048 of galaxy-central -
again, thanks for pointing them out Michael.
For the record, the warnings were from the HSmetrics and GCbias tools
and arose because there is a user configurable maxheap parameter that
is not available by default - it is commented ou
I have never setup a Galaxy instance fronting multiple clusters, but it's
something I would like to explore. I have a dedicated cluster to run Galaxy
jobs and I've got another a shared cluster to which I hope Galaxy can assign
jobs when the dedicated cluster is too busy.
>From my understanding of
It is there:
data_filesystems:
galaxyData:
- size: 200
vol_id: vol-5b059a30
services:
- service: SGE
- service: Postgres
- service: Galaxy
static_filesystems:
- filesystem: galaxyIndices
size: 700
snap_id: !!python/unicode 'snap-5b030634'
- filesystem: galaxyTools
size: 2
snap_id:
Does anyone know how to prevent the .txt suffix from being added to files
downloaded from Galaxy? For example, a fasta file is downloaded as
xxx.fasta.txt, instead of xxx.fasta.
Wondering,
David Hoover
Helix Systems Staff
http://helix.nih.gov
Hi Guys
I am trying to install Galaxy on Red Hat Enterprise Linux Server release
5.7 (Tikanga). I have installed Python 2.6. Our server is behind a
proxy that needs to be authenticated. I have set up the proxy for
Mercurial as described in
http://www.selenic.com/mercurial/hgrc.5#http-proxy
No
Good afternoon,
When starting galaxy I find the following errors logged in the paster.log
galaxy.tools DEBUG 2011-09-26 13:58:21,577 Loaded tool: PicardASMetrics 0.03
galaxy.tools.test DEBUG 2011-09-26 13:58:21,625 Error in add_param for maxheap:
Unable to determine parameter type of test input
Are you continuously running this instance and just restarting it or do you
start a clean instance each time?
I'd suggest ensuring the persistent_data.yaml in your cluster's bucket is
correct (see below), terminating this instance, and starting a new one with
the same user data as used for this clu
