Re: [galaxy-user] Problems starting Galaxy Cloudman

2012-03-09 Thread Dannon Baker
Greg,

The problem here is that the galaxy update failed to merge a change to run.sh 
because of minor customizations it has.  We'll have a long term fix out for 
this soon, but for now what you can do is ssh in to your instance and update 
run.sh yourself prior to restarting galaxy.  All you need to do is add 
'migrated_tools_conf.xml.sample' to the SAMPLES in 
/mnt/galaxyTools/galaxy-central/run.sh, execute `sh run.sh --run-daemon` (or 
restart galaxy again from the admin page) and you should be good to go.

That new AMI you're seeing is not owned by the Galaxy Team, and we don't 
actually know who made it.  Keep using the same galaxy-cloudman-2011-03-22 for 
now (and we'll always have the most up-to-date AMI listed at 
usegalaxy.org/cloud).  Because of Cloudman's modular volume design almost 
nothing resides on the AMI itself, so we can (and do) update the tools and 
index volumes without having to touch it.  So while the AMI reflects a date of 
almost a year old, the galaxy tools volume (and thus the actual Galaxy instance 
you're running) has been updated much more recently.

One last note- if you're updating and copying your tools in every time, you may 
want to try using the 'Persist changes' functionality available in the Cloudman 
admin panel.  Once you've set your instance up how you want, if you click 
'Persist changes to galaxyTools', it'll create a custom snapshot of your tools 
volume that will be used from that point forward with this instance.

Let me know if you have any more issues,

-Dannon

On Mar 9, 2012, at 2:53 AM, Greg Edwards wrote:

 Hi,
 
 I'm trying to restart my Galaxy Cloudman service, using the same approach 
 that has been successful over the last couple of months ..
 
  - launch AMI 861460482541/galaxy-cloudman-2011-03-22 as m1.large
  - update from Cloudman console
  - copy in my tools etc etc
  - restart
  - away we go, all works
 
 However today the update fails, the log says ...
 
 /mnt/galaxyTools/galaxy-central/eggs/pysam-0.4.2_kanwei_b10f6e722e9a-py2.6-linux-x86_64-ucs4.egg/pysam/__init__.py:1:
  RuntimeWarning: __builtin__.file size changed, may indicate binary 
 incompatibility
   from csamtools import *
 python path is: 
 /mnt/galaxyTools/galaxy-central/eggs/numpy-1.6.0-py2.6-linux-x86_64-ucs4.egg, 
 /mnt/galaxyTools/galaxy-central/eggs/pysam-0.4.2_kanwei_b10f6e722e9a-py2.6-linux-x86_64-ucs4.egg,
  /mnt/galaxyTools/galaxy-central/eggs/boto-2.2.2-py2.6.egg, 
 /mnt/galaxyTools/galaxy-central/eggs/Whoosh-0.3.18-py2.6.egg, 
 /mnt/galaxyTools/galaxy-central/eggs/pycrypto-2.0.1-py2.6-linux-x86_64-ucs4.egg,
  
 /mnt/galaxyTools/galaxy-central/eggs/python_lzo-1.08_2.03_static-py2.6-linux-x86_64-ucs4.egg,
  
 /mnt/galaxyTools/galaxy-central/eggs/bx_python-0.7.1_7b95ff194725-py2.6-linux-x86_64-ucs4.egg,
  /mnt/galaxyTools/galaxy-central/eggs/amqplib-0.6.1-py2.6.egg, 
 /mnt/galaxyTools/galaxy-central/eggs/pexpect-2.4-py2.6.egg, 
 /mnt/galaxyTools/galaxy-central/eggs/SQLAlchemy-0.5.6_dev_r6498-py2.6.egg, 
 /mnt/galaxyTools/galaxy-central/eggs/Babel-0.9.4-py2.6.egg, 
 /mnt/galaxyTools/galaxy-central/eggs/MarkupSafe-0.12-py2.6-linux-x86_64-ucs4.egg,
  /mnt/galaxyTools/galaxy-central/eggs/Mako-0.4.1-py2.6.egg, /mnt/g!
 alaxyTools/galaxy-central/eggs/WebHelpers-0.2-py2.6.egg, 
/mnt/galaxyTools/galaxy-central/eggs/simplejson-2.1.1-py2.6-linux-x86_64-ucs4.egg,
 /mnt/galaxyTools/galaxy-central/eggs/wchartype-0.1-py2.6.egg, 
/mnt/galaxyTools/galaxy-central/eggs/elementtree-1.2.6_20050316-py2.6.egg, 
/mnt/galaxyTools/galaxy-central/eggs/docutils-0.7-py2.6.egg, 
/mnt/galaxyTools/galaxy-central/eggs/WebOb-0.8.5-py2.6.egg, 
/mnt/galaxyTools/galaxy-central/eggs/Routes-1.12.3-py2.6.egg, 
/mnt/galaxyTools/galaxy-central/eggs/Cheetah-2.2.2-py2.6-linux-x86_64-ucs4.egg, 
/mnt/galaxyTools/galaxy-central/eggs/PasteDeploy-1.3.3-py2.6.egg, 
/mnt/galaxyTools/galaxy-central/eggs/PasteScript-1.7.3-py2.6.egg, 
/mnt/galaxyTools/galaxy-central/eggs/Paste-1.6-py2.6.egg, 
/mnt/galaxyTools/galaxy-central/lib, /usr/lib/python2.6/, 
/usr/lib/python2.6/plat-linux2, /usr/lib/python2.6/lib-tk, 
/usr/lib/python2.6/lib-old, /usr/lib/python2.6/lib-dynload
 Traceback (most recent call last):
   File /mnt/galaxyTools/galaxy-central/lib/galaxy/web/buildapp.py, line 82, 
 in app_factory
 app = UniverseApplication( global_conf = global_conf, **kwargs )
   File /mnt/galaxyTools/galaxy-central/lib/galaxy/app.py, line 24, in 
 __init__
 self.config.check()
   File /mnt/galaxyTools/galaxy-central/lib/galaxy/config.py, line 243, in 
 check
 tree = parse_xml( config_filename )
   File /mnt/galaxyTools/galaxy-central/lib/galaxy/util/__init__.py, line 
 105, in parse_xml
 tree = ElementTree.parse(fname)
   File 
 /mnt/galaxyTools/galaxy-central/eggs/elementtree-1.2.6_20050316-py2.6.egg/elementtree/ElementTree.py,
  line 859, in parse
 tree.parse(source, parser)
   File 
 /mnt/galaxyTools/galaxy-central/eggs/elementtree-1.2.6_20050316-py2.6.egg/elementtree/ElementTree.py,
  line 576, in parse
 source = 

Re: [galaxy-user] question from a new Galaxy user

2012-03-09 Thread Kevin L
If I may add, I believe galaxy will uncompress your files if zipped.
Unzipping a 13 GB file, will take a while.
Kev
___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

  http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

  http://lists.bx.psu.edu/

[galaxy-user] Clustal error during Bowtie run (public server)

2012-03-09 Thread Hemarajata, Peera
Dear all,

I was trying to use Bowtie on the public server to align my groomed paired 
reads to a reference FASTA file. My FASTA contains sequences of 7 contigs (so 7 
sequences altogether). After a while this error showed up:

Job output not returned by PBS: the output datasets were deleted while the job 
was running, the job was manually dequeued or there was a cluster error.

I re-checked the format of the FASTA file and it looked ok. No illegal 
character. Would anybody be able to suggest what I can do to fix this?

Thank you!

Peera Hemarajata, M.D.
Advanced graduate student - Versalovic lab
Department of Molecular Virology and Microbiology - Baylor College of Medicine
Department of Pathology - Texas Children's Hospital
Suite 830, 8th Floor Feigin Center. Tel: 832-824-8245

___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

  http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

  http://lists.bx.psu.edu/

[galaxy-user] Question about aaChange tool.

2012-03-09 Thread Maha Al Kahtani
Hello,
Recently i have used galaxy to find corresponding amino acids to a list of
SNPs that i have. i used aaChange tool from the tool panel for this
purpose. After obtaining the result i checked the correctness of this
results by searching dbSNP for randomly chosen SNPs. however, some of those
SNPs mapped to incorrect amino acid,
For example,
The SNP( rs11549096), was mapped by Galaxy to the change ( Asp:Tyr/His, ) ,
Searching the dbSNP for this SNP Shows that  the Change should be  Asp :Asn
and the link for this SNP in the dbSNP is :
http://www.ncbi.nlm.nih.gov/projects/SNP/snp_ref.cgi?searchType=adhoc_searchtype=rsrs=rs11549096

So, the reference is correct in all cases i searched (more than a
thousand), the position of change in the aa is correct, *but* the
alternative aa is not correct in all cases.
What causes  this mistake, and how to solve this problem?
Note: my list contains hundreds of thousands of SNPs, so, i can not check
each one of them.

prompt response is appreciated,

Best Regards,
Maha
___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

  http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

  http://lists.bx.psu.edu/

Re: [galaxy-user] Problems starting Galaxy Cloudman

2012-03-09 Thread Ross
Since Dannon is likely asleep, maybe this will help until he can respond:
http://dev.list.galaxyproject.org/error-on-fastq-file-while-grooming-or-fastqc-report-or-fastqc-converter-td4396664.html

ie: try removing the second coverage datatype definition from
datatypes_conf.xml and restarting the Galaxy process.

On Sat, Mar 10, 2012 at 2:00 PM, Greg Edwards gedwar...@gmail.com wrote:
 Dannon,

 Thanks for that. Adding 'migrated_tools_conf.xml.sample' fixed up most
 problems. I'm left with a couple though.

 1. The tools (apart from file upload with Get Data) don't initially execute.
 This includes my new tools and existing ones like Text Manipulation / Paste
 Files side-by-side. They stay in the grey waiting to run mode for about
 15-30 minutes, then run.

 2. When they finally run, they compute and report fine but finish in the Red
 error colour, and stderr has reported as below.This is both my tools and the
 system standard ones.


 WARNING:galaxy.datatypes.registry:Overriding conflicting datatype with
 extension 'coverage', using datatype from /mnt/galaxyData/tmp/tmp6o5hnt.


 There's an oddity I should mention. When I first fire
 up galaxy-cloudman-2011-03-22, a remnant of my add-on tools is already
 showing at the top of the Tools menu. PTM Tools is there, and in
 tools_conf.xml. But the tools are not in tools/ptmtools, so the menu is
 inactive. It's like I've corrupted the file systems associated
 with galaxy-cloudman-2011-03-22.

 I'm thinking of trying it all on the Singapore AWS node where I can't have
 touched the AMI's or file sets. This has all been on US East. In fact it's
 been on US East 1d, I could try on 1a, I never go there normally, but they
 probably share data. I could try on US West. I'll let you know, if I don't
 hear before.

 Greg.




 On Sat, Mar 10, 2012 at 12:14 AM, Dannon Baker dannonba...@me.com wrote:

 Greg,

 The problem here is that the galaxy update failed to merge a change to
 run.sh because of minor customizations it has.  We'll have a long term fix
 out for this soon, but for now what you can do is ssh in to your instance
 and update run.sh yourself prior to restarting galaxy.  All you need to do
 is add 'migrated_tools_conf.xml.sample' to the SAMPLES in
 /mnt/galaxyTools/galaxy-central/run.sh, execute `sh run.sh --run-daemon` (or
 restart galaxy again from the admin page) and you should be good to go.

 That new AMI you're seeing is not owned by the Galaxy Team, and we don't
 actually know who made it.  Keep using the same galaxy-cloudman-2011-03-22
 for now (and we'll always have the most up-to-date AMI listed at
 usegalaxy.org/cloud).  Because of Cloudman's modular volume design almost
 nothing resides on the AMI itself, so we can (and do) update the tools and
 index volumes without having to touch it.  So while the AMI reflects a date
 of almost a year old, the galaxy tools volume (and thus the actual Galaxy
 instance you're running) has been updated much more recently.

 One last note- if you're updating and copying your tools in every time,
 you may want to try using the 'Persist changes' functionality available in
 the Cloudman admin panel.  Once you've set your instance up how you want, if
 you click 'Persist changes to galaxyTools', it'll create a custom snapshot
 of your tools volume that will be used from that point forward with this
 instance.

 Let me know if you have any more issues,

 -Dannon

 On Mar 9, 2012, at 2:53 AM, Greg Edwards wrote:

  Hi,
 
  I'm trying to restart my Galaxy Cloudman service, using the same
  approach that has been successful over the last couple of months ..
 
   - launch AMI 861460482541/galaxy-cloudman-2011-03-22 as m1.large
   - update from Cloudman console
   - copy in my tools etc etc
   - restart
   - away we go, all works
 
  However today the update fails, the log says ...
 
 
  /mnt/galaxyTools/galaxy-central/eggs/pysam-0.4.2_kanwei_b10f6e722e9a-py2.6-linux-x86_64-ucs4.egg/pysam/__init__.py:1:
  RuntimeWarning: __builtin__.file size changed, may indicate binary
  incompatibility
    from csamtools import *
  python path is:
  /mnt/galaxyTools/galaxy-central/eggs/numpy-1.6.0-py2.6-linux-x86_64-ucs4.egg,
  /mnt/galaxyTools/galaxy-central/eggs/pysam-0.4.2_kanwei_b10f6e722e9a-py2.6-linux-x86_64-ucs4.egg,
  /mnt/galaxyTools/galaxy-central/eggs/boto-2.2.2-py2.6.egg,
  /mnt/galaxyTools/galaxy-central/eggs/Whoosh-0.3.18-py2.6.egg,
  /mnt/galaxyTools/galaxy-central/eggs/pycrypto-2.0.1-py2.6-linux-x86_64-ucs4.egg,
  /mnt/galaxyTools/galaxy-central/eggs/python_lzo-1.08_2.03_static-py2.6-linux-x86_64-ucs4.egg,
  /mnt/galaxyTools/galaxy-central/eggs/bx_python-0.7.1_7b95ff194725-py2.6-linux-x86_64-ucs4.egg,
  /mnt/galaxyTools/galaxy-central/eggs/amqplib-0.6.1-py2.6.egg,
  /mnt/galaxyTools/galaxy-central/eggs/pexpect-2.4-py2.6.egg,
  /mnt/galaxyTools/galaxy-central/eggs/SQLAlchemy-0.5.6_dev_r6498-py2.6.egg,
  /mnt/galaxyTools/galaxy-central/eggs/Babel-0.9.4-py2.6.egg,
  

Re: [galaxy-user] Clustal error during Bowtie run (public server)

2012-03-09 Thread Jennifer Jackson

Hi Peera,

This error was caused by a network problem on our cluster, that has been 
resolved.  Please let us know if you have any further problems running 
this tool.


Sorry for the inconvenience, and thanks for using Galaxy,

Best,

Jen
Galaxy team

On 3/9/12 9:29 AM, Hemarajata, Peera wrote:

Dear all,

I was trying to use Bowtie on the public server to align my groomed
paired reads to a reference FASTA file. My FASTA contains sequences of 7
contigs (so 7 sequences altogether). After a while this error showed up:

Job output not returned by PBS: the output datasets were deleted while
the job was running, the job was manually dequeued or there was a
cluster error.

I re-checked the format of the FASTA file and it looked ok. No illegal
character. Would anybody be able to suggest what I can do to fix this?

Thank you!

Peera Hemarajata, M.D.

Advanced graduate student - Versalovic lab
Department of Molecular Virology and Microbiology - Baylor College of
Medicine
Department of Pathology - Texas Children's Hospital
Suite 830, 8th Floor Feigin Center. Tel: 832-824-8245



___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

   http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

   http://lists.bx.psu.edu/


--
Jennifer Jackson
http://usegalaxy.org
http://galaxyproject.org/wiki/Support
___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

 http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

 http://lists.bx.psu.edu/


Re: [galaxy-user] Question about aaChange tool.

2012-03-09 Thread Jennifer Jackson

Hello Maha,

This does sound very strange. Would you please share a link to your 
history so that we can examine the data and determine where the problem 
originates? Please note which dataset contains this particular problem 
if there are several runs from this same tool.


Use Options - Share of Publish, generate the share link with the top 
button, copy the URL, and paste it into a reply email sent back to me 
directly.


Thank you!

Jen
Galaxy team

On 3/9/12 8:28 AM, Maha Al Kahtani wrote:

Hello,
Recently i have used galaxy to find corresponding amino acids to a list
of SNPs that i have. i used aaChange tool from the tool panel for this
purpose. After obtaining the result i checked the correctness of this
results by searching dbSNP for randomly chosen SNPs. however, some of
those SNPs mapped to incorrect amino acid,
For example,
The SNP( rs11549096), was mapped by Galaxy to the change ( Asp:Tyr/His,
) , Searching the dbSNP for this SNP Shows that  the Change should be
  Asp :Asn and the link for this SNP in the dbSNP is :
http://www.ncbi.nlm.nih.gov/projects/SNP/snp_ref.cgi?searchType=adhoc_searchtype=rsrs=rs11549096
http://www.ncbi.nlm.nih.gov/projects/SNP/snp_ref.cgi?searchType=adhoc_searchtype=rsrs=rs11549096

So, the reference is correct in all cases i searched (more than a
thousand), the position of change in the aa is correct, _*but*_ the
alternative aa is not correct in all cases.
What causes  this mistake, and how to solve this problem?
Note: my list contains hundreds of thousands of SNPs, so, i can not
check each one of them.

prompt response is appreciated,

Best Regards,
Maha


___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

   http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

   http://lists.bx.psu.edu/


--
Jennifer Jackson
http://usegalaxy.org
http://galaxyproject.org/wiki/Support
___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

 http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

 http://lists.bx.psu.edu/


Re: [galaxy-user] Job running speed is really slow

2012-03-09 Thread Jennifer Jackson

Hello Jiwen,

Galaxy has been very busy this week. Our recommendation for large 
datasets or time constraints is to consider moving to a local or 
(better) cloud instance.

http://wiki.g2.bx.psu.edu/Big%20Picture/Choices

Instructions for getting started are in our wiki:
http://getgalaxy.org
http://wiki.g2.bx.psu.edu/Admin/Cloud

Perhaps one of these alternatives will work out for you,

Best,

Jen
Galaxy team

On 3/7/12 3:06 AM, 杨继文 wrote:

Dear Galaxy team,
I found glalaxy (website) is running really slow today. I just did some
text manipulations over a very small file. It takes a long time till the
gray colour (waiting) turns into yellow (running). Now the jobs are
still waiting to be processed (gray colour).
I have to analyze my RNA-Seq data next weeks. If the speed continues to
be like this, I am sure it is not possible to finish the analysis, since
these files are really large.
Could you please let me know what I should do to speed it up?
Thanks,
Jiwen




___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

   http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

   http://lists.bx.psu.edu/


--
Jennifer Jackson
http://usegalaxy.org
http://galaxyproject.org/wiki/Support
___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

 http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

 http://lists.bx.psu.edu/

Re: [galaxy-user] Tophat

2012-03-09 Thread Jennifer Jackson

Hello Jiwen,

The tool NGS: Picard (beta) - SAM/BAM Alignment Summary Metrics gives 
a nice set of statistics for paired end data.


Hopefully this helps,

Best,

Jen
Galaxy team

On 3/7/12 12:35 AM, 杨继文 wrote:

Dear all,
This might be a silly question, but I couldn't figure it out by myself
:-((. Could you please tell me how I can find out how many reads have
been mapped to the genome after running Tophat for pair end RNA seq data?
Thanks in advance.
JIwen




___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

   http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

   http://lists.bx.psu.edu/


--
Jennifer Jackson
http://usegalaxy.org
http://galaxyproject.org/wiki/Support
___
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using reply all in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

 http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

 http://lists.bx.psu.edu/