On 06/19/2012 07:11 PM, Chebbi Mohamed Amine wrote:
Hi Galaxy team !
I'am trying to remove userless histories from my galaxy database as
mentoned in this link (
by using the command above :
python cleanup_datasets.py universe_wsgi.ini -d 60 -1
However I get an error message like this :
File
Hi Hans-Rudolf;
Yes!! I didn't pay attention and i was really calling the script fom
~/galaxy_dist/scripts/cleanup_datasets/.
Now when I call it from ~/galaxy_dist/ it works very well.
Thanks :)
Amine
2012/6/20 Hans-Rudolf Hotz h...@fmi.ch
On 06/19/2012 07:11 PM, Chebbi Mohamed Amine
Hi all,
I was working on the integration of the samtools view to work with Galaxy.
The idea is to filter an indexed bam file on a chromosome with samtools view
-bh in.bam.bai chr1.
After some research I noted that samtools will only execute this command when
it can find the corresponding
On Wed, Jun 20, 2012 at 2:59 PM, j.w.f.van_der_heij...@lumc.nl wrote:
Hi all,
I was working on the integration of the samtools view to work with Galaxy.
The idea is to filter an indexed bam file on a chromosome with samtools
view -bh in.bam.bai chr1.
After some research I noted that
Hi Peter,
Thanks for you quick answer! But I am very new to Galaxy. Could you explain
something about those symlinks?
Regards,
Jaap
From: Peter Cock [p.j.a.c...@googlemail.com]
Sent: Wednesday, June 20, 2012 4:01 PM
To: Heijden, J.W.F. van der (HG)
Cc:
I have to refine that statement about the error message I'm getting now:
On upload I get the same error message
Metadata was defined for some items in revision 'e183f52194a5'. Correct the
following problems if necessary and reset metadata.
join.xml - This file refers to a missing file
Dear,
I've been running unit tests on the latest galaxy-central 7294:663e03e40c86
that have me this error:
[localhost] out:
==
[localhost] out: ERROR: Failure: ImportError (cannot import name
install_manager)
[localhost] out:
Thanks Anne, I'll make sure this fix makes it into my next commit to Galaxy
central.
Greg
On Jun 20, 2012, at 11:42 AM, Anne Pajon wrote:
Dear,
I've been running unit tests on the latest galaxy-central 7294:663e03e40c86
that have me this error:
[localhost] out:
Thanks very much for the information Birgit - I'll be taking a look at this
shortly and get back to you when I have the fix committed.
On Jun 20, 2012, at 11:41 AM, Birgit Crain wrote:
I have to refine that statement about the error message I'm getting now:
On upload I get the same error
Hi Derrick,
If you use outputs_to_working_directory = True and put the working directory on
the SSD pool, writing during job execution will use the fast space. Once the
job completes, the outputs will be moved back to the larger, slower pool
configured for file_path.
--nate
On Jun 19, 2012,
On Jun 15, 2012, at 4:55 PM, Dellwo, Martin J. [JRDUS] wrote:
Hi there,
I am piloting my own instance of CloudMan in Amazon Web Services, using the
current public AMI (according to your Wiki), AMI: ami-da58aab3 and Name:
861460482541/galaxy-cloudman-2011-03-22.
I’d like to either
Hi Nate,
It seems very promising. Will try it out!
Thanks!
Derrick
On Thu, Jun 21, 2012 at 2:16 AM, Nate Coraor n...@bx.psu.edu wrote:
Hi Derrick,
If you use outputs_to_working_directory = True and put the working
directory on the SSD pool, writing during job execution will use the fast
Thank you all for the answers!
CL
___
Please keep all replies on the list by using reply all
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
Hi all,
This is going to be a very long message, so please bear with me. Anyway...
I have been asked by my colleagues to integrate modified versions of
velveth, velvetg and oases into our Galaxy instance. Of course, the first
step was to upload the would-be input files. Since these are stored as
14 matches
Mail list logo
