- galaxy-dev - lists.galaxyproject.org

The need for wrappers
by Timothy Wu 14 Oct '11

14 Oct '11

Hi, Looking under the tools directory I realized that some tools comes with *_wrapper.py. I wonder under what circumstances is this needed? I'm trying to do a quickie for RepeatMasker. It looks to me like the tool does not allow one to specify the name of the output files. It also appears to me that tools should have an $output variable specifies within the <command> tag. So I was wondering if this is one case where a wrapper.py is needed. Thanks. Timothy

3 2

Re: [galaxy-dev] Accept-Ranges: bytes for
by Kip Bodi 14 Oct '11

14 Oct '11

Perhaps this is a distribution issue. For those who have gotten the "Display at UCSC" link to work on a local server or workstation, what linux distribution and version did you use? Has anyone used this successfully with Red Hat Enterprise Linux 6.1? Best, -Kip On Fri, Oct 7, 2011 at 6:28 PM, Bodi, Kip <Kip.Bodi(a)tufts.edu> wrote: > Hi all, > > I have a local galaxy instance, proxied by Apache, and am trying to get the > 'display at UCSC' link to work. I've followed all of the instructions and am > nearly there, but now I'm getting this response from UCSC when it tries to > load the track: > > "Byte-range request was ignored by server. Expected Partial Content 206." > etc. > > I think the error is because the PasteWSGIServer isn't allowing byte-range > requests. When I look at the header, "Accept-Ranges: bytes" is not present: > [galaxy@galaxy galaxy_dist]$ curl --head localhost > HTTP/1.1 200 OK > Date: Fri, 07 Oct 2011 22:23:49 GMT > Server: PasteWSGIServer/0.5 Python/2.6.6 > content-type: text/html; charset=UTF-8 > Set-Cookie: > galaxysession=c6ca0ddb55be603a4e98b4f13a4db8bfb8635f0aa576697114d40b13a8355efe2cf7a075ef81d769; > expires=Thu, 05-Jan-2012 17:23:49 GMT; Max-Age=7776000; Path=/; Version=1 > Vary: Accept-Encoding > Connection: close > > Whereas on another server, "Accept-Ranges: bytes" appears in the header: > [galaxy@galaxy galaxy_dist]$ curl --head apollo.med.tufts.edu< > http://apollo.med.tufts.edu> > HTTP/1.1 403 Forbidden > Date: Fri, 07 Oct 2011 22:22:42 GMT > Server: Apache/2.2.21 (Fedora) > Accept-Ranges: bytes > Content-Length: 4609 > Connection: close > Content-Type: text/html; charset=UTF-8 > > I'm running RHEL6 with the latest version of galaxy-dist. I've tried > manually enabling 'accept-ranges' but haven't had any luck. Any suggestions? > Can I enable it somehow in universe_wsgi.ini? > > Best, > > -Kip > -- Kip Lord Bodi Jr. Tufts University School of Medicine 136 Harrison Avenue, South Cove 502 Boston, MA 02118 617-636-3763 kip.bodi(a)tufts.edu www.tucf.org | genomics.med.tufts.edu

2 1

Re: [galaxy-dev] Some changes to tophat and cufflinks wrappers for indexing loc files
by Chorny, Ilya 13 Oct '11

13 Oct '11

I made some changes to the cufflinks and tophat wrapper to pull gtf files from an indexed loc file as opposed to from history. The diff's are attached. I made it an optional feature. Please let me know if this makes its way into galaxy-central. Best, Ilya Ilya Chorny Ph.D. Bioinformatics Scientist I Illumina, Inc. 9885 Towne Centre Drive San Diego, CA 92121 Work: 858.202.4582 Email: ichorny(a)illumina.com<mailto:ichorny@illumina.com> Website: www.illumina.com<http://www.illumina.com>

2 4

samtools mpileup update
by David Hoover 13 Oct '11

13 Oct '11

Is there any good reason why Galaxy can't use a more recent version of samtools? The only difference I can see is the mpileup command. The algorithm by which mpileup finds SNPs is a little different. Does anyone know if the file format has changed? The only files that need to change are sam_pileup.py and sam_pileup.xml. David Hoover Helix Systems Staff http://helix.nih.gov

4 3

Re: [galaxy-dev] Possible to browse local filesystem
by Greg Von Kuster 13 Oct '11

13 Oct '11

