Hi Ry4an,
You are correct that Galaxy's GeneTrack integration requires running a local instance of GeneTrack. In the case of GeneTrack, files are accessed through a shared file system. I've added a note to clarify this in the wiki.
Thanks,
Dan
On Jan 3, 2011, at 5:47 PM, Ry4an Brase wrote:
I'm trying to get genetrack working for bed data and when clicking on the 'Genetrack' link for a bed format dataset I get a 500 Internal Server Error django exception from http://genetrack.g2.bx.psu.edu saying 'Unable to validate key!'. Example on our staging server:
http://genetrack.g2.bx.psu.edu/galaxy?filename=2f70726f6a6563742f67616c61787...
The GALAXY_URL I'm sending it decodes to:
http://dbw-galaxy.msi.umn.edu/tool_runner?tool_id=predict2genetrack
which redirects (302) to:
https://dbw-galaxy.msi.umn.edu/tool_runner?tool_id=predict2genetrack
However, I don't see a request for either in the Apache log.
Can the genetrack.g2.bx.psu.edu server be used for other galaxy installations as can the UCSC visualizer and I'm running afoul of my redirect and/or https setup, or should I have figured out that I need my own genetrack server from https://bitbucket.org/galaxy/galaxy-central/wiki/ExternalDisplayApplications... ?
Thanks,
-- Ry4an Brase 612-626-6575 Software Developer Application Development University of Minnesota Supercomputing Institute http://www.msi.umn.edu _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev