- galaxy-dev - lists.galaxyproject.org

determination of errors
by David Hoover 23 Oct '12

23 Oct '12

How does Galaxy determine that a job has failed? Does it simply see if the STDERR is empty? What happens if an application normally outputs to STDERR? This is a problem for our local installation, as I have enabled it to run as the local user on the backend cluster. If a user has an error in the .bashrc file, it will automatically write to STDERR, and all jobs, no matter what, are labelled as failing. David Hoover Helix Systems Staff

4 3

UCSC Data Browser Not Working in Recent Release
by Robert Chase 22 Oct '12

22 Oct '12

Hello, I'm having some difficulty troubleshooting an error that one of our users found. When we select UCSC from Get Data We get a screen saying to "submit query to galaxy" but there are no other options and there is no connection to the UCSC website. Is this something other users have experienced? Is this the expected behaviour? -Rob

1 0

Output from Barcode splitter
by Philipe Moncuquet 22 Oct '12

22 Oct '12

Hi, I am trying to use the Barcode splitter tool as part of a workflow, I am not happy with the html output produce by this tool and would like to have access to fasta files. Any suggestions on how I can modify the tool so that it produces fasta outputs that would appear in the workflow ? Thanks Philippe

2 1

Corner case in task splitter - merging zero files
by Peter Cock 22 Oct '12

22 Oct '12

Hi Scott, Following some failing hard drives, I'm rebuilding our Galaxy server. Something isn't quite right with our cluster integration yet, but it has exposed a problem in Galaxy's handling of task splitting - it can sometimes attempt to merge zero files. Here is my fix for the BLAST XML format (now in the ToolShed), https://bitbucket.org/peterjc/galaxy-central/changeset/5cb6411bad19802ba400… Here's an example using the text format: galaxy.jobs.splitters.multi ERROR 2012-10-18 16:26:21,330 Error merging files Traceback (most recent call last): File "/mnt/galaxy/galaxy-central/lib/galaxy/jobs/splitters/multi.py", line 133, in do_merge output_type.merge(output_files, output_file_name) File "/mnt/galaxy/galaxy-central/lib/galaxy/datatypes/data.py", line 545, in merge raise Exception('Result %s from %s' % (result, cmd)) Exception: Result 2 from cat > /mnt/galaxy/galaxy-central/database/files/000/dataset_304.dat The problem obviously is that while "cat file1 ... fileN > merged" will work fine for one or more files, with no files it sits waiting for stdin (and from a user perspective stalls). This logic error is in lib/galaxy/datatypes/data.py method merge, which could either treat zero files as an error, or a no-op: if len(split_files) == 1: cmd = 'mv -f %s %s' % ( split_files[0], output_file ) else: cmd = 'cat %s > %s' % ( ' '.join(split_files), output_file ) result = os.system(cmd) I think this should be something like this: if not split_files: raise Exception('Asked to merge zero files') elif len(split_files) == 1: cmd = 'mv -f %s %s' % ( split_files[0], output_file ) else: cmd = 'cat %s > %s' % ( ' '.join(split_files), output_file ) result = os.system(cmd) It might also make sense to check for zero files in the code which calls the merge, i.e. lib/galaxy/jobs/splitters/multi.py function do_merge I'm still investigating upstream how this comes about, one clue: galaxy.jobs.runners.drmaa DEBUG 2012-10-18 16:25:01,930 (273/510) state change: job is running galaxy.jobs.runners.drmaa DEBUG 2012-10-18 16:25:03,040 (273/510) state change: job finished, but failed galaxy.jobs.runners.drmaa DEBUG 2012-10-18 16:25:03,074 Job output not returned from cluster galaxy.jobs DEBUG 2012-10-18 16:25:03,074 task 641 for job 273 ended; exit code: 0 galaxy.jobs DEBUG 2012-10-18 16:25:03,148 task 641 ended galaxy.jobs.runners.tasks DEBUG 2012-10-18 16:25:05,169 execution finished - beginning merge: tblastx -query "/mnt/galaxy/galaxy-central/database/files/000/dataset_127.dat" -db "/var/local/blast/ncbi/nt" -query_gencode 2 -evalue 0.001 -out /mnt/galaxy/galaxy-central/database/files/000/dataset_304.dat -outfmt 0 -num_threads 8 galaxy.jobs.splitters.multi DEBUG 2012-10-18 16:25:05,181 files [] If you would prefer that small suggestion as a pull request, let me know. Regards, Peter

