Hi Thon
We see the same with our BED files, and I can reproduce it with your
example. I tend to ignore it since (so far) it has no influence on the
functionality, if I use the BED file in any other tool.
I only run into troubles when I present working with BED files in our
introductory cour
Hi, Galaxy developers,
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?
Thanks,
Luobin
___
Please keep all replies on the list by us
Hey Ido,
I actually copied & pasted those committed changes in dramaa.py manually
and it serves well as a temporary solution.
D
On Tue, Jan 22, 2013 at 10:51 PM, Ido Tamir wrote:
> Is it possible to backport this onto the latest distribution?
> Yes, I'm lazy, but there are also others that ar
Hi list,
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 relevant
.
Hi,I have noticed for a while now that BED files are not recognized correctly or at least not parsed out correctly.I notice that invariably, the (9 column) BED file comments state there is 1 region and X comments, where X + 1 is the actual number of regions in the file..Here's a few lines from the
On Tue, Jan 22, 2013 at 4:43 PM, Carl Eberhard wrote:
> Hello, Peter
>
> In revision 8646:50c65739cd1a, I've changed the error handling in
> history_contents.py:index and the client-side code that fetches dataset
> info.
>
> Long form:
> Now when an error (like yours) occurs when fetching dataset
Hello, Peter
In revision 8646:50c65739cd1a, I've changed the error handling in
history_contents.py:index and the client-side code that fetches dataset
info.
Long form:
Now when an error (like yours) occurs when fetching dataset information for
one or more datasets, the method will record the erro
Hi,
Thanks for your help!
Have a problem:
On some pages (in particular on the registration page, in .mako file) need
to add comments (explanatory information in Cyrillic (need to use utf-8)).
template`s files in ASCII.
Maybe there is a traditional method of solving this problem with the
encoding?
Hi Carl,
Sorry for the long delay!
It did not happen in a published or shared history. But it did
definitely happen in a history where some datasets where copied from
another history, since I've been copying a lot lately.
Thanks,
J
Joachim Jacob
Rijvisschestraat 120, 9052 Zwijnaarde
Tel:
Hi all,
After updating to the latest Galaxy dist-release (and moving our server
to a new location - but this can not be the reason I think), the status
of the jobs are not being updated. The box in the history stays grey.
After restarting Galaxy or the server, the correct status of the job is
Is it possible to backport this onto the latest distribution?
Yes, I'm lazy, but there are also others that are still updating
within the next weeks and will have problems without them being
aware of this fix.
best,
ido
On Jan 21, 2013, at 9:50 PM, Nate Coraor wrote:
> Hi all,
>
> The commit[1
No the problem is still there, but we have not updated yet since beginning of
december.
maybe this is related:
http://gmod.827538.n3.nabble.com/segfault-in-libdrmaa-gt-galaxy-front-end-failure-td4027349.html
best,
ido
On Jan 21, 2013, at 5:45 AM, Derrick Lin wrote:
> Hi Ido,
>
> I just found
12 matches
Mail list logo
