Difference between revisions of "Basics"

(Data representation/merging)
(Data representation)
Line 46: Line 46:
 
==Data representation==
 
==Data representation==
  
For working with data from multiple microarrays simultaneously, geWorkbench represents the entire dataset as a two-dimensional array of experiments and markers. This is also the file format that geWorkbench will save a microarray dataset to, and it is denoted by a file extension of .exp.  Such a representation can be created externally, for example in Excel, or geWorkbench can read in expression results from single arrays and merge them into the combined dataset.  This merging process is described in detail in the section [[Tutorial_-_Projects_and_Data_Files|Projects and Data Files]]. An option at the time of file read-in allows multiple files to be opened and merged simultaneously, either from disk or from remote data sources such as caArray.  Alternatively, single datasets that have already been read-in can also be merged at a later time.  Either route creates a single data object in the project folder representing all of the arrays.  This object can be viewed, for example, using the color mosaic component.
+
geWorkbench works on a single dataset at one time, as selected in the Project Folders.  For working with data from multiple microarrays simultaneously, for example for statistical analysis or clustering, all of the data must be represented as a single two-dimensional array of experiments and markers.   Such a representation can be created externally, for example in Excel, or geWorkbench can read in expression results from single arrays and merge them into a combined dataset.  The merging process is described in detail in the section [[Tutorial_-_Projects_and_Data_Files|Projects and Data Files]].  
 +
 
 +
An option at the time of file read-in allows multiple files to be opened and merged simultaneously, either from disk or from remote data sources such as caArray.  Alternatively, single datasets that have already been read-in can also be merged at a later time.  Either route creates a single data object in the project folder representing all of the arrays.  This object can be viewed, for example, using the color mosaic component.  The merged representation can be saved to the geWorkbench *.exp file type.
 +
 
 +
The results of any data analysis are stored in the Project Folders as a child of the dataset from which they were created.
  
 
==Limitations==
 
==Limitations==
  
 
As currently implemented, operations such as filtering and normalization are performed directly on the selected dataset.  A copy of the original is not made.
 
As currently implemented, operations such as filtering and normalization are performed directly on the selected dataset.  A copy of the original is not made.

Revision as of 16:27, 1 June 2006

Home | Quick Start | Basics | Menu Bar | Preferences | Component Configuration Manager | Workspace | Information Panel | Local Data Files | File Formats | caArray | Array Sets | Marker Sets | Microarray Dataset Viewers | Filtering | Normalization | Tutorial Data | geWorkbench-web Tutorials

Analysis Framework | ANOVA | ARACNe | BLAST | Cellular Networks KnowledgeBase | CeRNA/Hermes Query | Classification (KNN, WV) | Color Mosaic | Consensus Clustering | Cytoscape | Cupid | DeMAND | Expression Value Distribution | Fold-Change | Gene Ontology Term Analysis | Gene Ontology Viewer | GenomeSpace | genSpace | Grid Services | GSEA | Hierarchical Clustering | IDEA | Jmol | K-Means Clustering | LINCS Query | Marker Annotations | MarkUs | Master Regulator Analysis | (MRA-FET Method) | (MRA-MARINa Method) | MatrixREDUCE | MINDy | Pattern Discovery | PCA | Promoter Analysis | Pudge | SAM | Sequence Retriever | SkyBase | SkyLine | SOM | SVM | T-Test | Viper Analysis | Volcano Plot



Basic Layout of the Graphical User Interface

The graphical user interface for geWorkbench is divided into four major sections, for

1. Data management - Workspace and Projects (upper left)

2. Marker and Array/Phenotype set selection and management (lower left)

3. Visualization tools (upper right)

4. Analytical tools (lower right)


T geWorkbench1.0 all.png


Areas 2, 3 and 4 are defined for convenience. The actual placement of a given component into any of these three areas is controlled by a configuration file and can be customized as desired.

Data management area

Working with geWorkbench involves creating a project within the top-level workspace. Open data files and the results of data transformation or analysis are stored within a project. A workspace can contain more than one project at a time, allowing data to be organized as desired. A workspace and all the projects and data within it can be saved and later reloaded. These operations will be described in detail in further sections of the tutorials.

The GUI provides a menu bar at top with a standard choice of commands. Many commands that are available in the menu bar are also available by right-clicking on data objects.


Set selection and management

A key feature of geWorkbench is the ability to work with defined sets of markers or arrays. This allows subsets of data to be analyzed, and allows for passing of selected subsets of data between different components. For example, the t-test produces a list of markers showing a significant difference in expression between two states, and this list can then be used to retrieve relevant seqeunces or annotations.


Visualization and Analysis tools

geWorkbench works such that only the visualization and analysis components relevant to the type of dataset currently selected in the Project Folders area (1) are displayed through tabs in their respective areas (3 and 4). Thus choosing a microarray dataset will result in a different set of tabs being displayed as compared with those seen when a nucleotide sequence file is selected. When a new data file is loaded, or an analysis produces a new data set, not only is it added to the Project area (1), but an appropriate viewer in the Visualization area (3)is automatically selected.


Component Interoperability

The features described above underly the most important design goal of geWorkbench, which is to allow the different components to interoperate easily. The user is freed of the need to write programs to convert data from one format to another for different programs. Both the Project component (1) and the Set Selection component(2) can hold shared data. Typically each run of an analysis places either a new dataset into the active project, or a new set of markers or arrays into the Set Selection component. These are then available to any other appropriate component for reuse.


Data representation

geWorkbench works on a single dataset at one time, as selected in the Project Folders. For working with data from multiple microarrays simultaneously, for example for statistical analysis or clustering, all of the data must be represented as a single two-dimensional array of experiments and markers. Such a representation can be created externally, for example in Excel, or geWorkbench can read in expression results from single arrays and merge them into a combined dataset. The merging process is described in detail in the section Projects and Data Files.

An option at the time of file read-in allows multiple files to be opened and merged simultaneously, either from disk or from remote data sources such as caArray. Alternatively, single datasets that have already been read-in can also be merged at a later time. Either route creates a single data object in the project folder representing all of the arrays. This object can be viewed, for example, using the color mosaic component. The merged representation can be saved to the geWorkbench *.exp file type.

The results of any data analysis are stored in the Project Folders as a child of the dataset from which they were created.

Limitations

As currently implemented, operations such as filtering and normalization are performed directly on the selected dataset. A copy of the original is not made.