[galaxy-user] Finding Galaxy version
A perhaps obvious question: how do I work out what version of Galaxy an instance is? This has come up a few times because of apparent bugs and different behaviour across various development and production instances. Now if you're installed straight from the repo, you can use hg log for the repo number. But that doesn't work if it's been installed in another way, say from a tarball or via another versioning system (we use git to synchronize tool development to a production server). Simple solution? Paul Agapow (paul-michael.aga...@hpa.org.uk) Bioinformatics, Health Protection Agency - ** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **___ 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] Help
Hi, I read on Readme for MACS that: For the experiment with several replicates, it is recommended to concatenate several ChIP-seq treatment files into a single file. Now, I have illumina ChipSeq data: two files for IP samples and two files for Control samples. Is It right to use Concatenate datasets (text manipulation) and then use MACS for the peaks calling? Thank you so much. Giuseppe ___ 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] SNPEff - Reports Gain of Stop Codon as FRAME_SHIFT in some cases
Hi Pablo, Correct me if I am wrong, but I believe that SNPEff doesn't check the inserted sequence when computing the effect of an insertion? For instance an insertion of TTTA will be reported as a frameshift mutation. In the majority of cases this is fine, however if the current reading frame from the ORF annotation is the negative strand and the correct frame is selected the new codon will be: TAA T… The TAA is actually a stop codon, so the real effect of this insert should be insertion of a STOP CODON, not a frame shift in this instance. This is minor I know, but I though to report and make people aware. I am using version 2.02 of SNPEff, but I don't see this fix reported up to 2.04. -John ___ 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/