Thanks,
https://github.com/biopython/biopython/pull/385
You can't (yet) do this via the BLAST wrappers.
You would have to pull out the full sequences using the
makeblastdb wrapper, then edit them with another Galaxy
tool. Or work directly from the FASTA file if you have it.
Peter
On Wed, Oct 2
2014-10-21 14:36 GMT+02:00 Björn Grüning :
> Hi!
>
> Am 21.10.2014 um 12:39 schrieb Mikel Egaña Aranguren:
> > Hi;
> >
> > We are developing a Metagenomics tool suite (along the lines of Mothur)
> and
> > we would like to include some example workflows. What is the best
> practice
> > to upload wo
Struggling with this now...you have my vote!
From: galaxy-dev-boun...@lists.bx.psu.edu
[mailto:galaxy-dev-boun...@lists.bx.psu.edu] On Behalf Of Ross
Sent: donderdag 24 januari 2013 1:04
To: Dan Tenenbaum
Cc: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] filtering a of type 'data' so onl
Hi,
When I upload any .RData file to my Galaxy server it seems to be
unpacking/changing it. The resulting file in my history is different and around
2x larger than the uploaded file. The tool that needs to use it also aborts
with an error due to this erroneous file.
What are the workarounds?
Dear All
have very little experience in this area and probably making a very basic
mistake but I am trying to load the hg38 reference genome into a local instance
of galaxy (not installed by myself) using ‘Create DBkey and reference genome’
using ‘hg38’ in the UCSC DBkey option box(es) but keep
Hey Pieter,
Sorry I am swamped right now so I don't have time to dig into this
in detail - but I have encountered this before with datatypes that are
compressed - zipped, gzipped, etc Galaxy will attempt to
decompress them in order to figure out what they are. I believe this
is what is happe
After uploading my beta status tool to our test toolshed, I tried installing it
on another of our galaxy servers but it wasn't able to find the api endpoint
url. Is there a way to automatically do this within tool forms? I was hoping
to avoid hardcoding this as part of the tool installation pr
Well host is probably not enough - it doesn't seem like a good idea to
assume http right? There is the prefix and (trans.request.scheme) that
could be missing. Is trans.request.base what you want? Maybe
trans.request.path_url? It should be possible to recover that from
trans I guess - though I don'
