galaxy-dev July 2016

galaxy-dev@lists.galaxyproject.org

49 participants
69 discussions

Auto detection of output format Galaxy custom tool
by Katherine Beaulieu 07 Jul '16

07 Jul '16

Hi everyone, I am looking to auto-detect the file format of a file outputted by a python tool I have written. Does anyone have any idea how to do this? I have tried setting the format attribute to "auto" with no luck. Let me know if you would like to see my tool config file. Cheers, Katherine

4 11

Mapping requirements to conda recipe names (granularity?)
by Peter van Heusden 07 Jul '16

07 Jul '16

Hi there I'm trying to satisfy requirements on our RNA-seq oriented Galaxy server at SANBI using conda/bioconda. There's a disconnect between the names used in tool dependency tags and the names of conda recipes though, for example: 1) the BAM to BigWig converter (tool ID CONVERTER_bam_to_bigwig_0) has a requirement for ucsc_tools. The tool it needs, bedGraphToBigWig, is provided by the ucsc-bedgraphtobigwig package, so in this case ucsc_tools is a broader requirement than what bioconda provides. 2) the featurecounts tool requires featurecounts, which is part of the subreads recipe, so in this case featurecounts is a narrow requirement than what is provided in bioconda. In the second case, one could say subreads provides the featurecounts requirement. In the first case one could say the tool requires a narrower requirement than what it specifies, although the bioconda recipes split a single upstream package (ucsc_tools) into multiple recipes that invariable will be updated together, a somewhat strange choice. Right now I'm resolving these problems by manually creating environments (e.g. __package__featurecounts@__unversioned__) that will get picked up by the conda dependency resolver, but I'd like to hear from the list what the best way to support this is? Probably the easiest is keeping the tool requirements definition in line with what the conda recipe is called, but in some cases a mapping table between requirements and conda recipe names could be useful. Peter

2 1

Using operations on multiple datasets
by D K 06 Jul '16

06 Jul '16

Sorry for the crosspost to Biostars, but I didn't get a response, so I thought I'd post here: I just noticed that Galaxy allows creation of lists of datasets by clicking on the "Operations on multiple datasets" in the history panel. How does one use this with a custom tool (e.g. what does one put between the <input> </input> tags). Is the list treated as a text file with a list of each file? I couldn't find any examples or documentation online. I'd appreciate it if someone could point me in the right direction. Thanks!

3 2

Re: [galaxy-dev] Building tool dependencies
by Matthias De Smet 06 Jul '16

06 Jul '16

