I figured out that only jobs that used one of the files could not run.
They wanted a tabular file, which I uploaded before as "txt" and
changed then to "tabular".
It gave the message that some metadata could not be determined.
Auto-detection somehow just worked now when I tried it the 3rd time.
It
Hi list-members,
I have a Cloud Man instance on amazon.
I did minimal adaption (installing some tools, adding an index)
I'm currently running only a master, which is allowed to run jobs.
I have now 3 jobs saying: "This job is waiting to run"
But in the CloudMan console it says:
"Worker status: I
Hi Chris,
as a workaround, can you try to set: retry_metadata_internally = False
Cheers,
Bjoern
Am 09.06.2015 um 20:41 schrieb C. Ch.:
> Hi Bjoern,
> We could default to using sorted BAM files from Bismark as that is Ok with
> methylkit which we use for our downstream analysis. On the other han
Hi Folks,
thank you so far for the previous help. I got much further.
Now I'm stuck with data collections.
Because this is quite a list, I appreciate also answers to parts of my
questions ;)
I have two issues:
A) manual definition of data collections (any type) by user and/or admin
B) definition
Hi Hans,
This happens when I try to create new visualisations.
I'll try to have a look at the trackster code... but not feeling very confident
about that :-(
Thanks anyways,Cristian
Subject: Re: [galaxy-dev] Trackster bug
From: hansrudolf.h...@fmi.ch
Date: Wed, 10 Jun 2015 13:21:09 +0200
CC: gala
I am not really familiar about the linking of the datasets in the database
(especially, when it comes down to visualization), but as a last suggestion:
Have you tried using a new visualization ?
Hans-Rudolf
On Jun 10, 2015, at 12:36 PM, C. Ch. wrote:
> Nope, the name of the gff file is uniqu
Nope, the name of the gff file is unique except for the fact that I uploaded
different versions of it in the data library. The second test I did has only
one version and has the same problem. Remember that the file imported from the
data library into the history works but the file directly from
just double checking:and what about the 'name' in the History panel?
Hans-Rudolf
On Jun 10, 2015, at 11:43 AM, C. Ch. wrote:
> Hi Hans,
>
> Actually the older dataset has nothing to do with the actual GFF file
> name-wise or other. Trackster tries to load
> database/files/004/dataset_
Hi Hans,
Actually the older dataset has nothing to do with the actual GFF file name-wise
or other. Trackster tries to load database/files/004/dataset_4402.dat (a
dataset created in 01/2013 and which has been deleted and purged) whereas the
GFF file corresponds to database/files/044/dataset_44835
Hi Cristian
This problem sounds familiar. Have the new and the old file the same name? If
so, try renaming your new gff file.
Hans-Rudolf
On Jun 10, 2015, at 10:34 AM, C. Ch. wrote:
> Hi all,
>
> I have uploaded a gff annotation to a shared library and when I try to load
> it into trackste
Hi all,
I have uploaded a gff annotation to a shared library and when I try to load it
into trackster it tries consistently to load an older dataset that does not
exist anymore and does not correspond to the real gff dataset file. If I load
the gff into a history, then this file is correctly loa
11 matches
Mail list logo