2 5

How to report issues (link on the website requires Galaxy team membership)
by David van Enckevort 22 Oct '12

22 Oct '12

Hi, On the main galaxy page there is a link 'Report Issue' to the bitbucket issue tracker, however since a few weeks it is not possible to view or report issues anymore since it requires membership of the project. This raises two questions: 1. How should issues be reported? 2. How can we see which issues have been reported by others, and most importantly, whether they have been addressed by the Galaxy Team. I think it is very important for any group that maintains a Galaxy instance to have insight in the known issues and fixes, and I hope this information is still available somewhere. With kind regards, -- David van Enckevort Project Leader biobanking taskforce Software Integration Engineer BioAssist mob: +31 6 543 32 276 E-mail: david.van.enckevort(a)nbic.nl (mailto:david.van.enckevort@nbic.nl) Skype: enckevort76 Netherlands Bioinformatics Centre Postal address: 260 NBIC P.O. Box 9101 6500 HB Nijmegen tel: +31 24 36 19 500 fax: +31 24 89 01 798

3 2

Galaxy Tool Loading
by John Chilton 22 Oct '12

22 Oct '12

Hey Greg & Galaxy Team, Galaxy doesn't load tool sections from multiple files in a consistent manner. This is a minimal example that demonstrates the problem: https://bitbucket.org/jmchilton/galaxy-central-tool-load-example https://bitbucket.org/jmchilton/galaxy-central-tool-load-example/compare This example specifies two sections, Section 1 and Section 2. The first time you load up Galaxy, Section 1 appears first followed by Section 2. On every subsequent time Galaxy is loaded, Section 2 appears first followed by Section 1. I have attached the smallest patch I could come up with to fix this problem. While I was in that file, I noticed that a standing request I had the defunct bug tracker to allow directories to appear in the tool_config_file option is easy to implement, so I have attached a patch for that as well if you are so inclined. Thanks for your time, -John ------------------------------------------------ John Chilton Senior Software Developer University of Minnesota Supercomputing Institute Office: 612-625-0917 Cell: 612-226-9223 Bitbucket: https://bitbucket.org/jmchilton Github: https://github.com/jmchilton Web: http://jmchilton.net

2 1

Re: [galaxy-dev] pass more information on a dataset merge
by Alex.Khassapov＠csiro.au 22 Oct '12

22 Oct '12

