This seems really interesting! Just from a quick investigation it
looks like it is targeting the kind of problem I want to solve. I
wonder if you (or anyone else) have some experience to share with
bioHDF in terms of how easy it is to use or how much traction it's
gaining in the community? The
Hi Dannon,
two days of going crazy have an end. It works, tanks!
-Christian
Dannon Baker wrote:
Christian,
This is an issue with postgres9 and our JSONType custom datatype. I have a
ticket open that you can follow if you'd like to be notified of the resolution.
Here's the link:
Pauras P Patil wrote:
Hello,
I am currently working on a project related to bioinformatics here at Purdue
University and we wanted a tool that could create a workflow for the data
that we collect. I have downloaded the source code for galaxy, but have no
idea on how to integrate galaxy
David Hoover wrote:
This used to work. Now when I try to upload a directory of files, it gives
this error:
URL:
https://galaxy.cit.nih.gov/library_common/ldda_info?library_id=a799d38679e985dbshow_deleted=Falsecntrller=libraryfolder_id=0a248a1f62a0cc04use_panels=Falseid=dff4190d282fb07a
I've set up a local instance of Galaxy following the instructions in the
wiki for a production instance. I'm running on CentOS with Apache, and
a mysql database server.
Everything looks great when viewed directly through the Galaxy web
server on port 8080.
I've implemented the Serving
Ryan Golhar wrote:
I've set up a local instance of Galaxy following the instructions in
the wiki for a production instance. I'm running on CentOS with
Apache, and a mysql database server.
Everything looks great when viewed directly through the Galaxy web
server on port 8080.
I've
Hi Nick,
Yes, these nextgen reads files are huge and getting bigger every quarter!
But there will be storage issues nomatter whether you use Galaxy or not.
In fact, i think users are more likely to cleanup files and histories in
galaxy than they are to cleanup NFS folders -- out of sight, out
Hi Nate,
Thank you for your reply.
I am getting there, but I need a bit more help.
Firstly, yes, I had an alias hg (which was history | grep $1).
I got rid of it and hg is working fine.
Secondly, I installed the latest version of zlib (1.2.5) and
I can go further with sh run.sh, but it hangs
SOLVED. I copied/paste the Rewrite rules for apache from the wiki
without updating the paths to my installation...once I did that, all
worked well.
On 2/17/11 5:07 PM, Ryan Golhar wrote:
I've set up a local instance of Galaxy following the instructions in
the wiki for a production
Hi Nate,
Please ignore my previous post. I got it working.
I changed an entry in universe_wsgi.ini file.
From #host = 127.0.0.1 to host = vixen.egcrc.org.
It appears to be working.
Many thanks for your help.
Regards,
Tena Sakai
On 2/17/11 1:48 PM, Tena Sakai tsa...@gallo.ucsf.edu wrote:
Nevermind (once again). I figured out I need to compile it from the
torque...
On 2/17/11 10:30 PM, Ryan Golhar wrote:
I'm configuring my local install of galaxy to work with my torque/maui
cluster. On the Config/Cluster wiki page, there is mention about telling
Galaxy where the DRMAA library
I'm configuring my local install of galaxy to work with my torque/maui
cluster. On the Config/Cluster wiki page, there is mention about
telling Galaxy where the DRMAA library is located. The example given
points to libdrmaa.so.
I've searched my torque installation and haven't come across
Ok, so I think I have everything set up correctly. I'll test my cluster
integration tomorrow. For now, I can see galaxy from my web browser.
First issue - When I go to User - Login and try to log myself in (I've
already registered myself), it looks like it works, but the browser get
Ryan, congratulations on getting this far!
On Fri, Feb 18, 2011 at 3:52 PM, Ryan Golhar golha...@umdnj.edu wrote:
Ok, so I think I have everything set up correctly. I'll test my cluster
integration tomorrow. For now, I can see galaxy from my web browser.
First issue - When I go to User -
14 matches
Mail list logo
