Hi Jean-Frederic
I am currently writing a Galaxy wrapper (for SortMeRNA [1]) and I would
have several questions.
== Pre-processing an input ==
SortMeRNA filters rRNA reads against an indexed rRNA database. This
database can either be one bundled together with SortMeRNA and defined
in a
Hi Luobin
My python version is 2.6.3 and I would like to upgrade it to 2.7.3. So
is there anything that we need to on Galaxy after Python is upgraded to
a new version?
Based on my experience (2.5 to 2.6 ), it should work without any extra
steps required. When you restart Galaxy, it will
Hi Hans-Rudolf,
Thank you for your answer.
I am not sure of the best design here.
*Providing another wrapperfor this other binary, with users
explicitly
using it beforehand in their workflow?
*Assuming the databases have been processed outside of Galaxy
beforehand
? (As the tool
Hello,
I have the connection using OAuth and I get the email of a user from
other platform. Next, I want to associate this user with a user of
Galaxy, like the OpenID does. Can anyone describe me explicitly the
procedure should I do? What files should I change?
Thank you in advance,
Zinon
On 01/23/2013 12:22 PM, Jean-Frédéric Berthelot wrote:
Hi Hans-Rudolf,
Thank you for your answer.
I am not sure of the best design here.
*Providing another wrapperfor this other binary, with users
explicitly using it beforehand in their workflow?
*Assuming the databases have been processed
Hey Devs,In our local install we noticed some of our jobs would take longer than 24hours and in the admin manage job views the update time would rollover at 24 hours. I have attached a patch which is made against the January release in galaxy-dist that shows the correct time in hours.- Eric
On Thu, Jan 17, 2013 at 11:14 PM, Peter Cock p.j.a.c...@googlemail.com wrote:
On Thursday, January 17, 2013, Carlos Borroto wrote:
On Wed, Jan 16, 2013 at 7:28 AM, Peter Cock p.j.a.c...@googlemail.com
wrote:
Renaming the file to replace the colon with (say) an underscore allows
a manual
Hey Andy,
Financially, it's probably best to start small cluster-wise. What I'd probably
recommend for your particular project would be using a single m1.xlarge
instance as the head node, seeing how that goes, and then adding workers as you
find it useful. Should you find that it isn't
On Jan 23, 2013, at 4:09 PM, Luobin Yang wrote:
Hi,
I ran into this error and I found the following thread discussing the
problem, interestingly, for my system, the computer node runs the same Python
version as the head node, but with a newer OS version, but it also generates
this
Hi,
I installed galaxy completely from scratch:
rm -rf galaxy-dist hg clone https://bitbucket.org/galaxy/galaxy-dist/
I'm not a mercurial expert but I think I have changeset
8530:a4113cc1cb5e; at least that's the first entry in hg log.
Then started galaxy like this:
cd galaxy-dist
./run.sh
Hi, Dan.
Using format=rda will restrict the list to history items of the 'rda'
datatype - but ONLY if the rda datatype has been defined!
The easiest way to do that is to define a new datatype in
datatypes_conf.xml and since rData is binary, you should subclass binary.
Something like (untested -
On Wed, Jan 23, 2013 at 3:51 PM, Ross ross.laza...@gmail.com wrote:
Hi, Dan.
Using format=rda will restrict the list to history items of the 'rda'
datatype - but ONLY if the rda datatype has been defined!
The easiest way to do that is to define a new datatype in datatypes_conf.xml
and since
Hi, Dan
Glad it worked and thanks for pointing out a more general mimetype - does
any one else (other than me) want to vote to add
datatype extension=rda type=galaxy.datatypes.binary:Binary
mimetype=application/x-gzip subclass=True /
to datatypes_conf.xml.sample permanently ?
On Thu, Jan 24,
On Wed, Jan 23, 2013 at 4:03 PM, Ross ross.laza...@gmail.com wrote:
Hi, Dan
Glad it worked and thanks for pointing out a more general mimetype - does
any one else (other than me) want to vote to add
datatype extension=rda type=galaxy.datatypes.binary:Binary
mimetype=application/x-gzip
14 matches
Mail list logo