1) One more question, My colleague likes the idea, but his composite data set dataset_id.dat file contains only a plain list of uploaded files, not HTML like yours. I was wondering if it is possible to pass somehow a parameter to CompositeMultifile.regenerate_primary_file(dataset) to switch between HTML and plain list formats. I mean add a 'hidden' parameter in toll.xml file, but I'm not sure how to get these tool parameters in Galaxy source? 2) And one more question, I use your "m:xxx" format for the tool output, all files are generated in the dataset_id_files folder, but the dataset_id.dat file is empty. To force creation of the dataset.id file I use the exec_after_process hook (<code file="xxxx.py"/> tag): for key,val in out_data.items(): try: if not hasattr(val.dataset, "name"): val.dataset.name = val.dataset.file_name val.datatype.regenerate_primary_file(val.dataset) except Exception as e: print "######## ERROR: " + str(e) But it doesn't feel right, I wonder what is the proper way to use "m:xxx" format for the output? -Alex -----Original Message----- From: jmchilton(a)gmail.com [mailto:jmchilton@gmail.com] On Behalf Of John Chilton Sent: Saturday, 20 October 2012 1:40 AM To: Khassapov, Alex (CSIRO IM&T, Clayton) Subject: Re: [galaxy-dev] pass more information on a dataset merge Hey Alex, I think the idea here is that your initially uploaded files would have different names, but after Jorrit's tool split/merge step they will all just be named after the dataset id (see screenshot) so you need the task_X at the end so they don't all just have the same name. I have not thought a whole lot about the naming thing, in general it seems like a tough problem and one that Galaxy itself doesn't do a particularly good job at. Jorrit have you given any thought to this? I wonder if it would be feasible to use the initial uploaded name as a sort of prefix going forward. So if I upload say fraction1.RAW fraction2.RAW fraction3.RAW and run a conversion step, maybe I could get: fraction1_dataset567.ms2 fraction2_dataset567.ms2 fraction3_dataset567.ms2 instead of dataset567.dat_task_0 dataset567.dat_task_1 dataset567.dat_task_2 Jorrit do you mind if I give implementing that a shot? It seems like it would be a win to me. Am I am going to hit some problem I don't see now (presumable we have to send some data from the split to the merge and that might be tricky)? -John On Thu, Oct 18, 2012 at 7:00 PM, <Alex.Khassapov(a)csiro.au> wrote: > Thanks John, > > I wonder what's the reason for appending _task_XX to the file names, why can't we just keep original file names? > > Alex > > -----Original Message----- > From: jmchilton(a)gmail.com [mailto:jmchilton@gmail.com] On Behalf Of > John Chilton > Sent: Friday, 19 October 2012 6:16 AM > To: Khassapov, Alex (CSIRO IM&T, Clayton) > Subject: Re: [galaxy-dev] pass more information on a dataset merge > > On Tue, Oct 16, 2012 at 11:11 PM, <Alex.Khassapov(a)csiro.au> wrote: >> Hi John, >> >> I am definitely interested in this idea, not only me - we are currently working on moving a few scientific tools (not related to genome) into cloud using Galaxy. > > Great. My interests in Galaxy are mostly outside of genomics as well, it is good to have more people utilizing Galaxy in this way because it will force the platform to become more generic and address more broader use cases. > >> >> We will try it further and see if we need any changes. For now one improvement would be nice, make dataset_id.dat contain list of paths to the location of the uploaded files, so by displaying html page the user could just click on the link and download the file. >> > > Code that attempted to do this was in there, but didn't work obviously. I have now fixed it up. > > Thanks for beta testing. > > -John > >> We are pretty new to Galaxy, so our understanding of Galaxy is pretty limited. >> >> Thanks again, >> >> Alex >> >> >> -----Original Message----- >> From: jmchilton(a)gmail.com [mailto:jmchilton@gmail.com] On Behalf Of >> John Chilton >> Sent: Wednesday, 17 October 2012 3:21 AM >> To: Khassapov, Alex (CSIRO IM&T, Clayton) >> Subject: Re: [galaxy-dev] pass more information on a dataset merge >> >> Wow, thanks for the rapid feedback! I have made the changes you have suggested. It seems you must be interested in this idea/implementation. Let me know if you have specific use cases/requirements in mind and/or if you would be interested in write access to the repository. >> >> -John >> >> On Mon, Oct 15, 2012 at 11:51 PM, <Alex.Khassapov(a)csiro.au> wrote: >>> Hi John, >>> >>> I tried your galaxy-central-homogeneous-composite-datatypes implementation, works great thank you (and Jorrit). >>> >>> A couple of fixes: >>> >>> 1. Add multi_upload.xml to too_conf.xml 2. >>> lib/galaxy/tools/parameters/grouping.py line 322 (in get_filenames( context )) - >>> "if ftp_files is not None:" >>> Remove "is not None" as ftp_files is empty [], but not None, then line 331 "user_ftp_dir = os.path.join( trans.app.config.ftp_upload_dir, trans.user.email )" throws an exeption if ftp_upload_dir isn't set. >>> >>> Alex >>> >>> -----Original Message----- >>> From: galaxy-dev-bounces(a)lists.bx.psu.edu >>> [mailto:galaxy-dev-bounces@lists.bx.psu.edu] On Behalf Of John >>> Chilton >>> Sent: Tuesday, 16 October 2012 1:07 AM >>> To: Jorrit Boekel >>> Cc: galaxy-dev(a)lists.bx.psu.edu >>> Subject: Re: [galaxy-dev] pass more information on a dataset merge >>> >>> Here is an implementation of the implicit multi-file composite datatypes piece of that idea. I think the implicit parallelism may be harder. >>> >>> https://bitbucket.org/galaxyp/galaxy-central-homogeneous-composite-d >>> a >>> t >>> atypes/compare >>> >>> Jorrit do you have any objection to me trying to get this included in galaxy-central (this is 95% code I stole from you)? I made the changes against a clean galaxy-central fork and included nothing proteomics specific in anticipation of trying to do that. I have talked with Jim Johnson about the idea and he believes it would be useful his mothur metagenomics tools, so the idea is valuable outside of proteomics. >>> >>> Galaxy team, would you be okay with including this and if so is there anything you would like to see either at a high level or at the level of the actual implementation. >>> >>> -John >>> >>> ------------------------------------------------ >>> John Chilton >>> Senior Software Developer >>> University of Minnesota Supercomputing Institute >>> Office: 612-625-0917 >>> Cell: 612-226-9223 >>> Bitbucket: https://bitbucket.org/jmchilton >>> Github: https://github.com/jmchilton >>> Web: http://jmchilton.net >>> >>> On Mon, Oct 8, 2012 at 9:24 AM, John Chilton <chilton(a)msi.umn.edu> wrote: >>>> Jim Johnson and I have been discussing that approach to handling >>>> fractionated proteomics samples as well (composite datatypes, not >>>> the specifics of the interface for parallelizing). >>>> >>>> My perspective has been that Galaxy should be augmented with better >>>> native mechanisms for grouping objects in histories, operating over >>>> those groups, building workflows that involve arbitrary numbers of >>>> inputs, etc... Composite data types are kindof a kludge, I think >>>> they are more useful for grouping HTML files together when you >>>> don't care about operating on the constituent parts you just want >>>> to view pages a as a report or something. With this proteomic data >>>> we are working with, the individual pieces are really interesting right? >>>> You want to operate on the individual pieces with the full array of >>>> tools (not just these special tools that have the logic for dealing >>>> with the composite datatypes), you want to visualize the files, >>>> etc... Putting these component pieces in the composite data type >>>> extra_files path really limits what you can do with the pieces in Galaxy. >>>> >>>> I have a vague idea of something that I think could bridge some of >>>> the gaps between the approaches (though I have no clue on the >>>> feasibility). Looking through your implementation on bitbucket it >>>> looks like you are defining your core datatypes (MS2, CruxSequest) >>>> as subclasses of this composite data type (CompositeMultifile). My >>>> recommendation would be to try to define plain datatypes for these >>>> core datatype (MS2, CruxSequest) and then have the separate >>>> composite datatype sort of delegate to the plain datatypes. >>>> >>>> You could then continue to explicitly declare subclasses of the >>>> composite datatype (maybe MS2Set, CruxSequestSet), but also maybe >>>> augement the tool xml so you can do implicit data type instances >>>> the way you can with tabular data for instance (instead of defining >>>> columns you would define the datatype to delegate to). >>>> >>>> The next step would be to make the parallelism implicit (i.e pull >>>> it out of the tool wrapper). Your tool wrappers wouldn't reference >>>> the composite datatypes, they would reference the simple datatypes, >>>> but you could add a little icon next to any input that let you >>>> replace a single input with a composite input for that type. It >>>> would be kind of like the run workflow page where you can replace >>>> an input with a multiple inputs. If a composite input (or inputs) >>>> are selected the tool would then produce composite outputs. >>>> >>>> For the steps that actually combine multiple inputs, I think in >>>> your case this is perculator maybe (a tool like interprophet or >>>> Scaffold that merges peptide probabilities across runs and groups >>>> proteins), then you could have the same sort of implicit >>>> replacement but instead of for single inputs it could do that for >>>> multi-inputs (assuming the Galaxy powers that be accept my fixes for multi-input tool parameters: >>>> https://bitbucket.org/galaxy/galaxy-central/pull-request/76/multi-input-dat…) >>>> >>>> The upshot of all of that would be that then even if these >>>> composites datatypes aren't used widely, other people could still >>>> use your proteomics tools (my users are definitely interested in >>>> Crux for >>>> instance) and you could then use other developers' proteomic tools >>>> with your composite datatypes even though they weren't designed >>>> with that use case in mind (I have msconvert, myrimatch, idpicker, >>>> proteinpilot, Ira Cooke has X! Tandem, OMSSA, TPP, and NBIC has an >>>> entire suite of label free quant tools). A third benefit would be >>>> that people working in other -omicses could make use of the >>>> homogenous composite datatype implementation without needing to >>>> rewrite their wrappers and datatypes. >>>> >>>> There is probably something that I am missing that makes this very >>>> difficult, let me know if you think this is a good idea and what >>>> its feasibility might be. I forked your repo and set off to try to >>>> implement some of this stuff last week and I ended up with my >>>> galaxy pull requests to improve batching workflows and multi-input >>>> tool parameters instead, but I hope to eventually get around to it. >>>> >>>> -John >>>> >>>> ------------------------------------------------ >>>> John Chilton >>>> Senior Software Developer >>>> University of Minnesota Supercomputing Institute >>>> Office: 612-625-0917 >>>> Cell: 612-226-9223 >>>> Bitbucket: https://bitbucket.org/jmchilton >>>> Github: https://github.com/jmchilton >>>> Web: http://jmchilton.net >>>> >>>> On Mon, Oct 1, 2012 at 8:24 AM, Jorrit Boekel >>>> <jorrit.boekel(a)scilifelab.se> wrote: >>>>> Dear list, >>>>> >>>>> I thought I was working with fairly large datasets, but they have >>>>> recently started to include ~2Gb files in sets of >50. I have ran >>>>> these sort of things before as merged data by using tar to roll >>>>> them up in one set, but when dealing with >100Gb tarfiles, Galaxy >>>>> on EC2 seems to get very slow, although that's probably because of >>>>> my implementation of dataset type detection (untar and read through files). >>>>> >>>>> Since tarring/untarring isn't very clean, I want to switch from >>>>> tarring to creating composite files on merge by putting a tool's >>>>> results into the dataset.extra_files_path. This doesn't seem to be >>>>> supported yet, because we currently pass in do_merge the output >>>>> dataset.filename to the respective datatype's merge method. >>>>> >>>>> I would like to pass more data to the merge method (let's say the >>>>> whole dataset object) to be able to get the composite files directory and 'merge' >>>>> the files in there. Good idea, bad idea? If anyone has views on >>>>> this, I'd love to hear them. >>>>> >>>>> cheers, >>>>> jorrit >>>>> >>>>> ___________________________________________________________ >>>>> 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/

