Debian Codegraph @

docs/web/examples/index.html

raw ◀ ▶
Source reconstructed at patch state 0 of 1 — not the installed (fully patched) source.
1 Debian patch touch this file
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2 <html>
3 <head>
4 <title>The MUMmer 3 examples</title>
5 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
6 <style type="text/css">
7 <!--
8 body {
9 background-color: #FFFFFF;
10 }
11 h2 {
12 background-color: #BBBBFF;
13 font-style: italic;
14 }
15 h3 {
16 background-color: #CDCDEE;
17 }
18 h4 {
19 background-color: #EFEFEF;
20 }
21 code {
22 color: #CC0000;
23 }
24 td {
25 vertical-align: top;
26 }
27 .centered {
28 text-align: center;
29 }
30 -->
31 </style>
32 </head>
33
34 <body>
35 <p><img src="examples_logo.gif" alt="MUMmer 3 manual logo" border="0"></p>
36 <hr>
37 <h2>Table of Contents</h2>
38 <ol>
39 <li><a href="#introduction">Introduction</a></li>
40 <li><a href="#examples">Examples</a>
41 <ol>
42 <li><a href="#mapview">mapview</a>
43 <ol>
44 <li><a href="#promermapview">Running promer</a></li>
45 <li><a href="#mapviewmapview">Running mapview</a></li>
46 <li><a href="#outputmapview">Viewing the output</a></li>
47 </ol>
48 </li>
49 <li><a href="#mummer">mummer</a>
50 <ol>
51 <li><a href="#mummermummer">Running mummer</a></li>
52 <li><a href="#mummerplotmummer">Running mummerplot</a></li>
53 <li><a href="#outputmummer">Viewing the output</a></li>
54 </ol>
55 </li>
56 <li><a href="#nucmer">nucmer</a>
57 <ol>
58 <li><a href="#nucmernucmer">Running nucmer</a></li>
59 <li><a href="#showcoordsnucmer">Running show-coords</a></li>
60 <li><a href="#showsnpsnucmer">Running show-snps</a></li>
61 <li><a href="#showtilingnucmer">Running show-tiling</a></li>
62 <li><a href="#outputnucmer">Viewing the output</a></li>
63 </ol>
64 </li>
65 <li><a href="#promer">promer</a>
66 <ol>
67 <li><a href="#promerpromer">Running promer</a></li>
68 <li><a href="#showcoordspromer">Running show-coords</a></li>
69 <li><a href="#showalignspromer">Running show-aligns</a></li>
70 <li><a href="#outputpromer">Viewing the output</a></li>
71 </ol>
72 </li>
73 <li><a href="#mummer1">run-mummer1</a>
74 <ol>
75 <li><a href="#runmummer1runmummer1">Running run-mummer1</a></li>
76 <li><a href="#outputrunmummer1">Viewing the output</a></li>
77 </ol>
78 </li>
79 <li><a href="#mummer3">run-mummer3</a>
80 <ol>
81 <li><a href="#runmummer3runmummer3">Running run-mummer3</a></li>
82 <li><a href="#outputrunmummer3">Viewing the output</a></li>
83 </ol>
84 </li>
85 </ol>
86 </li>
87 <li><a href="#contact">Contact information</a></li>
88 </ol>
89 <hr width="100%">
90 <h2><a name="introduction"></a>1. Introduction</h2>
91 <p>Because of its breadth MUMmer can, at first glance, be an overwhelming sea
92 of scripts and subroutines. This document attempts to walk the user through
93 some of the more useful modules of the package, and provides example data and
94 expected outputs to assure the correct and productive operation of MUMmer. All
95 example data is real DNA sequence from various eukaryotic and prokaryotic organisms,
96 and can be found in its entirety in the <a href="data">data directory</a>. Although
97 the input sequences are only subsections of their respective genomes, they have
98 been carefully selected to permit speedy and informative walk-throughs. It is
99 not necessary to download all of the data at once, as each subsection will have
100 separate links to the relevant files.</p>
101 <p>For further information regarding any of the MUMmer programs or their output
102 formats, please refer to the online <a href="../manual">MUMmer manual</a>.</p>
103 <hr>
104 <h2><a name="examples"></a>2. Examples</h2>
105 <h3><a name="mapview"></a>2.1. mapview</h3>
106 <p>MapView is a utility script for displaying sequence alignments as provided
107 by NUCmer or PROmer. It takes the output from <code>show-coords</code> and converts
108 it to a FIG, PDF or PS image file. By default, it produces FIG files which can
109 be viewed with the common system utility <code>xfig</code> or converted to PDF
110 or PS with the <code>fig2dev</code> utility (neither programs are included with
111 MUMmer). <code>mapview</code> is useful for mapping multiple query contigs (e.g.
112 from a draft sequencing project) against an annotated reference sequence. Exons
113 and other features can also be plotted with the NUCmer or PROmer alignments,
114 aiding in exon refinement and analysis. Individual MUMmer hits are plotted according
115 to their percent identity, making regions of high or low similarity easily distinguishable.</p>
116 <p>In the following sections, a short example is given that demonstrates how to
117 use <code>mapview</code>. Since <code>nucmer</code> and <code>promer</code>
118 have a near identical user interface, the alignments for this example will be
119 generated using <code>promer</code>. This example aligns a few query sequences
120 to a single reference sequence using <code>promer</code>, and then uses <code>mapview</code>
121 to plot the resulting areas of conservation and the reference sequence annotation.</p>
122 <h5>The following input files will be used to demonstrate this example:</h5>
123 <ul>
124 <li><code><a href="data/D_melanogaster_2Rslice.cds">D_melanogaster_2Rslice.cds</a></code></li>
125 <li><code><a href="data/D_melanogaster_2Rslice.fasta">D_melanogaster_2Rslice.fasta</a></code></li>
126 <li><code><a href="data/D_melanogaster_2Rslice.utr">D_melanogaster_2Rslice.utr</a></code></li>
127 <li><code><a href="data/D_pseudoobscura_contigs.fasta">D_pseudoobscura_contigs.fasta</a></code></li>
128 </ul>
129 <h5>The following output files will be generated by this example:</h5>
130 <ul>
131 <li><code><a href="data/mapview_0.fig">mapview_0.fig</a></code></li>
132 <li><code><a href="data/mapview_0.pdf">mapview_0.pdf</a></code></li>
133 <li><code><a href="data/promer.coords">promer.coords</a></code></li>
134 </ul>
135 <h4><a name="promermapview" id="promermapview"></a>2.1.1. Running promer</h4>
136 <p>Please complete the <a href="#promer">PROmer walk-though</a> in order to generate
137 the alignment between the <em>Drosophila melanogaster</em> chromosome 2R segment
138 and the 2 contigs from <em>Drosophila pseudoobscura</em>. The PROmer walk-through
139 will generate the <code>.coords </code>file that is necessary to continue with
140 the rest of this tutorial. If already familiar with the <code>promer</code>
141 alignment script, simply continue this tutorial using the supplied <code>promer.coords</code>
142 file. Note that when generating the <code>.coords</code> file with <code>show-coords</code>
143 it is important to use the <code>-l -r</code> options (and optionally the <code>-k</code>
144 option) in order to generate the proper input format for <code>mapview</code>.</p>
145 <h4><a name="mapviewmapview" id="mapviewmapview"></a>2.1.2. Running mapview</h4>
146 <p>The output of <code>show-coords</code> is then used by MapView to create a
147 FIG, PDF or PS file.</p>
148 <p><code>mapview -n 1 -p mapview promer.coords </code></p>
149 <p>The <code>-n</code> option is used to set the number of output files to 1.
150 By default, MapView partitions its output among 10 files in order to keep the
151 figures for large comparisons small. Since we are only comparing a small slice
152 of the actual chromosome, only 1 file will be needed. The output of this command
153 will be a single file named <code>mapview_0.fig</code>. A more informative plot
154 can be generated by supplying a UTR and CDS coordinate file in <a href="http://www.sanger.ac.uk/Software/formats/GFF/">GFF
155 format</a>. These files contain annotation information that will be plotted
156 along side the PROmer alignments, thus making it possible to compare the conserved
157 regions with annotated exon positions.</p>
158 <p><code>mapview -n 1 -p mapview promer.coords D_melanogaster_2Rslice.utr D_melanogaster_2Rslice.cds</code></p>
159 <p>This will generate a single file, <code>mapview_0.fig</code>, that will have
160 the annotation information displayed above the blue reference rectangle. Below,
161 you can see this file displayed with the xfig viewer. The only difference between
162 this file and the file produced without the UTR and CDS files are the annotation
163 rectangles above the blue rectangle at the very top of the figure. </p>
164 <div class="centered"> <img src="mapview_fig.jpg" alt="mapview xfig" name="mapview_fig" id="mapview_fig">
165 </div>
166 <p>In order to generate a PDF format, use the same command plus the <code>-f pdf</code>
167 option.</p>
168 <p><code>mapview -n 1 -f pdf -p mapview promer.coords D_melanogaster_2Rslice.utr
169 D_melanogaster_2Rslice.cds</code> </p>
170 <p>This will generate the same image, <code>mapview_0.pdf</code>, but in PDF format.</p>
171 <h4><a name="outputmapview" id="outputmapview"></a>2.1.3. Viewing the output</h4>
172 <div class="centered"> <img src="mapplot.gif" alt="mapview plot example" name="mapplot" id="mapplot">
173 </div>
174 <p>The above MapView FIG shows a 220 kbp slice of <em>D. melanogaster</em> chromosome
175 2L and its alignment to <em>D. pseudoobscura.</em> The alignment, generated
176 by PROmer, shows all regions of conserved amino acid sequence. The blue rectangle
177 spanning the figure represents the reference (<em>D. melanogaster</em>), with
178 annotated genes shown above it and the PROmer alignments shown below it. Alternative
179 splice variants of the same gene are stacked vertically. Exons are shown as
180 boxes, with intervening introns connecting them. The 5' and 3' UTRs are colored
181 pink and blue to indicate the gene's direction of translation. PROmer matches
182 are shown twice, once just below the reference genome, where all matches are
183 collapsed into red boxes, and in a larger display showing the separate matches
184 within each contig, where the contigs are colored differently to indicate contig
185 boundaries. The vertical position of the matches indicates their percent identity,
186 ranging from 50% at the bottom of the display to 100% just below the red rectangles.
187 Percent identity is of the amino acid translations used by PROmer. Matches from
188 the same query sequence are connected by lines of the same color.</p>
189 <h3><a name="mummer"></a>2.2. mummer</h3>
190 <p><code>mummer</code> is a suffix tree algorithm designed to find maximal exact
191 matches of some minimum length between two input sequences. The match lists
192 produced by <code>mummer</code> can be used alone to generate alignment dot
193 plots, or can be passed on to the clustering algorithms for the identification
194 of longer non-exact regions of conservation. These match lists have great versatility
195 because they contain huge amounts of information and can be passed forward to
196 other interpretation programs for clustering, analysis, searching, etc.</p>
197 <p>In the following sections, a short example is given that demonstrates how to
198 use <code>mummer</code>. This example compares a single query sequence to a
199 single reference sequence using <code>mummer</code>, and then uses <code>mummerplot</code>
200 to generate a dot plot representation of the comparison.</p>
201 <h5>The following input files will be used to demonstrate this example:</h5>
202 <ul>
203 <li><code><a href="data/H_pylori26695_Eslice.fasta">H_pylori26695_Eslice.fasta</a></code></li>
204 <li><code><a href="data/H_pyloriJ99_Eslice.fasta">H_pyloriJ99_Eslice.fasta</a></code></li>
205 </ul>
206 <h5>The following output files will be generated by this example:</h5>
207 <ul>
208 <li><code><a href="data/mummer.gp">mummer.gp</a></code></li>
209 <li><code><a href="data/mummer.mums">mummer.mums</a></code></li>
210 <li><code><a href="data/mummer.fplot">mummer.fplot</a></code></li>
211 <li><code><a href="data/mummer.rplot">mummer.rplot</a></code></li>
212 <li><code><a href="data/mummer.ps">mummer.ps</a></code></li>
213 </ul>
214 <h4><a name="mummermummer" id="mummermummer"></a>2.2.1. Running mummer</h4>
215 <p><code>mummer</code> can handle multiple reference and multiple query sequences,
216 however a dotplot of more that two sequences can be confusing, so for the case
217 of this example we will be dealing with a single reference and a single query
218 sequence.</p>
219 <p><code>mummer -mum -b -c H_pylori26695_Eslice.fasta H_pyloriJ99_Eslice.fasta
220 &gt; mummer.mums</code></p>
221 <p>This command will find all maximal unique matches (<code>-mum</code>) between
222 the reference and query on both the forward and reverse strands (<code>-b</code>)
223 and report all the match positions relative to the forward strand (<code>-c</code>).
224 Output is to <code>stdout</code>, so we will redirect it into a file named <code>mummer.mums</code>.
225 This file lists all of the MUMs of the default length or greater between the
226 two input sequences.</p>
227 <h4><a name="mummerplotmummer" id="mummerplotmummer"></a>2.2.2. Running mummerplot</h4>
228 <p>A dotplot of all the MUMs between two sequences can reveal their macroscopic
229 similarity.</p>
230 <p><code>mummerplot -x &quot;[0,275287]&quot; -y &quot;[0,265111]&quot; -postscript
231 -p mummer mummer.mums</code></p>
232 <p>This command will plot all of the MUMs in the <code>mummer.mums</code> file
233 in postscript format (<code>-postscript</code>) between the given ranges for
234 the X and Y axes. When plotting <code>mummer</code> output, it is necessary
235 to use the lengths of the input sequences to set the plot ranges, otherwise
236 the plot will be automatically scaled around the minimum and maximum data points.
237 The four output files are prefixed by the string specified with the <code>-p</code>
238 option. The <code>plot</code> files contains the data points, <code>mummer.gp</code>
239 is a gnuplot script for plotting the data points in the <code>plot</code> files,
240 and <code>mummer.ps</code> is the postscript plot generated by the gnuplot script.
241 Below, you can see the <code>mummer.ps</code> file displayed with ghostview.
242 Note that with newer versions of <code>mummerplot</code> the color and thickness
243 of the plot lines may be different.</p>
244 <div class="centered"> <img src="mummer_ps.jpg" alt="mummer postscript plot" name="mummer_ps" id="mummer_ps">
245 </div>
246 <p> Most image manipulation programs can edit the postscript output, or it can
247 be sent directly to a printer with the <code>lpr</code> command. If you would
248 rather use the default terminal for gnuplot, simply remove the <code>-postscript</code>
249 option from the <code>mummerplot</code> call.</p>
250 <h4><a name="outputmummer" id="outputmummer"></a>2.2.3. Viewing the output</h4>
251 <div class="centered"> <img src="dotplot.gif" alt="mummerplot example" name="dotplot" id="dotplot">
252 </div>
253 <p>The above postscript plot represents the set of all MUMs between the two input
254 sequences used in this example. Forward MUMs are plotted as red lines/dots while
255 reverse MUMs are plotted as green lines/dots (blue may be used for reverse matches
256 in newer versions). A line of dots with slope == 1 represents an undisturbed
257 segment of conservation between the two sequences, while a line of slope ==
258 -1 represents an inverted segment of conservation between the two sequences.
259 The green segment in the upper left quadrant of the graph shows both an inversion
260 and translocation, as it is of negative slope and inconsistently located relative
261 to the rest of the plot which falls on a line approximated by f(x) = x. However
262 the green segment in the upper right quadrant of the graph shows only an inversion,
263 as it is of negative slope but is consistent in location with the rest of the
264 plot. Generally, the closer a plot is to an imaginary line f(x) = x (or -x)
265 the fewer macroscopic differences exist between the two sequences.</p>
266 <h3><a name="nucmer"></a>2.3. nucmer</h3>
267 <p><code>nucmer</code> is the MUMmer's most user-friendly alignment script for
268 standard DNA sequence alignment. It is a robust pipeline that allows for multiple
269 reference and multiple query sequences to be aligned in a many vs. many fashion.
270 For instance, a very common use for <code>nucmer</code> is to determine the
271 position and orientation of a set of sequence contigs in relation to a finished
272 sequence, however it can be just as effective in comparing two finished sequences
273 to one another.</p>
274 <p>In the following sections, a short example is given that demonstrates how to
275 use <code>nucmer</code>. This example aligns a set of draft sequence contigs
276 to a finished sequence using <code>nucmer</code>; displays the alignment coordinates
277 using <code>show-coords</code>; and tiles them across the reference using <code>show-tiling</code>.</p>
278 <h5>The following input files will be used to demonstrate this example:</h5>
279 <ul>
280 <li><code><a href="data/B_anthracis_Mslice.fasta">B_anthracis_Mslice.fasta</a></code></li>
281 <li><code><a href="data/B_anthracis_contigs.fasta">B_anthracis_contigs.fasta</a></code></li>
282 </ul>
283 <h5>The following output files will be generated by this example:</h5>
284 <ul>
285 <li><code><a href="data/nucmer.coords">nucmer.coords</a></code></li>
286 <li><code><a href="data/nucmer.delta">nucmer.delta</a></code></li>
287 <li><code><a href="data/nucmer.snps">nucmer.snps</a></code></li>
288 <li><code><a href="data/nucmer.tiling">nucmer.tiling</a></code></li>
289 </ul>
290 <h4><a name="nucmernucmer"></a>2.3.1. Running nucmer</h4>
291 <p>Like <code>mummer</code>, <code>nucmer</code> can handle multiple reference
292 and query sequences, however it is most commonly used to map a set of query
293 sequences to a single reference sequence. This example will demonstrate that
294 functionality, as a number of <em>B. anthracis</em> draft contigs will be mapped
295 to the final assembly.</p>
296 <p><code>nucmer -maxmatch -c 100 -p nucmer B_anthracis_Mslice.fasta B_anthracis_contigs.fasta</code></p>
297 <p>To assure all contigs were mapped, all maximal matches were used as alignment
298 anchors (<code>-maxmatch</code>) and because of the sequence similarity the
299 minimum cluster size was bumped up to 100 (<code>-c 100</code>). The two output
300 files are prefixed by the string specified with the <code>-p</code> option.
301 <code>nucmer.delta</code> is an
302 encoded file that represents the alignment between the two inputs. At this stage,
303 the alignment of the two inputs is complete, however it is necessary to parse
304 the <code>nucmer.delta</code> file with the provided utilities in order to extract
305 useful information from the comparison.</p>
306 <h4><a name="showcoordsnucmer"></a>2.3.2. Running show-coords</h4>
307 <p>To view a summary of all the alignments produced by NUCmer, we need to run
308 the <code>nucmer.delta</code> file through the <code>show-coords</code> utility.</p>
309 <p><code>show-coords -r -c -l nucmer.delta &gt; nucmer.coords</code></p>
310 <p>This command will list the coordinates, percent identities and other useful
311 statistics of each alignment in a table. Each line of the table represents an
312 individual pairwise alignment, and each line is sorted by its starting reference
313 coordinate (<code>-r</code>). Additional information, like alignment coverage
314 (<code>-c</code>) and sequence length (<code>-l</code>) can be added to the
315 table with the appropriate options. Output is to <code>stdout</code>, so we
316 have redirected it into the file, <code>nucmer.coords</code>.</p>
317 <h4><a name="showsnpsnucmer" id="showsnpsnucmer"></a>2.3.4. Running show-snps</h4>
318 <p>To view a summary of all the SNPs and indels between the two sequence sets,
319 we need to run the <code>nucmer.delta</code> file through the <code>show-snps</code>
320 utility.</p>
321 <p><code>show-snps -C nucmer.delta &gt; nucmer.snps</code></p>
322 <p>This will generate a report of all the SNPs internal to the alignments contained
323 in the <code>nucmer.delta</code> file. Each line of the table represents a single
324 mismatch in the pairwise alignment. With the <code>-C</code> option, only SNPs
325 from uniquely aligned regions will be reported. Additional information can be
326 added or removed with the command line switches described in the manual. Output
327 is to <code>stdout</code>, so we have redirected it into the file, <code>nucmer.snps</code>.</p>
328 <h4><a name="showtilingnucmer"></a>2.3.5. Running show-tiling</h4>
329 <p>To produce a minimal tiling of contigs across the reference sequence, we need
330 to run the <code>nucmer.delta</code> file through the <code>show-tiling</code>
331 utility.</p>
332 <p><code>show-tiling nucmer.delta &gt; nucmer.tiling</code></p>
333 <p>This command will list the contigs and positions that generate the maximal
334 alignment coverage across the reference sequence using the fewest contigs possible.
335 This output can aid the closure of a draft genome when a closely related organism
336 has already be finished.</p>
337 <h4><a name="outputnucmer"></a>2.3.6. Viewing the output</h4>
338 <p><code>nucmer</code> and <code>show-tiling</code> output can both be viewed
339 with <code>mummerplot</code>, however these plots would offer little more information
340 in regards to this example. <code>mapview</code> can also be used to display
341 the output of <code>show-coords</code>, as is shown in the <a href="#mapview">mapview
342 walkthrough</a>.</p>
343 <h3><a name="promer"></a>2.4. promer</h3>
344 <p><code>promer</code> is a close relative to the NUCmer script. It follows the
345 exact same steps as NUCmer and even uses most of the same programs in its pipeline,
346 with one exception - all matching and alignment routines are performed on the
347 six frame amino acid translation of the DNA input sequence. This provides <code>promer</code>
348 with a much higher sensitivity than <code>nucmer</code> because protein sequences
349 tends to diverge much slower than their underlying DNA sequence. Therefore,
350 on the same input sequences, <code>promer</code> may find many conserved regions
351 that <code>nucmer</code> will not, simply because the DNA sequence is not as
352 highly conserved as the amino acid translation.</p>
353 <p>In the following sections, a short example is given that demonstrates how to
354 use <code>promer</code>. This example aligns a few query sequences to single
355 reference sequence using <code>promer</code>; displays the alignment coordinates
356 using <code>show-coords</code>; and prints a pairwise alignment of one of the
357 contigs using <code>show-aligns</code>.</p>
358 <h5>The following input files will be used to demonstrate this example:</h5>
359 <ul>
360 <li><code><a href="data/D_melanogaster_2Rslice.fasta">D_melanogaster_2Rslice.fasta</a></code></li>
361 <li><code><a href="data/D_pseudoobscura_contigs.fasta">D_pseudoobscura_contigs.fasta</a></code></li>
362 </ul>
363 <h5>The following output files will be generated by this example:</h5>
364 <ul>
365 <li><code><a href="data/promer.aligns">promer.aligns</a></code></li>
366 <li><code><a href="data/promer.coords">promer.coords</a></code></li>
367 <li><code><a href="data/promer.delta">promer.delta</a></code></li>
368 </ul>
369 <h4><a name="promerpromer" id="promerpromer"></a>2.4.1. Running promer</h4>
370 <p>Like <code>mummer</code>, <code>promer</code> can handle multiple reference
371 and query sequences, however it is most commonly used to map a set of query
372 sequences to a single reference sequence. This example will demonstrate that
373 functionality, as two <em>D. pseudoobscura</em> draft contigs will be mapped
374 to the final <em>D. melanogaster</em> assembly.</p>
375 <p><code>promer -p promer D_melanogaster_2Rslice.fasta D_pseudoobscura_contigs.fasta</code></p>
376 <p>Default parameters were used to align the two inputs, however if the alignment
377 is too sensitive or not sensitive enough the minimum match length and cluster
378 sizes can be adjusted accordingly. The two output files are prefixed by the
379 string specified with the <code>-p</code> option. <code>promer.delta</code> is an encoded file that represents
380 the alignment between the two inputs. At this stage, the alignment of the two
381 inputs is complete, however it is necessary to parse the <code>promer.delta</code>
382 file with the provided utilities in order to extract useful information from
383 the comparison.</p>
384 <h4><a name="showcoordspromer" id="showcoordspromer"></a>2.4.2. Running show-coords</h4>
385 <p>To view a summary of all the alignments produced by PROmer, we need to run
386 the <code>promer.delta</code> file through the <code>show-coords</code> utility.</p>
387 <p><code>show-coords -r -c -l -L 100 -I 50 promer.delta &gt; promer.coords</code></p>
388 <p>This command will list the coordinates, percent identities and other useful
389 statistics of each alignment in a table. Each line of the table represents an
390 individual pairwise alignment, and each line is sorted by its starting reference
391 coordinate (<code>-r</code>). Additional information, like alignment coverage
392 (<code>-c</code>) and sequence length (<code>-l</code>) can be added to the
393 table with the appropriate options. And minimum length (<code>-L</code>) and
394 minimum percent identity (<code>-I</code>) cutoffs can be specified to reduce
395 poor alignments. Output is to <code>stdout</code>, so we have redirected it
396 into the file, <code>promer.coords</code>. If this file is planned for input
397 to <code>mapview</code>, it is important to always use the <code>-r</code> <code>-c</code>
398 <code>-l</code> options.</p>
399 <h4><a name="showalignspromer" id="showalignspromer"></a>2.4.3. Running show-aligns</h4>
400 <p>To view all the pairwise alignments between two of the input sequences, we
401 need to run the <code>promer.delta</code> file through the <code>show-coords</code>
402 utility. </p>
403 <p><code>show-aligns promer.delta &quot;D_melanogaster_2Rslice&quot; &quot;3214968&quot;
404 &gt; promer.aligns</code></p>
405 <p>This command will print all of the pairwise alignments stored in the <code>promer.delta</code>
406 file for the sequences &quot;D_melanogaster_2Rslice&quot; and &quot;3214968&quot;.
407 Output is to <code>stdout</code>, so we have redirected it into the file, <code>promer.aligns</code>.
408 If the alignments do not fit within your screen width, or you would like them
409 to be printed on longer lines, the screen width can be adjusted with the <code>-w</code>
410 option. Since <code>show-aligns</code> only displays the alignments between
411 two sequences, it will have to be run separately for each desired pair of sequences.</p>
412 <h4><a name="outputpromer" id="outputpromer"></a>2.4.4. Viewing the output</h4>
413 <p><code>promer</code> and <code>show-tiling</code> output can both be viewed
414 with <code>mummerplot</code>, however these plots would offer little more information
415 in regards to this example. <code>mapview</code> can also be used to display
416 the output of <code>show-coords</code>, as is shown in the <a href="#mapview">mapview
417 walkthrough</a> which uses the <code>promer.coords</code> file generated in
418 this example to generate a plot of the alignment.</p>
419 <h3><a name="mummer1"></a>2.5. run-mummer1</h3>
420 <p><code>run-mummer1</code> is a legacy script from the original MUMmer1.0 release.
421 It has been updated to utilize the new suffix tree code of version 3.0, however
422 all other programs called from this script are identical to the original MUMmer
423 release back in 1999. Even though it is an outdated program, it still has some
424 advantages over the newer alignment scripts (<code>nucmer</code>, <code>promer</code>,
425 <code>run-mummer3</code>). Like all of the alignment scripts, <code>run-mummer1</code>
426 is a three step process - matching, clustering and extension. However, unlike
427 the newer alignment scripts, <code>run-mummer1</code> uses the <code>gaps</code>
428 program for its clustering step. The <code>gaps</code> program does not allow
429 for rearrangements like <code>mgaps</code>, instead if finds the single longest
430 increasing subset of matches across the full length of both sequences. This
431 makes it well suited for SNP and small indel identification between small (&lt;
432 10 Mbp), very similar sequences with few to no rearrangements.</p>
433 <p>In the following sections, a short example is given that demonstrates how to
434 use <code>run-mummer1</code>. This example aligns a single query sequence to
435 a single reference sequence using <code>run-mummer1</code>.</p>
436 <h5>The following input files will be used to demonstrate this example:</h5>
437 <ul>
438 <li><code><a href="data/H_pylori26695_Bslice.fasta">H_pylori26695_Bslice.fasta</a></code></li>
439 <li><code><a href="data/H_pyloriJ99_Bslice.fasta">H_pyloriJ99_Bslice.fasta</a></code></li>
440 </ul>
441 <h5>The following output files will be generated by this example:</h5>
442 <ul>
443 <li><code><a href="data/mummer1.align">mummer1.align</a></code></li>
444 <li><code><a href="data/mummer1.errorsgaps">mummer1.errorsgaps</a></code></li>
445 <li><code><a href="data/mummer1.gaps">mummer1.gaps</a></code></li>
446 <li><code><a href="data/mummer1.out">mummer1.out</a></code></li>
447 </ul>
448 <h4><a name="runmummer1runmummer1"></a>2.5.1. Running run-mummer1</h4>
449 <p><code>run-mummer1</code> is only suited for a single reference and query sequence
450 that have few to zero inversions or translocations. This example aligns two
451 such sequences.</p>
452 <p><code>run-mummer1 H_pylori26695_Bslice.fasta H_pyloriJ99_Bslice.fasta mummer1</code></p>
453 <p>To adjust the minimum match length for the comparison, the user must manually
454 edit the <code>run-mummer1</code> script. Output files are prefixed by the string
455 specified at the end of the command line call. <code>mummer1.align</code> displays
456 the alignments of each gap between adjacent MUMs, <code>mummer1.errorsgaps</code>
457 lists each MUM and the number of errors between it and the previous MUM, <code>mummer1.gaps</code>
458 lists the ordered set of MUMs and the gap distance to the previous MUM, and
459 <code>mummer1.out</code> simply lists all of the MUMs greater than or equal
460 to the minimum match length.</p>
461 <h4><a name="outputrunmummer1"></a>2.5.2. Viewing the output</h4>
462 <p>There are no visualization tools designed for <code>run-mummer1</code> output.
463 To view a MUM dotplot, run <code>mummer</code> by itself on two individual sequence
464 as demonstrated in the <a href="#mummer">mummer walkthrough</a>.</p>
465 <h3><a name="mummer3"></a>2.6. run-mummer3</h3>
466 <p><code>run-mummer3</code> is the simplest pipeline of the latest MUMmer3.0 programs.
467 It runs the same matching and clustering algorithm as <code>nucmer</code> and
468 <code>promer</code>, however it uses a different extension technique and does
469 not perform the important pre- and post-processing steps of NUC/PROmer. Because
470 of its simplistic form, <code>run-mummer3</code> can only handle a single reference
471 sequence, but like <code>run-mummer1</code> its error-focused output makes it
472 a handy tool for detecting SNPs and other small errors. The only major difference
473 between <code>run-mummer3</code> and <code>run-mummer1</code> is the new version's
474 ability to handle multiple query sequences and its tolerance of large rearrangements.
475 This makes <code>run-mummer3</code> well suited for error detection between
476 highly similar sequences that may have large rearrangements, inversions etc.</p>
477 <p>In the following sections, a short example is given that demonstrates how to
478 use <code>run-mummer3</code>. This example aligns a single query sequence to
479 a single reference sequence using <code>run-mummer3</code>.</p>
480 <h5>The following input files will be used to demonstrate this example:</h5>
481 <ul>
482 <li><code><a href="data/H_pylori26695_Eslice.fasta">H_pylori26695_Eslice.fasta</a></code></li>
483 <li><code><a href="data/H_pyloriJ99_Eslice.fasta">H_pyloriJ99_Eslice.fasta</a></code></li>
484 </ul>
485 <h5>The following output files will be generated by this example:</h5>
486 <ul>
487 <li><code><a href="data/mummer3.align">mummer3.align</a></code></li>
488 <li><code><a href="data/mummer3.errorsgaps">mummer3.errorsgaps</a></code></li>
489 <li><code><a href="data/mummer3.gaps">mummer3.gaps</a></code></li>
490 <li><code><a href="data/mummer3.out">mummer3.out</a></code></li>
491 </ul>
492 <h4><a name="runmummer3runmummer3"></a>2.6.1. Running run-mummer3</h4>
493 <p><code>run-mummer3</code> can only handle a single reference sequence, but it
494 is capable of dealing with multiple query sequences. However, this example aligns
495 a single query sequence to a single reference sequence. Unlike <code>run-mumer1</code>,
496 <code>run-mummer3</code> can handle inversions and translocations, but not with
497 the same grace as <code>nucmer</code>.</p>
498 <p><code>run-mummer3 H_pylori26695_Bslice.fasta H_pyloriJ99_Bslice.fasta mummer3</code></p>
499 <p>To adjust any of the alignment parameters, the user must manual edit the <code>run-mummer3</code>
500 scripts. Do not, however, add the <code>-c</code> option to the <code>mummer</code>
501 invocation, as it will confuse the next steps in the pipeline. It may be easier
502 to reverse complement the sequence yourself and run the script twice (once for
503 forward, second for reverse) with the <code>-b</code> option removed. Try adding
504 the <code>-D</code> option to the <code>combineMUMs</code> command line in the
505 script to output a format that is easier to parse for SNPs and small indels.
506 Output files are prefixed by the string specified at the end of the command
507 line call. <code>mummer3.align</code> displays the alignments of each gap between
508 adjacent MUMs, <code>mummer3.errorsgaps</code> lists each MUM and the number
509 of errors between it and the previous MUM, <code>mummer3.gaps</code> lists the
510 ordered set of MUMs and the gap distance to the previous MUM, and <code>mummer3.out</code>
511 simply lists all of the MUMs greater than or equal to the minimum match length.</p>
512 <h4><a name="outputrunmummer3"></a>2.6.2. Viewing the output</h4>
513 <p>The <code>mummer3.out</code> file is identical to the output of <code>mummer</code>
514 on a 1 vs many search, so it may be plotted as demonstrated in the <a href="#mummer">mummer
515 walkthrough</a>.</p>
516 <hr width="100%">
517 <h2><a name="contact"></a>3. Contact information</h2>
518 <p>Please address questions and bug reports via Email to:</p>
519 <p><a href="http://lists.sourceforge.net/lists/listinfo/mummer-help" target="_blank"><img src="../mummer-help.gif" alt="mummer-help(at)lists(dot)sourceforge(dot)net" width="290" height="24" border="0"></a></p>
520 <hr width="100%">
521 <div class="centered"><p><em>VERSION 3.17 - May 2005</em></p></div>
522
523 <a href="http://sourceforge.net"><img
524 src="http://sourceforge.net/sflogo.php?group_id=133157&amp;type=3" alt="SourceForge.net Logo" width="125" height="37" border="0"/></a>
525 </body>
526 </html>