Hi,
I'm having trouble getting visualization icons, like Phyloviz, to show up
on my Galaxy instance running in CentOS 6.7. Here are the steps I took,
expecting it to work:
1. cloned Galaxy tag v15.07 (that's the version we need to run in
production)
2. Followed the steps in https://wiki.galaxyp
Hi Edgar,
for the package_perl issue please try installing updates to the
dependencies (package_gnu_coreutils and package_perl in their respective
versions) and then return to this screen and click the 'repository action'
button and then 'manage dependencies' from the menu. Uninstall both
dependen
Hello Galaxians,
I’m running Galaxy 15.10 and running workflows that include tools that require
reference genomes (e.g. Extract Genomic DNA). I set the dbkey for the input
dataset and it is retained for some tools, but not others. Running the
workflow multiple times, it looks like the dbekey
It works! Thank you Gildas!
Amos Raphenya
Bioinformatics Software Developer
Department of Biochemistry & Biomedical Sciences
McMaster University, MDCL 2317
p: (905) 525-9140 ext: 22787
a: 1280 Main St W.,Hamilton,
Ontario, Canada L8S 4K1
e: raphe...@mcmast
Hi,
When you use ${output}, Galaxy creates a file in
database/file//dataset_YYY.dat.
Your script seem to need a directory or maybe a prefix like "output".
So when the script generate its output filename. You can use the from_work_dir
attribute of
So, I guess something like that:
>
>
Hi All,
I have a problem getting all the outputs in galaxy.
My xml config file looks like this:
id="a5_miseq" name="A5 MiSeq" version="0.1.0">
assemble microbial fastQ to fatsA
interpreter="perl">a5_pipeline.pl ${file1} ${file2} ${output}
Hi there
I've got Trimmomatic installed (from the toolshed) into our local Galaxy
server (server is latest commit on the dev branch from GitHub). It refuses
to see a dataset pair as a valid input, however.
I've tested this with two types: firstly a pair made out of 2 individual
datasets (both fas
