Hello,
What is an appropriate galaxy URL to use to obtain bed and fasta index
files? I have tried below:
myGalaxy.org:port/dataset/get_metadata_file?hda_id=[fasta_dataset_id]_name=fasta.fai
{for fasta index}
and
myGalaxy.org:port/dataset/get_metadata_file?hda_id=[bed_dataset_id]_name=bed.idx
).
Hope that helps.
On Thu, Aug 27, 2015 at 1:14 PM, Asma Riyaz asmariya...@gmail.com wrote:
Hi Carl,
Thank you for your help, I was able to access all the dataset ids in
history with the pointers you gave, but I am not finding an immediate way
to deduce which original file is from which id. I
know and we can work directly with the code
if you'd like.
On Tue, Aug 25, 2015 at 1:48 PM, Asma Riyaz asmariya...@gmail.com wrote:
In addition to my previous attempts, here is another I have tried:
*in igv.mako:*
%!
users_current_history = trans.history
dataset_ids
, Asma Riyaz asmariya...@gmail.com
wrote:
Hi Carl,
The visualization comes into play after a lab implemented tool in galaxy
is ran; I am not using galaxy's workflow. Is tracing back ids still
possible in this case with the test case you wrote earlier?
Also I couldn't figure out what trans
,
Asma
On Thu, Aug 20, 2015 at 3:03 PM, Asma Riyaz asmariya...@gmail.com wrote:
-- Forwarded message --
From: Carl Eberhard carlfeberh...@gmail.com
Date: Thu, Aug 20, 2015 at 2:46 PM
Subject: Re: [galaxy-dev] Get dataset/API ids for a dataset
To: Asma Riyaz asmariya
Hello Galaxy-dev,
I thank you so much for all the help you have given me.
I have a question about data set ids in galaxy. As a background, I am
running my own galaxy instance on a server. A pipeline implemented in the
lab produces the following files in the history:
1) 2 BAM files
2) A JSON
Hi,
Configuration of Galaxy for an LSF server led me to this link:
https://wiki.galaxyproject.org/Admin/Config/Performance/Cluster#DRMAA
The issue being the /lsf folder under galaxy does not exist. I am sort of
stuck at this point and would highly appreciate anybody's help in this
regard.
Thank
Hi,
I have been through previous issues regarding this issue. So far, I have
included the rewrite Engine logic written in
/etc/apache2/sites-available/defaults - looks like so:
VirtualHost *:80
.
.
RewriteEngine on
RewriteRule ^/galaxy$ /galaxy/ [R]
RewriteRule
