Hello,
A Data Manager for this function exists in the Tool Shed. Perhaps it will
help with troubleshooting?
https://toolshed.g2.bx.psu.edu/view/devteam/data_manager_picard_index_builder/00491eabe22b
Best,
Jen
--
Jennifer Hillman-Jackson
Galaxy Application Support
http://usegalaxy.org
http://ga
Hi Vijay,
Chicken will be added soon. Duck needs a review first. I'll put more
comments in your Biostars post later today/tomorrow depending on progress
for galGal3/4.
https://biostar.usegalaxy.org/p/17529/
Thanks,
Jen
--
Jennifer Hillman-Jackson
Galaxy Application Support
http://usegalaxy.o
Hi Julie,
We ran into some encoding issues last month when working on a
new Galaxy server with MySQL, and decided to switch to PostgreSQL
instead - and so far that has been fine:
http://dev.list.galaxyproject.org/MySQL-amp-ToolShed-installs-latin-1-codec-can-t-encode-character-td4669251.html
The
Dear sir,
Kindly add reference Genome of Chicken (Gallus gallus) and Duck (Anas
platyrhynchos) in Tophat Reference genome section.
*Regards,*
*Dr. P. Vijayakumar,*
*Assistant Professor,*
*Instructional Livestock Farm Complex, *
*Veterinary College and Research Institute,*
*Orathanadu, **Thanjavur,*
Dear all,
I have just changed my galaxy database encoding in utf8 to avoid error
of loading histories. It works fine.
But when I run a new job after this change, the bad characters
re-appear in my output and the error "An error occured when getting
updates from the server" re-appear too.
When I've
Dear Sebastian,
Thank you very much for your response. I just had a look at posters few minutes
before I receive your email. It looks really great and helpful. I think it will
save me a lot of time during Galaxy installation.
Thank you once again.
Regards,
Marija
-Original Message-
Fr
Dear Marija,
I would recommend to google for the "ngs-fablab" - there are two posters
and a talk online from the GCCs 2014 and 2015, respectively.
I admit, it may look like self-advertising :). But in fact we set up a
local instance at the medical faculty in Munich (LMU) which is quite
similar to
Dear all,
I am currently working on Galaxy installation at our Center for Medical
Research. As a login server, we are using VM based on SLES-12. We are planning
to extend it on a Cluster later and we would like to use SLURM as DRM. Is there
any recommendation or "step-by-step" recipe how to set
Ah, and if you want to figure out the ID of a tool, you can click the small
info button
of a dataset produced by the tool, so in the case of the upload tool it
reads:
Galaxy Tool ID: upload1
On 9 May 2016 at 12:25, Marius van den Beek wrote:
> Puhh, you're right, and somewhere in the undepths of
Hi Tiziano,
I think you are correct in your assumption.
If you do not need to have uploads run on pulsar, you should be able to
specify a local destination for uploads (the upload tool id is upload1) in
your job_conf.xml.
There are some examples described here:
https://github.com/galaxyproject/gal
Hi all,
I have succesfully setup a Galaxy-Pulsar architecture and I am able to run
jobs over datasets* already uploaded on a history*.
When I try to upload a new file to the history, though, the upload job
fails with the following error:
Traceback (most recent call last):
> File "/home/flati/p
11 matches
Mail list logo