Difference between revisions of "FAQs"

From CoGepedia
Jump to: navigation, search
(How is CoGe designed and put together?)
Line 23: Line 23:
 
==How is CoGe designed and put together?==
 
==How is CoGe designed and put together?==
 
CoGe's core design principle is to keep things easy and efficient.  This extends from the underling computational infrastructure to the web-based tools.  Primarily, the web-based tools are what drives analyses, although large-scale comparative genomics analytics are best done using programming and access to CoGe's [[API]].  Follow this link for an overview of [[CoGe system arcitecture | CoGe's system design]].
 
CoGe's core design principle is to keep things easy and efficient.  This extends from the underling computational infrastructure to the web-based tools.  Primarily, the web-based tools are what drives analyses, although large-scale comparative genomics analytics are best done using programming and access to CoGe's [[API]].  Follow this link for an overview of [[CoGe system arcitecture | CoGe's system design]].
 +
 +
==What is needed to run CoGe?==
 +
Not much.  Just a web-browser:
 +
*Browser settings: 
 +
** Recommended browser: [http://www.mozilla.com/firefox Firefox]
 +
**[http://get.adobe.com/flashplayer/ Flash]
 +
** Enable Javascript ([http://support.mozilla.com/en-US/kb/Javascript#_Enabling_and_disabling_JavaScript How to enable Javascript in Firefox])
 +
** Enable Popups (for CoGe only)
 +
** [http://support.mozilla.com/en-US/kb/cookies Enable Cookies] (needed if you have a CoGe user account)
  
 
==What is CoGe's sequence analysis workflow or pipeline?==
 
==What is CoGe's sequence analysis workflow or pipeline?==

Revision as of 17:41, 10 January 2010

Commonly asked questions about CoGe.

What is CoGe?

CoGe is a online system for making the retrieval and comparison of genomic information and sequence quick and easy.

Why call it CoGe?

CoGe (pronounced /kō:jē/ ) stands for Comparative Genomics.

Why make another comparative genomics system?

We found that existing comparative genomic systems were limited in their ability to accommodate genomic information and making it easily accessible for comparative analyses. We designed CoGe from the ground up to solve four major limitations:

  1. Store multiple versions of multiple genomes from multiple organism in a single platform
  2. Quickly find sequences of interest in genomes of interest (with associated information)
  3. Comparing multiple genomic regions using any algorithms
  4. Visualize the results of analyses in such a way as to make the identification of "interesting" patterns quick and easy.

All told, we wanted a comparative genomics system that would allow us to test our ideas and hypotheses as quick as possible so we could spend more time thinking about genomes and their evolution instead of trying to get and analyze genomic sequences.

Also, we realized that we wanted a system that allowed us to quickly develop new tools and add new genomic data as they become available. This means that when we load a new genome into CoGe, all the tools of CoGe are immediately available to analyze it. Likewise, if we develop a new tool to solve one particular problem with one set of genomes, it is immediately available to all the genomes in CoGe.

How is CoGe designed and put together?

CoGe's core design principle is to keep things easy and efficient. This extends from the underling computational infrastructure to the web-based tools. Primarily, the web-based tools are what drives analyses, although large-scale comparative genomics analytics are best done using programming and access to CoGe's API. Follow this link for an overview of CoGe's system design.

What is needed to run CoGe?

Not much. Just a web-browser:

What is CoGe's sequence analysis workflow or pipeline?

While we designed CoGe to make it easy to find and comparing genomic sequences, there is no single, linear workflow through the system. Instead, CoGe's tools create an open-ended analysis network. There are central tools and access points that allow you to access the system to find sequences of interest, and "hub" points to take you from one part of the system to another. This allows for ideas to be generated while working CoGe, and be able to quickly branch out to investigate any number of interesting phenomena you find. An analysis ends when you have your answer.

For example, you start with your favorite genome (mouse), do a whole genome comparison of it to human using SynMap, identify a region with an inversion, compare the breakpoints of that region in high-detail using GEvo, extract out the human sequence using SeqView, find all the protein coding regions using FeatView, use them to find homologs in other vertebrate genomes (e.g. chimp, mouse, and platypus) using CoGeBlast, validate putative syntenic regions using GEvo, find a particular gene extra interesting because of its copy-number variation in this syntenic region and get its sequence using FeatView once again, find putative intra- and inter-specific homologs of it using CoGeBlast, generate a fasta file of those putative homologs using FastaView, which you can align using CoGeAlign, and then use to build a phylogenetic tree using TreeView or export to more expansive phylogenetic tools-sets such as CIPRES. While waiting for your trees to be reconstructed, you decided to check out the codon and protein usage variation of the genes using FeatList, notice that there is some interesting variation in a couple of genes, check their over all GC content and wobble-position GC content FeatView, wonder if these have been horizontally transferred from the mitochondria, send those sequences to CoGeBlast to search mitochondrial genomes, find putative a homolog in several of those genomes, and then compare mitochondrial genomes to determine if there are inversions near those homologs using GEvo ...

In other words, there is no predefined end-point to an analysis.

What web browser do you recommend and how should it be configured?

We only test CoGe using Firefox. For CoGe to function properly, make sure to allow pop-ups, javascript, and install Adobe's Flash Player.

What programming languages/software are used in CoGe?

Different parts of CoGe use different languages, based on what works best and what language(s) a programmer knows. In no particular order:

  • Operating System
    • Some flavor of linux
  • Web Server
    • Apache
  • Database
    • MySQL (though CoGe has been ported to PostgreSQL)
  • Database API
    • Perl
  • Web-interface
    • HTML
    • Perl CGI
    • javascript
      • jquery
    • Flash (haXe)
  • Algorithms and other stuff. Note that many programs used by CoGe are written by other programmers (e.g. Blast, Lagan, DiAlign, DAGChainer, codeml) and use a variety of languages not listed here
    • Python
    • C
    • C++
    • Java

Can you add a genome?

Yes.

We are committed to providing and supporting any publicly available genomic sequence with annotations. Please send the name of the organism, phylogenetic description, and the website from which the data can be downloaded (to ensure correct and appropriate sequencing credit). If there are multiple annotation sets, please review them and select the one that best represents high-quality and non-redundant annotations.

Example request:

Dear Eric,

Can you please add this genome to CoGe?  

 Name: Phytophthora ramorum
 Description: Eukaryota; stramenopiles; Oomycetes; Peronosporales; Phytophthora 
 Site: http://genome.jgi-psf.org/Phyra1_1/Phyra1_1.home.html
 Annotation: Filtered models with coodrdinates: FM_Phyra1_1.gtf.gz (available on download page)

Thanks in advance,
Charlie D.

If you would like a proprietary or embargoed genome loaded into CoGe such that only a specific user account of CoGe can access it, please see CoGe's System Support.


What is CoGe's Graphical Genomic Visualization Library?

CoGe uses its own genomic visualization library called GeLo.

Can CoGe be installed locally

First, remember that CoGe is a multi-component system designed to run on linux servers running apache, mysql, perl, python, and requires a plethora of other bioinformatics algorithms. Unfortunately, CoGe hasn't been packaged for redistribution. This is because our development team is very small, CoGe's code base has many independent components, and CoGe was developed for research goals (hence to get the job done). As the code base for CoGe matures, we will be releasing source code. However, under certain circumstances, we will help you install a local version of the system. Please see our system support page for additional information.

Help! I don't know how to do something.

If you have an additional question, please e-mail Eric Lyons. If you have a problem, chances are someone else is having the same problem. Your questions help drive the documentation of CoGe, and we will usually incorporate your questions into a tutorial or some other part of CoGepedia.