Re: [galaxy-dev] QIIME tools for Galaxy (WIP, call for collaborators)

2015-10-06 Thread Lance Parsons
I agree that it would be very nice to get the data flowing between each of the tools and to be able to mix/match with other tools. That is an area of Galaxy tool-dev that I'm less familiar with, so any help would be greatly appreciated. As for the manual massaging, I agree, however, at this

Re: [galaxy-dev] Installing Cairo into Gakaxy

2015-10-06 Thread Christian Brenninkmeijer
i finally got Cairo installed into R inside galaxy. As well as cairo needing fontconfig to add cairo into R also requires libmxl2 I also changed the R install. 1. Never use the zip as it has hard coded environment variables in it 2. The set_environment variable in the R install to "prepend_to"

Re: [galaxy-dev] Installing Cairo into Gakaxy

2015-10-06 Thread Björn Grüning
Hi Christian, what is needed from the TS site? Do you have any changes that are needed in the cairo package or R package? For me everything is now working and the only thing you need to do is to specify the Rcairo tarball in your tool_dependendy file. Like here:

Re: [galaxy-dev] Installing Cairo into Gakaxy

2015-10-06 Thread Christian Brenninkmeijer
HI Bjorn, I now see you are bringing in libmxl2 in dexseq. As this is needed by various R packages and already installed by fontconfig would it be worth making it a first class dependency of package_r_3_2_1 I also see that in dexseg you specifically say "libxml2 needs to be sourced after R"

[galaxy-dev] Connection to PBS server XXX for state check failed - is it possible to get any help?

2015-10-06 Thread Zuzanna K. Filutowska
Dear All, is it possible to get any help in a subject of pbs_python problems? Especially Galaxy crash related to this issue. Let me remind: I encountered exactly the same problem: http://osdir.lowified.com/galaxy-development-source-control/2012-07/msg00132.html However my Galaxy instance

Re: [galaxy-dev] QIIME tools for Galaxy (WIP, call for collaborators)

2015-10-06 Thread Daniel Blankenberg
Hi Lance, I looked at this a bit ago and had similar concerns, particularly with the outputs and inputs not being well-defined. In addition to the output tar ball —> local, extract —> upload not being great, as you mention, the input datatypes, etc, could use some work — in the very least, we