Re: [galaxy-dev] Galaxy and Toolshed issues
Hi Greg, thanks for the response Quoting Greg Von Kuster g...@bx.psu.edu on Tue, 31 Jul 2012 11:50:36 -0400: Hi Shaun, On Jul 31, 2012, at 9:37 AM, SHAUN WEBB wrote: Hi, I have been trying out the latest version of Galaxy and a newly installed local toolshed and I have a few questions/suggestions/bug reports: 1. Tool Versioning: a) As I understand from the wiki, when I create a new version of a tool in a tool shed I must then install the latest version in my Galaxy instance. This is not correct - you can choose to install any valid version of the tool(s). Can you let me know what content of the wiki resulted in this confusion? I'll be sure to make it more clear. This then shows up as two separate tools in my tool menu. Presumably it is best to change the xml description tag to reflect the version number and make tool versions distinguishable in the Galaxy tool menu? b) Would it make more sense to have a single entry for each tool in the tool menu and a drop down to choose which version to run in the tool gui? Similar to when I try to rerun a tool that is no longer installed I get a drop down option to use a derivative of that tool if it exists. Your above recommendation in (b) is exactly what will occur as soon as I get a chance to implement it. Perhaps my wording was unclear here. What I meant was if a new version of a tool is created in a tool shed I have to install that version to be able to use it, rather than using 'get updates'. This then results in multiple listings of the tool. But it sounds like you plan on improving this process anyway. c) The toolshed interface allows me to change the name of my tool. If I do this, then go to my Galaxy admin ui and try to get updates for my tool then it fails. Does it make sense to change a tools name after it is created? Is it possible to track previous tool names to avoid this happening? This should not occur. Where are you able to change the name of your tool? You are not even allowed to change the name of the repository if it has been cloned (you can change the name of the repository as long as it has not been cloned). Can you send me a screen shot of hte page that allows you to change the name of your tool in the tool shed? I'll provide a fix as soon as I see where the issue lies. OK, I guess I changed the name of my repository not tool. I then installed the tool via my local Galaxy instance. I can still change the name of the repository in my toolshed and when I try to get updates via Galaxy admin panel I get the following server error: AttributeError: 'NoneType' object has no attribute 'repo_path' Running toolshed tools: I have no problems installing tools from toolsheds via Galaxy admin interface, however I can't get these tools to run. They stay Grey forever and look like this in the manage jobs table: 65 x...@.xx.ac.uk 0 minutes ago toolshed.g2.bx.psu.edu/repos/aaronquinlan/bedtools/bedtools_coveragebed_counts/0.1.0 new None None None Do I have to set a tool runner or some other option for shed_tools? No special configuration settings are required in your local Galaxy instance to to run tools installed from a tool shed. If they stay in the queued state, there must be an issue in your local Galaxy instance that causes installed tools as well as tools included in the distribution to remain queued. It has nothing to do with the fact they were installed. No. All other tools run fine. Tools installed from either my toolshed or the Galaxy toolshed remain queued. If this is not a known issue then I will try to dig a little deeper to find the problem. Any pointers would be useful if you can think of why there should be a difference. Thanks for your help! Shaun -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] Upload local files
I finally wrote a script which can be used as a separate tool. The script takes one or more file paths which can be either a file or a directory. As soon as the script does not know the exact number of files to upload it places links to the files in __new_file_path__. The problem now is, that Galaxy copies the files pointed to into it?s database directory which results in the former problem of space overhead. Is there a way to let Galaxy only copy the links? Thanks in advance, Sascha Kastens Project Manager GATC Biotech AG Jakob-Stadler-Platz 7 D-78467 Konstanz Phone: +49 (0) 7531-81604110 Fax: +49 (0) 7531-816081 Email: s.kast...@gatc-biotech.com http://www.gatc-biotech.com http://www.twitter.com/gatcbiotech http://www.facebook.com/gatcbiotech http://www.xing.com/companies/gatcbiotechag GATC Biotech AG Chairman Supervisory Board: Fritz Pohl Board of Directors: Peter Pohl, Thomas Pohl, Dr. Marcus Benz UID: DE 142 315 733 | Registration: Konstanz, HRB 1757 | Registered Office: Konstanz The information contained in this email is intended solely for the addressee. Access to this email by anyone else unauthorized. If you are not the intended recipient, any form of disclosure, reproduction, distribution or any action taken or refrained from in reliance on it, is prohibited and may be unlawful. Please notify the sender immediately. The content of this email is not legally binding unless confirmed by letter. Original Message processed by CONSOLIDATE Subject: Re: [galaxy-dev] Upload local files Sent: Dienstag, 31. Juli 2012 00:08 From: Smithies, Russell (russell.smith...@agresearch.co.nz) Yes, we d like to do this as well. Our users data are all on the servers, not on their Windows PCs and requiring the admin create shared data libraries is an overhead we d rather avoid. Thanx, Russell Smithies Infrastructure Technician T 03 489 9085 M 027 4734 600 E russell.smith...@agresearch.co.nz Invermay Agricultural Centre Puddle Alley, Private Bag 50034, Mosgiel 9053, New Zealand T +64 3 489 3809 F +64 3 489 3739 www.agresearch.co.nz From: galaxy-dev-boun...@lists.bx.psu.edu [mailto:galaxy-dev-boun...@lists.bx.psu.edu] On Behalf Of Sascha Kastens Sent: Tuesday, 31 July 2012 2:09 a.m. To: galaxy-dev@lists.bx.psu.edu Subject: [galaxy-dev] Upload local files Hi devs, when using the upload tool it would be nice to let the user specify paths to files stored on our internal servers like the admin can when choosing to add data to a library. Also it would be nice to be able to link to these files. Unfortunately I was not able to find the tool for uploading files into a library so it would be nice if you can give me a hint. With this information I should be able to extend the normal upload tool. Thanks in advance! Cheers, Sascha Kastens Project Manager GATC Biotech AG Jakob-Stadler-Platz 7 D-78467 Konstanz Phone: +49 (0) 7531-81604110 Fax: +49 (0) 7531-816081 Email: s.kast...@gatc-biotech.com http://www.gatc-biotech.com http://www.twitter.com/gatcbiotech http://www.facebook.com/gatcbiotech http://www.xing.com/companies/gatcbiotechag GATC Biotech AG Chairman Supervisory Board: Fritz Pohl Board of Directors: Peter Pohl, Thomas Pohl, Dr. Marcus Benz UID: DE 142 315 733 | Registration: Konstanz, HRB 1757 | Registered Office: Konstanz The information contained in this email is intended solely for the addressee. Access to this email by anyone else unauthorized. If you are not the intended recipient, any form of disclosure, reproduction, distribution or any action taken or refrained from in reliance on it, is prohibited and may be unlawful. Please notify the sender immediately. The content of this email is not legally binding unless confirmed by letter. Attention: The information contained in this message and/or attachments from AgResearch Limited is intended only for the persons or entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipients is prohibited by AgResearch Limited. If you have received this message in error, please notify the sender immediately. ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] Update Galaxy instance with Mercurial error
Hi Makis, This should work to get you an update-able galaxy instance going forward, without having to manually migrate anything. Please note that this method will clobber any existing changes to code, so if you've modified any of the core galaxy you'll need to patch the new files. All of your data and database settings will remain intact (but still do steps 1 and 2). 1) Back up everything, just in case 2) Make sure you did step #1 2) cd into the root galaxy directory and `hg init` 3) create a file, galaxy_root/.hg/hgrc with the following two lines: [paths] default = https://bitbucket.org/galaxy/galaxy-dist 4) And again from the galaxy root `hg pull` 5) Finally `hg update -C` And you should be good to go. -Dannon On Jul 31, 2012, at 6:05 AM, Makis Ladoukakis makis4e...@hotmail.com wrote: Dear Galaxy users, I am running a Galaxy instance in my institution's server and I want to keep it up to date with the latest release. Nevertheless when i try hg incomingi get the following error: abort: There is no Mercurial repository here (.hg not found)! Most probably the administrator of the server has downloaded the Galaxy-dist directory without the use of Mercurial (I was suspicious of that all along as the directory of the Galaxy installation is named galaxy_dist and not galaxy-dist). Is there another way to update my instance? Thank you, Makis Ladoukakis ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] egg distribution error when running galaxy-central
Clare- Have you resolved this yet? I had seen similar issues with respect to pycrypto before I used virtualenv, but I don't believe that I saw it afterwards. I'll take a look and see if I can reproduce it. I only have obvious things to recommend right now. For example, make sure that the environment has been loaded each time. Check http://wiki.g2.bx.psu.edu/Admin/Config/Performance/Production%20Server#Use_a_clean_environment , which I'm sure you've already done. -Scott - Original Message - On 1 August 2012 15:28, Clare Sloggett s...@unimelb.edu.au wrote: I can run galaxy-dist without problems and have been working with that (so its eggs are all installed already), but now I want to create a pull request so want to run galaxy-dist. oops, of course I mean 'so want to run galaxy-central.' -- Clare Sloggett Research Fellow / Bioinformatician Life Sciences Computation Centre Victorian Life Sciences Computation Initiative University of Melbourne, Parkville Campus 187 Grattan Street, Carlton, Melbourne Victoria 3010, Australia Ph: 03 903 53357 M: 0414 854 759 ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] Local instance and storage space to provide
Hi Sarah- I'm sure others have experiences that could help, so I hope they will chime in. Nate put together some slides two years ago on production setups, including some architecture for the server main.g2.bx.psu.edu: http://wiki.g2.bx.psu.edu/Events/GDC2010?action=AttachFiledo=gettarget=GDC2010_building_scalable.pdf There is also a wiki page describing production environments: http://wiki.g2.bx.psu.edu/Admin/Config/Performance/Production%20Server Again, I'm sure others have had different experiences with both more and less hardware on hand. Of course your mileage may vary based on the tools being used (which in your case I'm guessing is Tophat), the number of datasets that will need to be analyzed, and so on. I hope that helps! -Scott - Original Message - Dear all, To purchase equipment related to a local instance of Galaxy, I would like to have your feedback. Did you notice load problems when 10 to 20 users launch jobs at the same time and on a single instance of Galaxy, with mi-RNA or RNA seq data ? What do you recommend in terms of storage space, number of nodes, number of instances? Thank you in advance, Sarah Maman ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] PBS Server Throwing Errors
Hi Dan- Thanks again for your great hospitality at UCI! It looks like you've done most of the sane things, and a quick check looks like the PBS egg is requesting protocol version 1 while the server supports protocol version 2. One possibility is that there is a protocol mismatch, which could be the result of using an old library. We can check if the egg is at fault first - try the following link for compiling the pbs_python.py egg yourself and try the example to see if the connection and a simple stats-gathering operation (the examples/pbsnodes-a.py script from pbs_python) works: https://subtrac.sara.nl/oss/pbs_python/wiki/TorqueInstallation -Scott - Original Message - Hi, Galaxy Community, Greetings from The University of Chicago; I hope all who attended the Galaxy conference enjoyed it as much as I did. I have searched the mailing list archives as well as Google to a resolve problem I am seeing, however I am somewhat at a loss as to the next course of action I should be taking to bring this issue to a close. I am hoping that one of the bright minds on this mailing list could help me shed some light on the solution to my problem, or at least help me identify a root cause. I have configured Galaxy to integrate with TORQUE (version 4.0.2) server, and successfully built the PBS python egg as specified in the Galaxy documentation. I am using Python version 2.6 and the latest build of Galaxy. Whenever I launch a job from the Galaxy UI, I get the following error message(s) on the PBS server: 07/30/2012 15:42:48;0080;PBS_Server;Req;dis_request_read;conflicting version numbers, 1 detected, 2 expected 07/30/2012 15:42:48;0080;PBS_Server;Req;req_reject;Reject reply code=15058(Bad DIS based Request Protocol MSG=cannot decode message), aux=0, type=AlternateUserAuthentication, from galaxy@ 07/30/2012 15:42:48;0080;PBS_Server;Req;dis_request_read;conflicting version numbers, 1 detected, 2 expected 07/30/2012 15:42:48;0080;PBS_Server;Req;req_reject;Reject reply code=15058(Bad DIS based Request Protocol MSG=cannot decode message), aux=0, type=QueueJob, from galaxy@ 07/30/2012 15:42:48;0080;PBS_Server;Req;dis_request_read;conflicting version numbers, 1 detected, 2 expected 07/30/2012 15:42:48;0080;PBS_Server;Req;req_reject;Reject reply code=15058(Bad DIS based Request Protocol MSG=cannot decode message), aux=0, type=Disconnect, from galaxy@ 07/30/2012 15:43:01;0002;PBS_Server;Svr;PBS_Server;Torque Server Version = 4.0.2, loglevel = 1 One thing I did notice, that suggests there might be a problem, is that there is no hostname after the galaxy@; most of the other messages in this log file have a host name appended to log entry, i.e.: 07/30/2012 15:43:38;0100;PBS_Server;Req;;Type StatusJob request received from root@sc01, sock=10 I have completed a tcpdump on the schedule node, and I can definitely see bi-directional traffic between the Galaxy server and the scheduler node on TCP port 15001. In addition to this, I have installed the TORQUE client tools on on the Galaxy server, and can spawn an interactive job with qsub -I, as well as check the status of queued jobs using qstat (from the Galaxy server). This suggests to me that there a potential problem with the PBS Egg, although I am not certain. Has anybody seen something like this before, or could somebody point me in the right direction? We do have a support contract with Adaptive Computing, and I am opening a ticket with them as well, however I wanted to reach out to the Galaxy community to cover all of my bases. Thank-you so much for taking the time to read my email. Dan Sullivan ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] PBS Server Throwing Errors
I've been told by Galaxy folks to keep this on galaxy-dev. My apologies for any confusion. -Scott - Original Message - Hi Dan- Thanks again for your great hospitality at UCI! It looks like you've done most of the sane things, and a quick check looks like the PBS egg is requesting protocol version 1 while the server supports protocol version 2. One possibility is that there is a protocol mismatch, which could be the result of using an old library. We can check if the egg is at fault first - try the following link for compiling the pbs_python.py egg yourself and try the example to see if the connection and a simple stats-gathering operation (the examples/pbsnodes-a.py script from pbs_python) works: https://subtrac.sara.nl/oss/pbs_python/wiki/TorqueInstallation -Scott - Original Message - Hi, Galaxy Community, Greetings from The University of Chicago; I hope all who attended the Galaxy conference enjoyed it as much as I did. I have searched the mailing list archives as well as Google to a resolve problem I am seeing, however I am somewhat at a loss as to the next course of action I should be taking to bring this issue to a close. I am hoping that one of the bright minds on this mailing list could help me shed some light on the solution to my problem, or at least help me identify a root cause. I have configured Galaxy to integrate with TORQUE (version 4.0.2) server, and successfully built the PBS python egg as specified in the Galaxy documentation. I am using Python version 2.6 and the latest build of Galaxy. Whenever I launch a job from the Galaxy UI, I get the following error message(s) on the PBS server: 07/30/2012 15:42:48;0080;PBS_Server;Req;dis_request_read;conflicting version numbers, 1 detected, 2 expected 07/30/2012 15:42:48;0080;PBS_Server;Req;req_reject;Reject reply code=15058(Bad DIS based Request Protocol MSG=cannot decode message), aux=0, type=AlternateUserAuthentication, from galaxy@ 07/30/2012 15:42:48;0080;PBS_Server;Req;dis_request_read;conflicting version numbers, 1 detected, 2 expected 07/30/2012 15:42:48;0080;PBS_Server;Req;req_reject;Reject reply code=15058(Bad DIS based Request Protocol MSG=cannot decode message), aux=0, type=QueueJob, from galaxy@ 07/30/2012 15:42:48;0080;PBS_Server;Req;dis_request_read;conflicting version numbers, 1 detected, 2 expected 07/30/2012 15:42:48;0080;PBS_Server;Req;req_reject;Reject reply code=15058(Bad DIS based Request Protocol MSG=cannot decode message), aux=0, type=Disconnect, from galaxy@ 07/30/2012 15:43:01;0002;PBS_Server;Svr;PBS_Server;Torque Server Version = 4.0.2, loglevel = 1 One thing I did notice, that suggests there might be a problem, is that there is no hostname after the galaxy@; most of the other messages in this log file have a host name appended to log entry, i.e.: 07/30/2012 15:43:38;0100;PBS_Server;Req;;Type StatusJob request received from root@sc01, sock=10 I have completed a tcpdump on the schedule node, and I can definitely see bi-directional traffic between the Galaxy server and the scheduler node on TCP port 15001. In addition to this, I have installed the TORQUE client tools on on the Galaxy server, and can spawn an interactive job with qsub -I, as well as check the status of queued jobs using qstat (from the Galaxy server). This suggests to me that there a potential problem with the PBS Egg, although I am not certain. Has anybody seen something like this before, or could somebody point me in the right direction? We do have a support contract with Adaptive Computing, and I am opening a ticket with them as well, however I wanted to reach out to the Galaxy community to cover all of my bases. Thank-you so much for taking the time to read my email. Dan Sullivan ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] egg distribution error when running galaxy-central
I haven't been able to reproduce this yet with the instructions you
gave, but I'm not using the same environment. Can you give me an idea
of what tools you're using outside of SciPy/NumPy/Enthought stuff?
There is the possibility that the virtualenv.py script isn't being
sourced correctly. We can check if it's actually using the correct
environment by calling echo $PATH and checking that the path is
pointing to the virtual environment. For example, I installed
virtualenv stuff under /home/smcmanus/clare/galaxy_env/bin, and
I got:
(galaxy_env)$ echo $PATH
/home/smcmanus/clare/galaxy_env/bin:/usr/local/bin:other stuff deleted
-Scott
- Original Message -
Hi all,
I'm trying to run galaxy-central on my laptop in order to play around
with some changes, and I'm having trouble getting it to run. I can
run
galaxy-dist without problems and have been working with that (so its
eggs are all installed already), but now I want to create a pull
request so want to run galaxy-dist. I'm not trying to install any
extra tools or data, just the code.
I'm running on OSX 10.7.4 and using virtualenv. I have Enthought
installed, and I assume I will be using its version of python by
default. The default python seems to be 2.7.3.
I'm using the same virtualenv environment for galaxy-dist and
galaxy-central (though it doesn't seem to matter if I give
galaxy-central its own environment, I see the same error). So the
steps were:
- create a virtualenv environment and activate it
- get galaxy-dist and call run.sh - it asked me to build quite a lot
of dependencies myself, which was just a matter of running the
requested commands, and then it worked with no problems.
- shut down galaxy-dist, and in another directory, get galaxy-central
and call run.sh. I think it asked me to build a couple of
dependencies, but then it gives up with the following:
(galaxy_env)Clares-MacBook-Pro:galaxy-central clare$ sh run.sh
--reload
Some eggs are out of date, attempting to fetch...
Warning: MarkupSafe (a dependent egg of Mako) cannot be fetched
Warning: pycrypto (a dependent egg of Fabric) cannot be fetched
Warning: simplejson (a dependent egg of WebHelpers) cannot be fetched
Fetched http://eggs.g2.bx.psu.edu/ssh/ssh-1.7.14-py2.7.egg
One of Galaxy's managed eggs depends on something which is missing,
this is almost certainly a bug in the egg distribution.
Dependency ssh requires pycrypto=2.1,!=2.4
Traceback (most recent call last):
File ./scripts/fetch_eggs.py, line 30, in module
c.resolve() # Only fetch eggs required by the config
File
/Users/clare/galaxy/galaxy-central/lib/galaxy/eggs/__init__.py,
line 345, in resolve
egg.resolve()
File
/Users/clare/galaxy/galaxy-central/lib/galaxy/eggs/__init__.py,
line 168, in resolve
dists = pkg_resources.working_set.resolve( (
self.distribution.as_requirement(), ), env, self.fetch )
File
/Users/clare/galaxy/galaxy_env/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg/pkg_resources.py,
line 569, in resolve
raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (ssh 1.7.14
(/Users/clare/galaxy/galaxy-central/eggs/ssh-1.7.14-py2.7.egg),
Requirement.parse('pycrypto=2.1,!=2.4'))
Fetch failed.
Any idea what is causing this?
Thanks,
Clare
--
Clare Sloggett
Research Fellow / Bioinformatician
Life Sciences Computation Centre
Victorian Life Sciences Computation Initiative
University of Melbourne, Parkville Campus
187 Grattan Street, Carlton, Melbourne
Victoria 3010, Australia
Ph: 03 903 53357 M: 0414 854 759
___
Please keep all replies on the list by using reply all
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
___
Please keep all replies on the list by using reply all
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
Re: [galaxy-dev] [galaxy-user] Fwd: Local instance and storage space to provide
Sorry - I fouled up and should have kept this on galaxy-dev. -Scott - Original Message - I'm forwarding this to galaxy-user instead of galaxy-dev. -Scott - Forwarded Message - From: Scott McManus scottmcma...@gatech.edu To: Sarah Maman sarah.ma...@toulouse.inra.fr Cc: galaxy-dev@lists.bx.psu.edu Sent: Wednesday, August 1, 2012 4:18:29 PM Subject: Re: [galaxy-dev] Local instance and storage space to provide Hi Sarah- I'm sure others have experiences that could help, so I hope they will chime in. Nate put together some slides two years ago on production setups, including some architecture for the server main.g2.bx.psu.edu: http://wiki.g2.bx.psu.edu/Events/GDC2010?action=AttachFiledo=gettarget=GDC2010_building_scalable.pdf There is also a wiki page describing production environments: http://wiki.g2.bx.psu.edu/Admin/Config/Performance/Production%20Server Again, I'm sure others have had different experiences with both more and less hardware on hand. Of course your mileage may vary based on the tools being used (which in your case I'm guessing is Tophat), the number of datasets that will need to be analyzed, and so on. I hope that helps! -Scott - Original Message - Dear all, To purchase equipment related to a local instance of Galaxy, I would like to have your feedback. Did you notice load problems when 10 to 20 users launch jobs at the same time and on a single instance of Galaxy, with mi-RNA or RNA seq data ? What do you recommend in terms of storage space, number of nodes, number of instances? Thank you in advance, Sarah Maman ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using reply all in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list: http://lists.bx.psu.edu/listinfo/galaxy-dev To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
