1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
.TH "LONG-ORFS" "1"
.SH "NAME"
long-orfs \(em Find/Score potential genes in genome-file using
the probability model in icm-file
.SH "SYNOPSIS"
.PP
\fBtigr-long-orgs\fR [genome-file \fB\fIoptions\fR\fP]
.SH "DESCRIPTION"
.PP
Program long-orfs takes a sequence file (in FASTA format) and
outputs a list of all long "potential genes" in it that do not
overlap by too much. By "potential gene" I mean the portion of
an orf from the first start codon to the stop codon at the end.
.PP
The first few lines of output specify the settings of various
parameters in the program:
.PP
Minimum gene length is the length of the smallest fragment
considered to be a gene. The length is measured from the first base
of the start codon to the last base *before* the stop codon.
This value can be specified when running the program with the \-g option.
By default, the program now (April 2003) will compute an optimal length
for this parameter, where "optimal" is the value that produces the
greatest number of long ORFs, thereby increasing the amount of data
used for training.
.PP
Minimum overlap length is a lower bound on the number of bases overlap
between 2 genes that is considered a problem. Overlaps shorter than
this are ignored.
.PP
Minimum overlap percent is another lower bound on the number of bases
overlap that is considered a problem. Overlaps shorter than this
percentage of *both* genes are ignored.
.PP
The next portion of the output is a list of potential genes:
.PP
Column 1 is an ID number for reference purposes. It is assigned
sequentially starting with 1 to all long potential genes. If
overlapping genes are eliminated, gaps in the numbers will occur.
The ID prefix is specified in the constant ID_PREFIX .
.PP
Column 2 is the position of the first base of the first start codon in
the orf. Currently I use atg, and gtg as start codons. This is
easily changed in the function Is_Start () .
.PP
Column 3 is the position of the last base *before* the stop codon. Stop
codons are taa, tag, and tga. Note that for orfs in the reverse
reading frames have their start position higher than the end position.
The order in which orfs are listed is in increasing order by
Max {OrfStart, End}, i.e., the highest numbered position in the orf,
except for orfs that "wrap around" the end of the sequence.
.PP
When two genes with ID numbers overlap by at least a sufficient
amount (as determined by Min_Olap and Min_Olap_Percent ), they
are eliminated and do not appear in the output.
.PP
The final output of the program (sent to the standard error file so
it does not show up when output is redirected to a file) is the
length of the longest orf found.
.PP
Specifying Different Start and Stop Codons:
.PP
To specify different sets of start and stop codons, modify the file
gene.h . Specifically, the functions:
.PP
Is_Forward_Start Is_Reverse_Start Is_Start
Is_Forward_Stop Is_Reverse_Stop Is_Stop
.PP
are used to determine what is used for start and stop codons.
.PP
Is_Start and Is_Stop do simple string comparisons to specify
which patterns are used. To add a new pattern, just add the comparison
for it. To remove a pattern, comment out or delete the comparison
for it.
.PP
The other four functions use a bit comparison to determine start and
stop patterns. They represent a codon as a 12-bit pattern, with 4 bits
for each base, one bit for each possible value of the bases, T, G, C
or A. Thus the bit pattern 0010 0101 1100 represents the base
pattern [C] [A or G] [G or T]. By doing bit operations (& | ~) and
comparisons, more complicated patterns involving ambiguous reads
can be tested efficiently. Simple patterns can be tested as in
the current code.
.PP
For example, to insert an additional start codon of CAT requires 3 changes:
1. The line
|| (Codon & 0x218) == Codon
should be inserted into Is_Forward_Start , since 0x218 = 0010 0001 1000
represents CAT.
2. The line
|| (Codon & 0x184) == Codon
should be inserted into Is_Reverse_Start , since 0x184 = 0001 1000 0100
represents ATG, which is the reverse-complement of CAT. Alternately,
the #define constant ATG_MASK could be used.
3. The line
|| strncmp (S, "cat", 3) == 0
should be inserted into Is_Start .
.SH "OPTIONS"
.IP "\fB-g \fIn\fR\fP" 10
Set minimum gene length to n. Default is to compute an
optimal value automatically. Don't change this unless you
know what you're doing.
.IP "\fB-l\fP" 10
Regard the genome as linear (not circular), i.e., do not allow
genes to "wrap around" the end of the genome.
This option works on both glimmer and long-orfs .
The default behavior is to regard the genome as circular.
.IP "\fB-o \fIn\fR\fP" 10
Set maximum overlap length to n. Overlaps shorter than this
are permitted. (Default is 0 bp.)
.IP "\fB-p \fIn\fR\fP" 10
Set maximum overlap percentage to n%. Overlaps shorter than
this percentage of *both* strings are ignored. (Default is 10%.)
.SH "SEE ALSO"
.PP
tigr-glimmer3 (1),
tigr-adjust (1),
tigr-anomaly (1),
tigr-build-icm (1),
tigr-check (1),
tigr-codon-usage (1),
tigr-compare-lists (1),
tigr-extract (1),
tigr-generate (1),
tigr-get-len (1),
tigr-get-putative (1),
.PP
http://www.tigr.org/software/glimmer/
.PP
Please see the readme in /usr/share/doc/tigr-glimmer for a description on how to use Glimmer3.
.SH "AUTHOR"
.PP
This manual page was quickly copied from the glimmer web site by Steffen Moeller moeller@debian.org for
the \fBDebian\fP system.
.\" created by instant / docbook-to-man
|
