samtools in local instance of galaxy
i have installed local instance of galaxy and have a small problem with samtools. when i try to convert sam file to bam, the result pane shows that the job is running (for several hours). but when check the galaxy log file, it shows that the job is finished normally. i can also find the result (bam) file in galaxy/database/files/000/ folder. can anyone help to resolve this issue. Thanks Praveen
On Jan 25, 2012, at 5:28 AM, Praveen Baskaran wrote:
i have installed local instance of galaxy and have a small problem with samtools. when i try to convert sam file to bam, the result pane shows that the job is running (for several hours). but when check the galaxy log file, it shows that the job is finished normally. i can also find the result (bam) file in galaxy/database/files/000/ folder. can anyone help to resolve this issue.
Hi Praveen, Please change the following in your universe_wsgi.ini: set_metadata_externally = True And let us know if this makes a difference. Most likely, the tool output is very large and the Galaxy process is setting metadata on it. With metadata set externally, you'll be able to see this step as a separate process. --nate
Thanks Praveen
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
participants (2)
-
Nate Coraor
-
Praveen Baskaran