Hi Keith
It works with dropdowns and the when tag set on the same interface
page, see:
http://wiki.g2.bx.psu.edu/Admin/Tools/Tool%20Config%20Syntax#A.3Cwhen.3E_tag_set
Regards, Hans
On 02/29/2012 07:11 PM, Keith Sheppard wrote:
Hello, From looking at the documentation for tool config
Hi Leandro
Although we use 'dynamic_options' successfully in many tools, it is
still a little mystery to me sometimes - probably due to my non-existing
python knowledge.
Hence just double checking:
Does [ One,1,True ],
[ Two,2,False ],
[ Three,3,False]
Hi,
we work at the University of Oslo, USIT, The Research Computing Service
group (Norway). We are preparing a bioinformatics portal using Galaxy
and one of the requirements for the University of Oslo production is to
implement an authentication called FEIDE. Feide is local (for Norway)
Hi Hans!
Hey hope you liked the manuscript and hope to get feedback soon, yes
it seems with Galaxy when you use the dynamic_options feature to load
options into the form it seems to go through different code when
processing then statically set options in the tool XML, even though it
really
I discovered that an entry needed to be added to tool_data_table_conf.xml to
define the sam_fa_indexes table the samtools_mpileup.xml was looking for. The
entry points to the sam_fa_indicies.loc file. Now the Mpileup tools is enabled.
Mike Waldron
From:
Hello,
I am getting consistent breakage for a C. Cerevisiae reference and mapped
dataset when trying to visualize the mapped data in Trackster. I'm running the
latest galaxy-dist and Trackster appears to be generally working since I added
a couple of reference genomes and users were able to
Alex,
Generally cPickle errors when loading summary trees are a result of indexing
gone bad.
Here are a couple notes that should save you some work:
*your bowtie indices and 2bit files do not need to be rebuilt; they are not
generating these errors;
*converting your SAM files to BAM may
Hi,How far along are we about thinking about being able to re-use a complete workflow as a workflow step in another workflow?This would really allow us to modularize certain aspects of the analyses and would allow us to re-use a workflow in another.Barring that, a simple copy/paste from one
Hi,
I am trying SICER peak calling tool. I am getting the following error
An error occurred running this job: /bin/sh: SICER-rb.sh: not found
Traceback (most recent call last):
File /home/root12/galaxy-dist/tools/peak_calling/sicer_wrapper.py, line
156, in module
if __name__==__main__: __main__()