Allesandro, Are your users making the correct selection in the Copy data into Galaxy? select list? If they choose "Link to files without copying into Galaxy" as shown below, you should see the behavior you want. The default selection is "Copy files into Galaxy", so if they leave the default selection, copies of the files will be made. On Oct 12, 2011, at 12:10 PM, alessandro albiero wrote: > Dear Greg, > > thank you for your answer. I followed the wiki but I did not solve my problem. > I setted these parameters on the universe_wsgi.ini: > > user_library_import_dir = /u/galaxy/userimport > > Then I created the /u/galaxy/userimport directory with a series of sub-dirs named as the login users. > I done this to allow our user to load into galaxy their files. In this case every user put its data in its dir on /u/galaxy/userimport (or using symlinks) and then load them on galaxy. > > My problem is that galaxy duplicate the files; for example: > > 1) User "A" place a file "FILE1" on its dir and it load the dir on galaxy. On galaxy he sees "FILE1" > 2) The user "A" place another file in its dir ("FILE2") and re-load the dir on galaxy. On galaxy he sees "FILE1", "FILE1", "FILE2" > > It seems that galaxy re-loads all the files of the user dir without checking the duplications. > We would like to avoid this duplications. > > We found that removing the old files from the user directory solves the problem. Is there a simpler way to do this (without removing the files) ? > > > All the best > > Alessandro > > > > 2011/10/11 Greg Von Kuster <greg(a)bx.psu.edu> > Hello Alessandro, > > You can upload files from filesystem paths to a Galaxy data library without copying the files into Galaxy's configured file directory. This approach should provide what you're looking to do. See our wiki at http://wiki.g2.bx.psu.edu/Admin/Data%20Libraries/Uploading%20Library%20Files for all of the details. > > Greg Von Kuster > > On Oct 11, 2011, at 6:45 AM, alessandro albiero wrote: > >> Dear all, >> >> I have a problem with galaxy and I have already tried to write on ther user list.... >> My problem concern the upload on galaxy of new files. >> >> We are setting up a galaxy istance on our server (HPC Cluster with torque and PBS) for internal use. >> Our problem is that we manage only NGS data (SOLiD and Illumina Data) that are already stored on the server. >> We tried to set up the user directory in the universe_wgsi.ini file to allow to any user tu upload their local files, but adding new file and re-uploading the dir we found duplicated files (it seems that galaxy re-upload every time all the files ignoring if some are already present). This method is OK for us but how can we avoid the file duplications ? >> >> In a presentation found on web (blankenberg_pittsburg_2001), we saw that there is the possibility to automatically upload the sequenced reads on Galaxy (and let them available to all our user). Where can we find information for doing this ? >> >> >> Thank in advance >> >> All the best >> >> Alessandro >> >> >> >> >> -- >> ****************************** >> Alessandro Albiero >> Bioinformatics Lab >> CRIBI-Padua University >> Viale G. Colombo, 3 >> 35121 Padova-Italy >> >> http://genomics.cribi.unipd.it >> http://genomics.cribi.unipd.it/index.php/User:Albiero >> Phone. +39. 049 827-6165 >> Fax. +39. 049 827-6159 >> ******************************** >> >> >> ___________________________________________________________ >> 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/ > > Greg Von Kuster > Galaxy Development Team > greg(a)bx.psu.edu > > > > Greg Von Kuster Galaxy Development Team greg(a)bx.psu.edu

1 0

Trasfering Galaxy workflows to other instances
by Chorny, Ilya 13 Oct '11

13 Oct '11

Is there a way of uploading workflows by saving the workflow to a file and copying the workflow files to a directory or editing a database file to point to them. When external authentication is invoked linking to workflows does not seem to work and copy and pasting from a file is very tedious. Thanks, Ilya Ilya Chorny Ph.D. Bioinformatics Scientist I Illumina, Inc. 9885 Towne Centre Drive San Diego, CA 92121 Work: 858.202.4582 Email: ichorny(a)illumina.com<mailto:ichorny@illumina.com> Website: www.illumina.com<http://www.illumina.com>

2 1

Specifying data types for workflow inputs
by Ann Black 13 Oct '11

13 Oct '11

I am developing a custom workflow in galaxy. I have 4 input files that need to be fed into various steps of the workflow. I would like to be able to specify a data type for the inputs such that the pre-populated drop downs are filtered to datasets of the appropriate type as well as being able to do some simple validation before the workflow begins. Is there someway to do this? Thanks much, Ann

2 3

strange history error
by Chorny, Ilya 13 Oct '11

13 Oct '11

