March 2018 - galaxy-dev - lists.galaxyproject.org

Gateways 2018 Call for Participation (1st deadline: May 7)
by Katherine Lawrence 08 Mar '18

08 Mar '18

Call for Participation: Gateways 2018 (September 25–27, at the University of Texas at Austin) is now accepting submissions of papers, demos, tutorials, and panels (2–4 pages) on the topic of science or engineering gateways. Gateways are user-friendly interfaces to scientific computing, data, and other domain-specific resources to support research and education. Many projects using the Galaxy Project platform would be considered gateways, and this conference is an excellent opportunity to connect with others who do similar work in diverse fields. Topics may include gateway design, use, impact, development processes, sustainability, best practices, or any other aspect that you think fellow gateway creators or users will find interesting to learn. We also welcome educational topics directed toward the next generation of gateway creators. The primary submission deadline is May 7, 2018, and a poster session deadline (open to all) will be August 1. Read more details in the Call for Participation:http://sciencegateways.org/gateways2018/call

1 0

Ensuring Python 2.7 when resolving conda dependencies for tool
by Peter Briggs 06 Mar '18

06 Mar '18

Hello I'm in the process of updating our local Galaxy tools to use conda dependency resolution, and I've hit a snag with a tool that requires Python 2.7 along with the Python 2.7-compatible version of Biopython 1.65. I'd assumed that if I explicitly used the following in the "requirements" section of the tool XML: <requirement type="package" version="2.7">python</requirement> <requirement type="package" version="1.65">biopython</requirement> that the biopython install would respect the specified Python version, and that the command execution environment would be based on Python 2.7. But in practice it appears I'm getting Python3 as I'm seeing errors: File "XXXXXXXX/galaxy-tools/tools/pal_finder/pal_filter.py", line 129 print "\n~~~~~~~~~~" ^ SyntaxError: Missing parentheses in call to 'print' This is happening both when running the tool tests via the planemo tests, and also when I install the tool from a local toolshed instance. Can anyone advise how to coerce the Python dependencies to be 2.7-compatible? Thanks in advance for any help, Best wishes Peter -- Peter Briggs peter.briggs(a)manchester.ac.uk Bioinformatics Core Facility University of Manchester B.1083 Michael Smith Bldg Tel: (0161) 2751482

3 6

Disabling downloading datasets from the UI!
by Hakeem Almabrazi 06 Mar '18

06 Mar '18

Hi everyone, Is there a way to disable the ability to download datasets from the Galaxy UI history? If so can someone tell me how to do that Best regards, Hakeem Disclaimer: This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, any reading, printing, storage, disclosure, copying or any other action taken in respect of this e-mail is prohibited and may be unlawful. If you are not the intended recipient, please notify the sender immediately by using the reply function and then permanently delete what you have received. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Sidra Medical and Research Center.

1 0

bigwig problem
by Jochen Bick 06 Mar '18

06 Mar '18

Hi, how can I fix this problem? bedGraphToBigWig: error while loading shared libraries: libmysqlclient.so.18: cannot open shared object file: No such file or directory I have the files in the local bin but somehow it does not work inside galaxy. Thanks in advance. Cheers Jochen

2 7

tool output pattern syntax
by Jochen Bick 05 Mar '18

05 Mar '18

Hi, I have a problem with the output of rcorrector which I would like to wrap. The input are single-end or paired-end fastq file/s and the output is the name (name of the input file) of the files plus ".cor.fq" so for example: input: sample_R1.fastq, sample_R2.fastq output: sample_R1.cor.fq, sample_R2.cor.fq How can I catch the output? something like: <data name="output1" format="fastq" label="${tool.name} on ${on_string}: R1"> <discover_datasets pattern="$input1\_cor"/> </data> <data name="output2" format="fastq" label="${tool.name} on ${on_string}: R2"> <discover_datasets pattern="$input2\_cor"/> <filter>library['lib'] == 'paired'</filter> </data> but $input is the complete path ... Has anyone an idea? Cheer Jochen

1 0

Problem Loading Conda tool dependencies
by Hendriks, Marian 01 Mar '18

01 Mar '18

Dear all, I've written and deployed a tool to a local tool shed and using this tool shed I installed the tool into a local Galaxy instance. This tool uses two dependencies and both seem to working fine when running the tool in my local Galaxy instance as everything works as it is supposed to. Both dependencies are defined using the requirements tag: <requirements> <requirement type="package" version="0.21.0">pandas</requirement> </requirements> >From the local tool shed the tool was installed into a different local Galaxy instance, one that I can only access as user. The tool could successfully be installed however upon running the tool an error was generated saying: ModuleNotFoundError: No module named 'pandas' I've received word that in this Galaxy instance, Conda is listed as a dependency resolver in the dependency_resolvers_conf.xml file and that the Conda successfully installed the two dependencies (Galaxy Admin panel -> Manage Tool Dependencies) in the version described by the tool's XML-wrapper. I tried reinstalling the tool from the tool shed into my own local Galaxy instance after I have manually removed the dependencies using Conda and again, everything works like it is supposed to. I guess this means that the problem does not lie with the installation from the tool shed. Has anyone encountered similar problems or does anyone know how to fix this? Thanks in advance! With regards, Marian Hendriks

1 0