Hi All! Thanks for chiming in! I’ll give the conda recipe approach a go, this seems to be the easiest way to go, and the most futureproof! Thanks! M > Message: 1 > Date: Tue, 5 Jul 2016 06:56:00 +0000 > From: Matthias De Smet <Matthias.DeSmet(a)UGent.be> > To: "galaxy-dev(a)lists.galaxyproject.org" > <galaxy-dev(a)lists.galaxyproject.org> > Subject: Re: [galaxy-dev] Building tool dependencies > Message-ID: <D70EED58-F05E-4084-9323-1B78C707B95F(a)ugent.be> > Content-Type: text/plain; charset="utf-8" > > >> >> Hi >> >> I’m trying to put together a tool + dependency package to use umi-tools (https://github.com/CGATOxford/UMI-tools) from Galaxy. >> I’m at a loss on how I should organise this. >> >> The package is available from either github or pip. Which one is preferable to use? How do I make sure the package dependencies are installed? I’ve found the <action type="download_by_url”> and <action type=“create_virtualenv”> actions, but I’m not really sure that’s the way to go. I havent found any real resources on how to build package dependencies either. >> >> Any help? Now, approaching it by downloading the package from github with <action type="download_by_url”> and installing it with <action type="shell_command">python setup.py install</action>. This, however, tries to install the package to /usr/bin/ which isn’t desirable (obviously). >> >> Thanks a lot! >> M >> > > > ------------------------------ > > Message: 2 > Date: Tue, 5 Jul 2016 09:33:09 +0200 > From: Peter van Heusden <pvh(a)sanbi.ac.za> > To: galaxy-dev(a)lists.bx.psu.edu > Subject: Re: [galaxy-dev] Building tool dependencies > Message-ID: > <CAK1reXiH9JXQ19gysXdkdr6ynC9aZgAbKfzXAKtFM0M+Tc2-4w(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Actually, for recent Galaxy, I'd recommend making a conda recipe for > UMI-tools and contributing it to bioconda: > > https://bioconda.github.io/ > > Then your tool can just depend on this and the conda dependency resolver > (default in Galaxy since 16.01) can find it. Others can comment on the > recent work on conda/toolshed integration. > > Peter > > On 5 July 2016 at 08:56, Matthias De Smet <Matthias.DeSmet(a)ugent.be> wrote: > >> >>> >>> Hi >>> >>> I’m trying to put together a tool + dependency package to use umi-tools ( >> https://github.com/CGATOxford/UMI-tools) from Galaxy. >>> I’m at a loss on how I should organise this. >>> >>> The package is available from either github or pip. Which one is >> preferable to use? How do I make sure the package dependencies are >> installed? I’ve found the <action type="download_by_url”> and <action >> type=“create_virtualenv”> actions, but I’m not really sure that’s the way >> to go. I havent found any real resources on how to build package >> dependencies either. >>> >>> Any help? Now, approaching it by downloading the package from github >> with <action type="download_by_url”> and installing it with <action >> type="shell_command">python setup.py install</action>. This, however, tries >> to install the package to /usr/bin/ which isn’t desirable (obviously). >>> >>> Thanks a lot! >>> M >>> >> >> ___________________________________________________________ >> 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: >> https://lists.galaxyproject.org/ >> >> To search Galaxy mailing lists use the unified search at: >> http://galaxyproject.org/search/mailinglists/ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <https://lists.galaxyproject.org/pipermail/galaxy-dev/attachments/20160705/0…> > > ------------------------------ > > Message: 3 > Date: Tue, 5 Jul 2016 08:49:54 +0100 > From: Peter Briggs <peter.briggs(a)manchester.ac.uk> > To: galaxy-dev(a)lists.galaxyproject.org > Subject: Re: [galaxy-dev] Building tool dependencies > Message-ID: <577B66A2.60007(a)manchester.ac.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hello Matthias > > From what I've seen there are a number of different recipes used for > installing Python packages via the toolshed; the approach you're using > seems to be pretty common. In these cases the usual 'shell_command' > seems to be: > > python setup.py install --install-lib $INSTALL_DIR/lib/python > --install-scripts $INSTALL_DIR/bin > > which should avoid installing to /usr/bin. > > You'll then need to do something like: > > <action type="set_environment"> > <environment_variable action="prepend_to" > name="PYTHONPATH">$INSTALL_DIR/lib/python</environment_variable> > <environment_variable action="prepend_to" > name="PATH">$INSTALL_DIR/bin</environment_variable> > ... > </action> > > to ensure that the correct environment is set up when the tool is used. > > Aside from this: elsewhere I've seen other approaches including a > "magic" "package" command where the whole download and install is taken > care of in a single tag. For example: > > ... > <action type="setup_python_environment"> > <repository name="package_python_2_7_10" owner="iuc"> > <package name="python" version="2.7.10" /> > </repository> > <package > sha256sum="e01853dfe111f3aea005315573400b7216ddbabbf1f28d482a71217d67ae4f81">https://pypi.python.org/packages/source/p/pandas/pandas-0.16.2.tar.gz</package> > ... > > (see > https://github.com/galaxyproject/tools-iuc/blob/master/packages/package_pyt… > for the full recipe that I've pulled this fragment from.) > > HTH > > Best wishes > > Peter > > On 05/07/16 07:56, Matthias De Smet wrote: >> >>> >>> Hi >>> >>> I’m trying to put together a tool + dependency package to use umi-tools (https://github.com/CGATOxford/UMI-tools) from Galaxy. >>> I’m at a loss on how I should organise this. >>> >>> The package is available from either github or pip. Which one is preferable to use? How do I make sure the package dependencies are installed? I’ve found the <action type="download_by_url”> and <action type=“create_virtualenv”> actions, but I’m not really sure that’s the way to go. I havent found any real resources on how to build package dependencies either. >>> >>> Any help? Now, approaching it by downloading the package from github with <action type="download_by_url”> and installing it with <action type="shell_command">python setup.py install</action>. This, however, tries to install the package to /usr/bin/ which isn’t desirable (obviously). >>> >>> Thanks a lot! >>> M >>> >> >> ___________________________________________________________ >> 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: >> https://lists.galaxyproject.org/ >> >> To search Galaxy mailing lists use the unified search at: >> http://galaxyproject.org/search/mailinglists/ >> > > -- > Peter Briggs peter.briggs(a)manchester.ac.uk > Bioinformatics Core Facility University of Manchester > B.1083 Michael Smith Bldg Tel: (0161) 2751482

1 0

July Galactic News: GCC2016, GCC2017(!), Admin/Dev Trainings, GAMe 2017!
by Dave Clements 05 Jul '16

05 Jul '16

1 0

Error while running Cuffdiff
by Patel, Ravi Kanu 05 Jul '16

05 Jul '16

Dear Galaxy development team, I am trying to analyze RNAseq data using the following pipeline: FASTQ Trimmer | HISAT | Cufflinks | Cuffmerge | Cuffdiff | CummeRbund I am able to run everything without a problem up to the CuffDiff step. I always get an error message. I sent a bug report and posted on Biostars-Galaxy. Jen replied to my comment on Biostars and recommended I email galaxy-dev. Please see the details of the error message here: https://biostar.usegalaxy.org/p/18331/ I think it may have a problem loading the SQlite database? Even though CuffDiff gives an error message, I was still able to download the data from CuffDiff in tabular format and perform some data analysis using R. However, it would be useful to be able to use cummeRbund to analyze the cuffdiff data. Thank you in advance for all your help. Let me know if there is any other information I can provide to clarify the error, etc. Best Regards, Ravi

1 0

Re: [galaxy-dev] Building tool dependencies
by Matthias De Smet 05 Jul '16

05 Jul '16

> > Hi > > I’m trying to put together a tool + dependency package to use umi-tools (https://github.com/CGATOxford/UMI-tools) from Galaxy. > I’m at a loss on how I should organise this. > > The package is available from either github or pip. Which one is preferable to use? How do I make sure the package dependencies are installed? I’ve found the <action type="download_by_url”> and <action type=“create_virtualenv”> actions, but I’m not really sure that’s the way to go. I havent found any real resources on how to build package dependencies either. > > Any help? Now, approaching it by downloading the package from github with <action type="download_by_url”> and installing it with <action type="shell_command">python setup.py install</action>. This, however, tries to install the package to /usr/bin/ which isn’t desirable (obviously). > > Thanks a lot! > M >

3 2

Implementing iRODS with Galaxy
by Yip, Miu ki 01 Jul '16

01 Jul '16

Hello Galaxy Team, We're from the Bioinformatics Shared Resources (BSR) at Cold Spring Harbor Labs and we're looking to implement irods on a newly installed version of Galaxy. We want to incorporate iRODS (http://irods.org/). Is there a recommended way to do this, or no? Thanks in advance for the advice. Best, Miuki Yip

2 1

question using PICRUSt COG vs. KEGG
by Ana Weil 01 Jul '16

01 Jul '16

Hello, I have a general question. A metagenome prediction in PICRUSt worked fine when I ran it requesting KEGG output (running on MAIN), but I got the below error when requesting COG output. I could not find in the on-line forums or other areas of support what may be needed regarding a different input file or change in the normalization by copy number in order to get COG instead of KEGG output? Thank you very much for your help! Ana Traceback (most recent call last): File "/n/galaxy/www/galaxy_hutlab14/galaxy-hutlab14-20150109/tools/picrust_galaxy/scripts/predict_metagenomes.py", line 337, in <module> main() File "/n/galaxy/www/galaxy_hutlab14/galaxy-hutlab14-20150109/tools/picrust_galaxy/scripts/predict_metagenomes.py", line 171, in main ids_to_load=ids_to_load,verbose=opts.verbose,transpose=True) File "/n/galaxy/www/galaxy_hutlab14/galaxy-hutlab14-20150109/tools/picrust_galaxy/scripts/predict_metagenomes.py", line 113, in load_data_table genome_table_fh = gzip.open(data_table_fp,'rb') File "/n/hutlab11/tools/python2.7.8/lib/python2.7/gzip.py", line 34, in open return GzipFile(filename, mode, compresslevel) File "/n/hutlab11/tools/python2.7.8/lib/python2.7/gzip.py", line 94, in __init__ fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb') IOError: [Errno 2] No such file or directory: '/usr/local/galaxy-python/lib/python2.7/site-packages/picrust/data/cog_13_5_precalculated.tab.gz'

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

galaxy-dev July 2016