1 0

Error running cuffmerge
by Iry Witham 21 Oct '12

21 Oct '12

Hi Folks, I have run into an issue with cuffmerge. I am attempting to run it with mm10 references and it fails attempting to execute gtf_to_sam. The following is the actual error message I get: Error running cuffmerge. [Fri Oct 19 15:13:55 2012] Beginning transcriptome assembly merge ------------------------------------------- [Fri Oct 19 15:13:55 2012] Preparing output location cm_output/ [Fri Oct 19 15:14:15 2012] Converting GTF files to SAM gtf_to_sam: invalid option -- F cufflinks v0.9.1 ----------------------------- Usage: cufflinks [options] <transcripts.gtf> <out.sam Options: -r/--reference-seq reference fasta file for sequence bias correction [ default: NULL ] [FAILED] Error: could not execute gtf_to_sam I have assured that the indexes and loc files are correct and in place. Can someone point me in the right direction? Thanks, Iry Witham Scientific Applications Administrator Scientific Computing Group Computational Sciences Dept. The Jackson Laboratory 600 Main Street Bar Harbor, ME 04609 Phone: 207-288-6744 email: iry.witham(a)jax.org The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.

3 2

Re: [galaxy-dev] Poisson two-sample test question
by Josh Herr 19 Oct '12

