[ Program Manual | User's Guide | Data Files | Databases ]
GelView displays the structure of the contigs in a fragment assembly project.
See the Fragment Assembly System (FAS) Introduction for an overview of working with the programs within the FAS to assemble sequences in a sequencing project.
GelView makes a display of your fragment assembly project. A list of the fragments in each contig, along with a bar diagram representing the position, length, and orientation of each fragment, allows you to review the current status of your sequencing project.
Here is a session using GelView to look at the contigs in "myproject." This project was created in the example sessions of GelStart, GelEnter, and GelMerge.
% gelview What should I call the output file (* myproject.view *) ? MYPROJECT has 12 Fragments in 3 Contigs %
GELVIEW Fragment Assembly contig display of Project: myproject
September 17, 1996 10:34
Contig: mu2
3 mu23 +--------------------------->
2 mu2 +----------------------------------->
C CONSENSUS +----------------------------------->
|----------|----------|----------|---------|---------|
0 100 200 300 400
Contig: Mu26b
8 mu18b +--------------------->
7 mu9 <---+
6 mu32 +--->
5 mu26 <----+
4 mu18 +---->
3 mu27 <--------------------------------+
2 mu26b <------------------+
C CONSENSUS <-----------------------------------------------+
|----------|----------|----------|---------|---------|
0 100 200 300 400
Contig: mu5
4 mu6 <--------------------------------+
3 mu10 +--------------------------------------->
2 mu5 <------------------------+
C CONSENSUS <--------------------------------------------+
|----------|----------|----------|---------|---------|
0 100 200 300 400
12 Fragments in 3 Contigs
GelStart begins a fragment assembly session by creating a new fragment assembly project or by identifying an existing project. GelEnter adds fragment sequences to a fragment assembly project. It accepts sequence data from your terminal keyboard, a digitizer, or existing sequence files. GelMerge aligns the sequences in a fragment assembly project into assemblies called contigs. You can view and edit these assemblies in GelAssemble. GelAssemble is a multiple sequence editor for viewing and editing contigs assembled by GelMerge. GelView displays the structure of the contigs in a fragment assembly project. GelDisassemble breaks up the contigs in a fragment assembly project into single fragments.
A contig may not contain more than 1,650 fragments and may not be longer than 100,000 bases. No single fragment may be longer than 2,500 bases. Longer fragments and a larger number of fragments can be managed by the Fragment Assembly System if your system manager modifies the fragment assembly programs .
All parameters for this program may be put on the command line. Use the parameter -CHEck to see the summary below and to have a chance to add things to the command line before the program executes. In the summary below, the capitalized letters in the parameter names are the letters that you must type in order to use the parameter. Square brackets ([ and ]) enclose parameter values that are optional. For more information, see "Using Program Parameters" in Chapter 3, Using Programs in the User's Guide.
Minimal Syntax: % gelview -Default Prompted Parameters: [-OUTfile=]myproject.view output file name Local Data Files: None Optional Parameters: -NOBAR suppresses the fragment bar diagrams
None.
The parameters listed below can be set from the command line. For more information, see "Using Program Parameters" in Chapter 3, Using Programs in the User's Guide.
suppresses the bar diagram associated with each fragment name.
[ Program Manual | User's Guide | Data Files | Databases ]
Documentation Comments: doc-comments@gcg.com
Technical Support: help@gcg.com
Copyright (c) 1982, 1983, 1985, 1986, 1987, 1989, 1991, 1994, 1995, 1996 Gentics Computer Group, Inc. All rights reserved.
Licenses and Trademarks Wisconsin Package is a trademark of Genetics Computer Group, Inc. GCG and the GCG logo are registered trademarks of Genetics Computer Group, Inc.
All other product names mentioned in this documentation may be trademarks, and if so, are trademarks or registered trademarks of their respective holders and are used in this documentation for identification purposes only.