In my tool-config I try to use conditional number of output files. Is this possible? For input files the <CONDITIONAL> and <WHEN> statements are able to do that. What about output files?
If I have four listed I will always get 4 history items in my work flow. If I only generate 3 I still get 4 items of which one contains no data. I want to prevent this cluttering by providing the user a selective set of output files.
Basically can I modify the below using input parameters to generate 3 or 4 files? (not using a zip container).
Any clues appreciated.
<data name="out_1" format="tabular" label="Coords" />
<data name="out_2" format="tabular" label="Delta" />
<data name="out_3" format="png" label="Plot" />
<data name="out_4" format="text" label="Console log file" />
When building a tool's interface would it be possible to have a different
<help></help> tag for different <param type="select"> options of a
The options change the tool parameters significantly and having a big <help>
tag that includes explanation of all parameters of all the options would be
a bit confusing.
Still wondering if there's a way to get the unique id that is added to a
public url of a dataset.
For example: mygalaxy/datasets/2e5cc78dd64522bf/display/?preview=True
(I mean the 2e...).
As far as I understand from the code, It's a blowfish encryption of
something, not sure what exactly.
In the end, I'd need to foward the actual url that allows to download
the file to my tool. But of course, if I have that id, I can build the
Any help's appreciated!
I am probably missing something very obvious.
I am struggling to make a tool config file (and/or perl/bash wrapper) that runs some tools that have several input files (no problem) but also several FIXED name output files. I am able to give it some prefix but the extensions (if any) cannot be changed.
Any help appreciated how to link/get this in $output.
PS: sorry for cross posting users and dev. Not sure where the tool stuff belongs.
Anybody some suggestions for this?
Should I learn how to use rpy or simply stick with perl to get
R running in galaxy.
I've been browsing through the existing tool scripts in the galaxy dist,
but basically everything is written in rpy to run R tools.
There's 2 things I could do: either run R through perl scripts or
learn rpy, which looks pretty simple at first glance.
I'm curious as to how data from old histories gets deleted. I have
quite a few files built up under database/files/000, as .dat files seem
to stay there even when I delete my history. What is the best practice
to removing these files once they are no longer needed? Thanks
When I try to import a sample into Galaxy using a csv file I keep
getting the error "Invalid Request ID". I don't understand what a
request id is (unless it's the request name) and where it is supposed
to go in the sample csv file. Any suggestions as to what the "invalid
request id" is referring to would be great.
Hi all, did somebody tried this?
Cogentech - Consortium for Genomic Technologies
via adamello, 16