19 Oct '12

Hi Anton and the Galaxy Developers, Please forgive me for contacting the list, but for the life of me I've tried over the last couple of weeks to get the Poisson two-sample test under the metagenomic analysis option to work. My table is simple: a three column tabular file with the first column being the name of the query and the next two columns being the read amounts of two different samples. The test is pretty straightforward and I am getting no errors. When the test is returned to me I have a empty table. I've tried all different iterations of the table on lots of different versions of Galaxy (Penn State, JGI, UC Davis, etc.) and I'm getting the same result. Is there a way there is a bug present? I'm able to get this table to work in my R console. I've left my data active in my user account (jrh408(a)psu.edu) Sorry for the email and appreciate your time into either telling me I'm an idiot or there is a bug. Thanks ~ josh __________________________________________________________ Joshua R. Herr 321 Forest Resources Building The Schatz Center for Tree Molecular Genetics The Pennsylvania State University University Park, PA 16802, USA email: jherr(a)psu.edu joshua.r.herr(a)gmail.com phone: +01.503.880.3131 (cellular) 814.865.4440 (office) science blog: http://cymeandcystidium.com website: http://joshuaherr.com _____________________________________

1 0

Re: [galaxy-dev] [galaxy-user] Data table named 'bowtie2_indexes' is required by tool but not configured
by Jeremy Goecks 19 Oct '12