I am getting a strange error that I cannot figure out how to debug. It's from a second instance we have running on the same server. When I upload data it does not show me my history. I get the following messages from the log file. Thoughts? galaxy.web.framework DEBUG 2011-10-11 15:47:50,259 Error: this request returned None from get_history(): http://ussd-dev-swim02.illumina.com/galaxy2/history/list galaxy.web.framework DEBUG 2011-10-11 15:47:50,261 Error: this request returned None from get_history(): http://ussd-dev-swim02.illumina.com/galaxy2/history/list galaxy.web.framework DEBUG 2011-10-11 16:34:25,717 Error: this request returned None from get_his tory(): http://ussd-dev-swim02.illumina.com/galaxy2/tool_runner/upload_async_create galaxy.web.framework DEBUG 2011-10-11 16:34:25,717 Error: this request returned None from get_his tory(): http://ussd-dev-swim02.illumina.com/galaxy2/tool_runner/upload_async_create galaxy.web.framework DEBUG 2011-10-11 16:34:25,718 Error: this request returned None from get_his tory(): http://ussd-dev-swim02.illumina.com/galaxy2/tool_runner/upload_async_create galaxy.web.framework DEBUG 2011-10-11 16:34:25,718 Error: this request returned None from get_his tory(): http://ussd-dev-swim02.illumina.com/galaxy2/tool_runner/upload_async_create galaxy.web.framework DEBUG 2011-10-11 16:34:25,718 Error: this request returned None from get_his tory(): http://ussd-dev-swim02.illumina.com/galaxy2/tool_runner/upload_async_create galaxy.web.framework DEBUG 2011-10-11 16:34:25,718 Error: this request returned None from get_his tory(): http://ussd-dev-swim02.illumina.com/galaxy2/tool_runner/upload_async_create galaxy.web.framework DEBUG 2011-10-11 16:34:25,719 Error: this request returned None from get_his tory(): http://ussd-dev-swim02.illumina.com/galaxy2/tool_runner/upload_async_create galaxy.web.framework DEBUG 2011-10-11 16:34:25,719 Error: this request returned None from get_his tory(): http://ussd-dev-swim02.illumina.com/galaxy2/tool_runner/upload_async_create Ilya Chorny Ph.D. Bioinformatics Scientist I Illumina, Inc. 9885 Towne Centre Drive San Diego, CA 92121 Work: 858.202.4582 Email: ichorny(a)illumina.com<mailto:ichorny@illumina.com> Website: www.illumina.com<http://www.illumina.com>

2 2

hardware for local galaxy install
by Jeremy Goecks 13 Oct '11

13 Oct '11

David, Please direct questions about local installations to the galaxy-dev mailing list (cc'd); there are a large number of experienced people of this list that can likely help with this and similar questions. > Just a quick question about the compute infrastructure of the setup running the public instance of Galaxy. Our Galaxy copy is on our High Performance Cluster here at X and they are currently canvassing users about the next upgrade of the HPC. This cluster serves the needs of all the university academics here and so we are sharing time with physicists, aerodynamics engineers etc. However, the HPC board of directors tell me that they see biological computing problems as the next big growth area for them - especially now we have a copy of Galaxy. What they would like to know is what kind of mix of new nodes would be most useful to us. They have about X million pounds to spend (about X million dollars) and the question as I understand it is determining the right mix of expensive high memory nodes (e.g. with 1 or 2TB RAM on board) and cheaper lower memory nodes (e.g. with 32G ram on board or less even). The problem for me is that I have no idea what to suggest (I am not that compute savvy). So any advice from your experiences (or that of the Galaxy team) would be most helpful. Your hardware will depend on what types of analyses you plan to support/run. For instance, assembly jobs (e.g. ABySS, Velvet, Trinity) require high-memory nodes, and read mapping jobs (e.g. BWA, Bowtie, Tophat) are best run on high CPU nodes. Also, creating indices (often used in visualization) such as bigWig and bigBed require large amounts of memory as well. You'll want to do some research on the tools that you plan to run most often and determine the best hardware for them. Nate Coraor's presentation at GCC 2011 has some useful information about setting up a production Galaxy as well as details about our public instance: http://wiki.g2.bx.psu.edu/Events/GCC2011 In short, we use multiple clusters to distribute resource-intensive jobs appropriately. Also, you may want to search the galaxy-dev mailing list as there's been discussion about hardware specs for a Galaxy instance previously: http://gmod.827538.n3.nabble.com/Galaxy-Development-f815885.html Nate and others, please feel free to chime in with additional information. Good luck, J.

2 1

scatterplot broken
by David Hoover 13 Oct '11

13 Oct '11

Hi, The scatterplot tool is broken in the distributed version. It works on the main Galaxy server, but on our local installation it gives this error: An error occurred running this job:Warning messages: 1: In min(x) : no non-missing arguments to min; returning Inf 2: In max(x) : no non-missing arguments to max; returning -Inf 3: In min(x) : no non-missing arguments to min; returning Inf 4: In max(x) : no non-missing arguments to max; re Any ideas? David Hoover Helix Systems Staff SCB/CIT/NIH

1 1