Hi Nate,
We are having an issue that when use_tasked_jobs = True, the job_wrapper.user
= None in drama.py. Do you know why that might be. It crashes my code.
Thanks,
Ilya
Ilya Chorny Ph.D.
Bioinformatics Scientist I
Illumina, Inc.
9885 Towne Centre Drive
San Diego, CA 92121
Work: 858.202.458
Running Galaxy under a python virtualenv created with the
--no-site-packages flag will prevent any pollution from local
packages.
eg see
http://wiki.pylonshq.com/display/pylonscookbook/Using+a+Virtualenv+Sandbox
Galaxy will then run using its own distributed eggs without any conflicts.
On Tue,
I'm working on a SOLiD ChIP-Seq workflow in which I want to use SICER
for peak detection. In attempting to add SICER to the workflow, I've
run into some difficulty:
1) My input is an interval file which I've created using Convert
SAM. In order to connect to the SICER module, I had to
We recently updated to the latest galaxy-dist, and learned that the
sam_merge.xml tool now uses picard MergeSamFiles.jar to merge the files instead
of the samtools merge wrapper sam_merge.py.
this is a problem for us because MergeSamFiles.jar does not honor $TMPDIR when
creating temporary file
Hi everyone,
I am experiencing a similar problem to that of Leandro. I have defined a new
datatype deriving Data, and having extension "foobar". The simplest and first
thing I'd like to do with it is create a dataset of this new type "Foobar" by
uploading from my local machine to my Galaxy de
Hi,
we want to setup a local installation of Galaxy. It seems that Galaxy
doesn't like the fact that we already have a different version of numpy
installed. When following the installation instructions, we get
following error messages:
Traceback (most recent call last):
File "./scripts/fe
On 09/19/2011 04:35 PM, sohk...@notes.cc.sunysb.edu wrote:
> Hi,
>
> I am wondering if there is way to manage user access to Galaxy tools?
>
> I.E, certain users are restricted to use certain tools.
> Thanks.
Hi Sohail
We use a 'quick and dirty' solution by enforcing log-in and then taking
adv