19 Oct '12

(moving to galaxy-dev) If the server won't start, there should be log messages describing the problem. What do the log messages say? On Oct 19, 2012, at 9:30 AM, Sachit Adhikari wrote: > Thanks but after adding those lines when I stop and started the server using --daemon mode, the server is not working? What might be the problem? > > On Fri, Oct 19, 2012 at 9:01 AM, Jeremy Goecks <jeremy.goecks(a)emory.edu> wrote: > You'll need to update the tool_data_table_conf.xml file in your Galaxy home directory. > > If you haven't made changes to the file, you can copy tool_data_table_conf.xml.sample to tool_data_table_conf.xml If you have made changes, add these entries to the file: > > -- > <table name="bowtie2_indexes" comment_char="#"> > <columns>value, dbkey, name, path</columns> > <file path="tool-data/bowtie2_indices.loc" /> > </table> > > <table name="tophat2_indexes" comment_char="#"> > <columns>value, dbkey, name, path</columns> > <file path="tool-data/bowtie2_indices.loc" /> > </table> > -- > > Finally, please direct questions about local Galaxy installations to the galaxy-dev mailing list: galaxy-dev(a)bx.psu.edu > > Best, > J. > > On Oct 19, 2012, at 2:58 AM, Sachit Adhikari wrote: > >> I am getting this error in Bowtie2 and Tophat2: >> Data table named 'bowtie2_indexes' is required by tool but not configured >> Data table named 'tophat2_indexes' is required by tool but not configured. >> >> How can I solve it? Thanks >> ___________________________________________________________ >> 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/ > >

1 0