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
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
|
codcmp
Function
Codon usage table comparison
Description
This program reads in two codon usage table files.
It counts the number of the 64 possible codons which are unused (i.e.
has a usage fraction of 0) in either one or the other or both of the
codon usage tables.
The usage fraction of a codon is its proportion (0 to 1) of the total
of the codons in the sequences used to construct the usage table.
For each codon that is used in both tables, it takes the difference
between the usage fraction. The sum of the differences and the sum of
the differences squared is reported in the output file, together with
the number of unused codons.
Statistical significance
Question:
How do you interpret the statistical significance of any difference
between the tables?
Answer:
This is a very interesting question. I don't think that there is any
way to say if it is statistically significant just from looking at it,
as it is essentially a descriptive statistic about the difference
between two 64-mer vectors. If you have a whole lot of sequences and
codcmp results for all the possible pairwise comparisons, then the
resulting distance matrix can be used to build a phylogenetic tree
based on codon usage.
However, if you generate a series of random sequences, measure their
codon usage and then do codcmp between each of your test sequences and
all the random sequences, you could then use a z-test to see if the
result between the two test sequences was outside of the top or bottom
5%.
This would assume that the codcmp results were normally distributed,
but you could test that too. The simplest way is just to plot them and
look for a bell-curve. For more rigour, find the mean and standard
deviation of your results from the random sequences, use the normal
distribution equation to generate a theoretical distribution for that
mean and standard deviation, and then perform a chi square between the
random data and the theoretically generated normal distribution. If
you generate two sets of random data, each based on your two test
sequences, an F-test should be used to establish that they have equal
variances. Then you can safely go ahead and perform the z-test.
You could use shuffle to base your random sequences on the test
sequences - so that would ensure the randomised background had the
same nucleotide content.
F-tests, z-tests and chi-tests can all be done in Excel, as well as
being standard in most statistical analysis packages.
Answered by Derek Gatherer <d.gatherer vir.gla.ac.uk> 21 Nov 2003
Usage
Here is a sample session with codcmp
This compares the codon usage tables for Escherichia coli and
Haemophilus influenzae.
% codcmp
Codon usage table comparison
Codon usage file: Eecoli.cut
Second Codon usage file: Ehaein.cut
Output file [eecoli.codcmp]:
Go to the output files for this example
Command line arguments
Standard (Mandatory) qualifiers:
[-first] codon First codon usage file
[-second] codon Second codon usage file for comparison
[-outfile] outfile [*.codcmp] Output file name
Additional (Optional) qualifiers: (none)
Advanced (Unprompted) qualifiers: (none)
Associated qualifiers:
"-first" associated qualifiers
-format1 string Data format
"-second" associated qualifiers
-format2 string Data format
"-outfile" associated qualifiers
-odirectory3 string Output directory
General qualifiers:
-auto boolean Turn off prompts
-stdout boolean Write standard output
-filter boolean Read standard input, write standard output
-options boolean Prompt for standard and additional values
-debug boolean Write debug output to program.dbg
-verbose boolean Report some/full command line options
-help boolean Report command line options. More
information on associated and general
qualifiers can be found with -help -verbose
-warning boolean Report warnings
-error boolean Report errors
-fatal boolean Report fatal errors
-die boolean Report dying program messages
Input file format
It reads in the Codon Usage Tables - these are available as EMBOSS
data files. See below for details.
Output file format
Output files for usage example
File: eecoli.codcmp
# CODCMP codon usage table comparison
# Eecoli.cut vs Ehaein.cut
Sum Squared Difference = 2.178
Mean Squared Difference = 0.034
Root Mean Squared Difference = 0.184
Sum Difference = 9.504
Mean Difference = 0.149
Codons not appearing = 0
Data files
The codon usage tables are read by default from "Ehum.cut" in the
data/CODONS directory of the EMBOSS distribution.
If the name of a codon usage file is specified on the command line,
then this file will first be searched for in the current directory and
then in the 'data/CODONS' directory of the EMBOSS distribution.
EMBOSS data files are distributed with the application and stored in
the standard EMBOSS data directory, which is defined by the EMBOSS
environment variable EMBOSS_DATA.
To see the available EMBOSS data files, run:
% embossdata -showall
To fetch one of the data files (for example 'Exxx.dat') into your
current directory for you to inspect or modify, run:
% embossdata -fetch -file Exxx.dat
Users can provide their own data files in their own directories.
Project specific files can be put in the current directory, or for
tidier directory listings in a subdirectory called ".embossdata".
Files for all EMBOSS runs can be put in the user's home directory, or
again in a subdirectory called ".embossdata".
The directories are searched in the following order:
* . (your current directory)
* .embossdata (under your current directory)
* ~/ (your home directory)
* ~/.embossdata
Notes
None.
References
None.
Warnings
None.
Diagnostic Error Messages
None.
Exit status
This program always exits with a status of 0.
Known bugs
None.
See also
Program name Description
cai CAI codon adaptation index
chips Codon usage statistics
cusp Create a codon usage table
syco Synonymous codon usage Gribskov statistic plot
Author(s)
Alan Bleasby (ajb ebi.ac.uk)
European Bioinformatics Institute, Wellcome Trust Genome Campus,
Hinxton, Cambridge CB10 1SD, UK
Some more statistics were added by David Martin
(dmartin rfcgr.mrc.ac.uk)
History
Completed 9 Sept 1999
20 Oct 2000 - David Martin added a couple more statistics to the
output.
Target users
This program is intended to be used by everyone and everything, from
naive users to embedded scripts.
Comments
None
|
