Debian Codegraph @

USER_GUIDE

raw
1
2
3 DIALIGN 2.2.2
4
5 User Guide
6
7 Program code written by
8
9 Burkhard Morgenstern, Said Abdeddaim
10
11 at University of Bielefeld (FSPM and International Graduate School in
12 Bioinformatics and Genome Research), GSF (ISG, IBB, MIPS/IBI),
13 North Carolina State University, Universite de Rouen, MPI fuer
14 Biochemie (Martinsried), University of Goettingen, Institute of
15 Microbiology and Genetics.
16
17
18 E-mail contact: [email protected]
19
20
21 Reference:
22
23 B. Morgenstern (1999).
24 DIALIGN 2: improvement of the segment-to-segment approach to
25 multiple sequence alignment.
26 Bioinformatics 15, 211 - 218.
27
28 Public research assisted by DIALIGN should cite this article. For more
29 information, updated references etc. please visit the DIALIGN home page at
30
31 http://dialign.gobics.de/
32
33
34 Program usage:
35
36 dialign2-2 [ options ] <seq_file>
37
38
39 <seq_file> is the name of the input sequence file; this must be a multiple
40 FASTA file (all sequences in one file), a description of the format is
41 given below. The following options are available (a more detailed description
42 of these options is given below):
43
44 -afc Creates additional output file "*.afc" containing data of
45 all fragments considered for alignment
46 WARNING: this file can be HUGE !
47
48 -afc_v like "-afc" but verbose: fragments are explicitly printed
49 WARNING: this file can be EVEN BIGGER !
50
51 -anc Anchored alignment. Requires a file <seq_file>.anc
52 containing anchor points.
53
54 -cs if segments are translated, not only the `Watson strand'
55 but also the `Crick strand' is looked at.
56
57 -cw additional output file in CLUSTAL W format.
58
59 -ds `dna alignment speed up' - non-translated nucleic acid
60 fragments are taken into account only if they start with
61 at least two matches. Speeds up DNA alignment at the expense
62 of sensitivity.
63
64 -fa additional output file in FASTA format.
65
66 -ff Creates file *.frg containing information about all
67 fragments that are part of the respective optimal pairwise
68 alignmnets plus information about consistency in the multiple
69 alignment
70
71 -fn <out_file> output files are named <out_file>.<extension> .
72
73
74 -fop Creates file *.fop containing coordinates of all fragments
75 that are part of the respective pairwise alignments.
76
77 -fsm Creates file *.fsm containing coordinates of all fragments
78 that are part of the final alignment
79
80 -iw overlap weights switched off (by default, overlap weights are
81 used if up to 35 sequences are aligned). This option
82 speeds up the alignment but may lead to reduced alignment
83 quality.
84
85 -lgs `long genomic sequences' - combines the following options:
86 -ma, -thr 2, -lmax 30, -smin 8, -nta, -ff,
87 -fop, -ff, -cs, -ds, -pst
88
89 -lgs_t Like "-lgs" but with all segment pairs assessed at the
90 peptide level (rather than 'mixed alignments' as with the
91 "-lgs" option). Therefore faster than -lgs but not very
92 sensitive for non-coding regions.
93
94 -lmax <x> maximum fragment length = x (default: x = 40 or x = 120
95 for `translated' fragments). Shorter x speeds up the program
96 but may affect alignment quality.
97
98 -lo (Long Output) Additional file *.log with information abut
99 fragments selected for pairwise alignment and about
100 consistency in multi-alignment proceedure
101
102 -ma `mixed alignments' consisting of P-fragments and N-fragments
103 if nucleic acid sequences are aligned.
104
105 -mask residues not belonging to selected fragments are replaced
106 by `*' characters in output alignment (rather than being
107 printed in lower-case characters)
108
109 -mat Creates file *mat with substitution counts derived from the
110 fragments that have been selected for alignment
111
112 -mat_thr <t> Like "-mat" but only fragments with weight score > t
113 are considered
114
115 -max_link "maximum linkage" clustering used to construct sequence tree
116 (instead of UPGMA).
117
118 -min_link "minimum linkage" clustering used.
119
120 -mot "motif" option.
121
122 -msf separate output file in MSF format.
123
124 -n input sequences are nucleic acid sequences. No translation
125 of fragments.
126
127 -nt input sequences are nucleic acid sequences and `nucleic acid
128 segments' are translated to `peptide segments'.
129
130 -nta `no textual alignment' - textual alignment suppressed. This
131 option makes sense if other output files are of intrest --
132 e.g. the fragment files created with -ff, -fop, -fsm or -lo
133
134 -o fast version, resulting alignments may be slightly different.
135
136 -ow overlap weights enforced (By default, overlap weights are
137 used only if up to 35 sequences are aligned since calculating
138 overlap weights is time consuming). Warning: overlap weights
139 generally improve alignment quality but the running time
140 increases in the order O(n^4) with the number of sequences.
141 This is why, by default, overlap weights are used only for
142 sequence sets with < 35 sequences.
143
144 -pst "print status". Creates and updates a file *.sta with
145 information about the current status of the program run.
146 This option is recommended if large data sets are aligned
147 since it allows the user to estimate the remaining running
148 time.
149
150 -smin <x> minimum similarity value for first residue pair (or codon
151 pair) in fragments. Speeds up protein alignment or alignment
152 of translated DNA fragments at the expense of sensitivity.
153
154 -stars <x> maximum number of `*' characters indicating degree of
155 local similarity among sequences. By default, no stars
156 are used but numbers between 0 and 9, instead.
157
158 -stdo Results written to standard output.
159
160 -ta standard textual alignment printed (overrides suppression
161 of textual alignments in special options, e.g. -lgs)
162
163 -thr <x> Threshold T = x.
164
165 -xfr "exclude fragments" - list of fragments can be specified
166 that are NOT considered for pairwise alignment
167
168
169 General remark: If contradictory options are used, subsequent options
170 override previous ones, e.g.:
171
172 dialign2-2 -nt -n <seq_file>
173
174 runs the program with the "-n" option (no translation!), while
175
176 dialign2-2 -n -nt <seq_file>
177
178 runs it with the "-nt" option (translation!).
179
180
181
182 Input File:
183
184 Sequences to be aligned must be contained in a single file in FASTA
185 format. Example:
186
187
188 >HTL2
189 LDTAPCLFSDGSPQKAAYVLWDQTILQQDITPLPSHETHSAQKGELLALICGLRAAKPWP
190 SLNIFLDSKY
191 >MMLV
192 GKKLNVYTDSRYAFATAHIHGEIYRRRGLLTSEGKEIKNKDEILALLKALFLPKRLSIIH
193 CPGHQKGHSAEARGNRMADQAARKAAITETPDTSTLL
194 >HEPB
195 RPGLCQVFADATPTGWGLVMGHQRMRGTFSAPLPIHTAELLAACFARSRSGANIIGTDNS
196 GRTSLYADSPSVPSHLPDRVH
197
198
199 The first line for each sequence starts with ">" and contains the name of
200 the sequence. Please make sure, that the first line in the input file is
201 not empty and that the first character in the first line is not blank.
202
203 Some details about avaliable options:
204
205 (1) Sequence Type:
206
207 The user can decide if nucleic acid or protein sequences are to be
208 aligned.
209
210 (2) Threshold T:
211
212 As described in our papers, the program DIALIGN constructs alignments
213 from gapfree pairs of similar segments of the sequences. Such segment
214 pairs are referred to as `(alignment) fragments' (previously, we called
215 them `diagonals').
216
217 Every possible fragment is given a so-called weight reflecting the
218 degree of similarity among the two segments involved. The overall
219 score of an alignment is then defined as the sum of weights of the
220 fragments it consists of and the program tries to find an alignment with
221 maximum score -- in other words: the program tries to find a consistent
222 collection of fragments with maximum sum of weights. This novel scoring
223 scheme for alignments is the basic difference between DIALIGN and other
224 global or local alignment methods. Note that DIALIGN does not employ any
225 kind of gap penalty.
226
227 It is possible to use a threshold T for the quality of the fragments.
228 In this case, a fragment is considered for alignment only if its
229 `weight' exceeds this threshold. Regions of lower similarity are ignored.
230
231 In the first version of the program (DIALIGN 1), this threshold was in
232 many situations absolutely necessary to obtain meaningful alignments.
233 By contrast, DIALIGN 2 should produce reasonable alignments without a
234 threshold, i.e. with T = 0. This is the most important difference between
235 DIALIGN 2 and the first version of the program. Nevertheless, it is still
236 possible to use a positive threshold T to filter out regions of lower
237 significance and to include only high scoring fragments into the
238 alignment.
239
240 (3) Different levels of sequence similarity:
241
242 If (possibly) coding nucleic acid sequences are to be aligned, DIALIGN
243 optionally translates the compared `nucleic acid segments' to `peptide
244 segments' according to the genetic code -- without presupposing any of
245 the three possible reading frames, so all combinations of reading frames
246 get checked for significant similarity. If this option is used, the
247 similarity among segments will be assessed on the `peptide level' rather
248 than on the `nucleotide level'.
249
250 We strongly recommend to use the `translation' option if nucleic acid
251 sequences are expected to contain protein coding regions, as it will
252 significantly increase the sensitivity of the alignment procedure in
253 such cases.
254
255 For the levels of sequence similarity, release 2.2 of DIALIGN has
256 two additional options:
257
258 (a) it can measure the similarity among segment pairs at both levels
259 of similarity (nucleotide-level and peptide-level similarity). The
260 score of a fragment is based on whatever similarity is stronger. As a
261 result, the program can now produce `mixed alignments' that contain
262 both types of fragments. Fragments with stronger similarity at the
263 `nucleotide level' referred to as N-fragments whereas fragments with
264 stronger similarity a the peptide level are called P-fragments.
265
266 (b) if the `translation' or `mixed alignment' option is used, it is
267 possible to consider the `reverse complements' of segments, too. In
268 this case, both the original segments and their reverse complements
269 are translated and both pairs of implied `peptide segments' are
270 compared. This option is useful if DNA sequences contain coding regions
271 not only on the `Watson strand' but also on the `Crick strand'.
272
273 (4) The score that DIALIGN assigns to a fragment is based on the
274 probability to find a fragment of the same respective length and number
275 of matches (or BLOSUM values, if the translation option is used) in
276 random sequences of the same length as the input sequences. If long
277 genomic sequences are aligned, an iterative procedure can be applied
278 where the program first looks for fragments with strong similarity.
279 In subsequent steps, regions between these fragments are realigned.
280 Here, the score of a fragment is based on random occurrence in these
281 regions between the previously aligned segment pairs.
282
283 (5) With the -ff (or -lgs) option, a file with all fragments contained
284 in the output alignment can be returned. This file contains additional
285 information about the identified fragments such as
286
287 - start coordinates in the respective sequences
288 - length
289 - fragment weight,
290 - iteration step (if the iterative option is used)
291 - whether the similarity among the segments is strongest at the
292 nucleotide level (N-frg) or at the peptide level (P-frg) if the
293 `mixed alignment' option is used
294 - whether the similarity is stronger on the `Watson strand' (" + " )
295 or on the `Crick strand' (" - " ) - if a fragment is translated
296 and the respective option is used
297
298 All this information can be used to further post-process the DIALIGN
299 output, for example by customized visualisation tools.
300
301 The file containing this information looks like this:
302
303
304 # program call: ./dialign2-2 -lgs seq_file
305
306 seq_len: 552 527
307 sequences: seq1 seq2
308
309 1) seq: 1 2 beg: 161 351 len: 27 wgt: 7.60 it: 1 cons P-frg +
310 2) seq: 1 2 beg: 300 507 len: 17 wgt: 4.40 it: 1 cons N-frg
311 3) seq: 1 2 beg: 111 170 len: 12 wgt: 4.34 it: 1 cons N-frg
312
313
314 (6) Degree of local sequence similarity:
315
316 Numbers between 0 and 9 are printed below the alignment to indicate
317 the degree of local sequence similarity (in previous verions of the
318 program, "*" characters were used instead of numbers). These numbers
319 are normalized such that the region of highest similarity gets a
320 score of 9. With the -stars option, "*" characters can be used as
321 previously.
322
323 (7) `overlap weights':
324
325 This option improves the sensitivity of the program if multiple sequences
326 are aligned but it also increases the running time, especially if large
327 numbers of sequences are aligned. By default, `overlap weights' are used
328 if up to 35 sequences are aligned but switched off for larger data sets.
329 In the command-line version, `overlap weights' can be switched on or off
330 for data sets of any size, see below.
331
332 (8) `anchored alignment':
333
334 Forces the program to align user-specified anchor points to speed-up
335 the alignment procedure for long sequences. Anchor points are given in
336 a file <seq_file>.anc where <seq_file> is the name of the sequence file
337 (without extension .fa or .seq). Note that anchoring is possible for
338 pairwise as well as for multiple alignment. The format of the .anc file
339 is as follows (each line represents one anchor point):
340
341
342 2 5 13724 7646 23 23.45345
343 1 3 6596 517 5 12.34555
344 3 5 33511 9438 34 27.45459
345
346 The first two columns are the sequences to be anchored, columns 3
347 and 4 contain the beginning positions of the anchored segments in
348 the specified sequences, and column 5 contains a score of the
349 anchor that specifies its priority compared to other anchoring
350 regions in case there is a conflict between inconsistent anchor
351 points (see below).
352
353 In the above example, three anchored segment pairs are specified.
354 Here, 13724 is the beginning position of the first anchor in sequence 2,
355 7646 is the beginning position of the first anchor in sequence 5 and
356 23 is the length of the first anchor. In other words, the program is
357 forced to align positions 13724 - 13746 in sequence 2 with positions
358 7646 - 7668 in sequence 5. Similarly, a segment of sequence 1 starting
359 at position 6596 is anchored with a segment of sequence 3 starting
360 at position 517 etc.
361
362 The program can use only consistent sets of anchor points. This means,
363 that all anchored regions must fit into one single multiple alignment
364 (see our papers for our notion of "consistency"). The anchor points
365 in the specified file are sorted according to their scores (as given
366 in the last column of the anchor file) and then accepted one-by-one
367 -- provided they are consistent with the already accepted anchor points.
368
369 This is exactly the way, dialign includes fragments (segment pairs
370 or "diagonals") into a resulting multiple alignment, see the dialign
371 papers for more details.
372
373 Anchor points can be created by any suitable software program,
374 for example by CHAOS developed by Mike Brudno, Stanford:
375
376 http://www.stanford.edu/~brudno/chaos/
377
378
379 (9) `Motif' option:
380
381 A motif can be specified by a simple regular expression such as "TY[ILV]A".
382 Gaps are not allowed in motifs; all residues within brackets are allowed
383 at the respective position. For example, "TYIA", "TYLA" and "TYVA" would
384 match the above motif. Alignments where instances of the motif are aligned
385 to each other, are preferred. They receive a bonus which can be specified
386 by the user. There are two paramters to determine the bonus for matched
387 motifs: a first weighting factor (fct1) assigns a bonus for aligned
388 instances of the motif occurring at the same relative position in the
389 input sequences. The bonus decreases with the distance between the
390 matched motif in the sequences. A second parameter (fct2) controls how fast
391 the bonus decreases.
392
393 With the two user-defined parameters fct1 and fct2, the bonus for each
394 matched motif is calculated as follows: If a matched motif occurs at
395 positions i and j in two of the input sequences, |i-j| is the `offset'
396 of the motif. The bonus is then
397
398 fct1 * exp - ( |i-j|^2 / (fct2^2 * 10 ) )
399
400 I.e. a high value of fct2 means that even matches of the motif that are
401 far apart within the sequences reveive a high bonus.
402
403 With the motif-search option, the program call is:
404
405 ./dialign2-2 [para] -mot <regex> <fct1> <fct2> [para] <seq>
406
407 where
408 <regex> is a regular expression, e.g. "AT[CG]XT",
409 <fct1> is the first parameter
410 <fct2> is the second parameter
411 <seq> is the input sequence file and
412 [para] are (optional) additional program parameters
413
414
415 Similarity Matrix:
416
417 DIALIGN 2 uses the BLOSUM62 amino acid substitution matrix. In the current
418 version, it is NOT possible to replace BLOSUM62 by other similarity matrices,
419 since the probability values contained in the files n_prob and p_prob refer
420 to the BLOSUM62 matrix.
421
422
423
424 Program Output:
425
426 By default, DIALIGN creates a single file containing
427
428 - An alignment of the input sequences in DIALIGN format.
429 - The same alignment in FASTA format.
430 - A sequence tree in PHYLIP format. This tree is constructed by applying
431 the UPGMA clustering method to the DIALIGN similarity scores. It roughly
432 reflects the different degrees of similarity among sequences. For
433 detailed phylogenetic analysis, we recommend the usual methods for
434 phylogenetic reconstruction.
435
436
437 This is the DIALIGN alignment format:
438
439
440
441 SMb21199_AA- 1 mtemkdsila vrglkvdfyt pd-GTVE-AV KGIDLDVRSG ETLAVVGESG
442 SMb21206_AA- 1 mpapatepgt apfVRLTGVT KRFGTARpAL DAVAGEIFGG RVTGLVGPDG
443 SMb21592_AA- 1 mtlq------ ---IELNGVN KFYGSYH-AL KDIDLAIEEG TFVALVGPSG
444 SMb21605_AA- 1 msg------- ---IKLTGVS KSFGAVK-VI HGVDIEIGQG EFAVFVGPSG
445
446 0000000000 0000000000 0002222022 2222233356 6666666666
447
448
449 SMb21199_AA- 49 SGKSQTMMGI MGLLakngtv tgsaryrgqe lvgLAPKALN KVRGS-KITM
450 SMb21206_AA- 51 AGKTTLIRLM TGLMLPDAGT IE-------- ---VLGydtr rdpasiQAAI
451 SMb21592_AA- 41 CGKSTLLRSL AGLEKISAGE MK-------- ---IAGARMN DVPPR-KRDV
452 SMb21605_AA- 40 CGKSTLLRMI AGLEETTGGE IR-------- ---Idaedvt hkePS-KRGV
453
454 6666666666 6664333333 3300000000 0003110000 0001102222
455
456
457 SMb21199_AA- 98 IFQEPMTSLD PLYTIGRQIA EPIvhhRGGS FKEA---RRR VLELLELVGI
458 SMb21206_AA- 90 GYMPQRFGLY EDLSVQENLD LYADL-RGLP KTER---SRT FGELLDFTDL
459 SMb21592_AA- 79 AMVFQSYALY PHMTVEENLT YSLRI-RGVK KAEA---LKA AAEVATTTGL
460 SMb21605_AA- 78 AMVFQSYALY PHLSVFDNMA FSLSI-ARRP KAEieqkVKA AAEIlrlsdy
461
462 2222222222 2222222222 2222202222 2220000000 0000000000
463
464
465
466 Names of aligned sequences are shown on the left hand side of the
467 alignment.
468
469 Numbers on the left hand side of the alignment denote the position
470 of the first residue in a line within the respective sequence.
471
472 Capital letters denote aligned residues, i.e. residues involved in
473 at least one of the fragments the alignment consists of. Lower-case
474 letters denote residues not belonging to any of these selected
475 fragments. They are not considered to be aligned by DIALIGN. Thus,
476 if a lower-case letter is standing in the same column with other letters,
477 this is pure chance; these residues are not considered to be homologous.
478
479 Numbers below the alignment reflects the degree of local similarity
480 among sequences. More precisely: They represent the sum of `weights'
481 of fragments connecting residues at the respective position.
482
483 These numbers are normalized such that regions of maximum similarity
484 always get a score of 9 - no matter how strong this maximum simliarity
485 is.
486
487
488
489 This is FASTA alignment format:
490
491
492 >HTL2
493 ldtapcLFSDGS------PQKAAYVLWDQTIL---QQDITPLPSHethSA
494 QKGELLALICGLRAAKPWPSLNIFLDSKYLIKYLHslaigaflgtsah--
495 -------QT---LQAALPPLLQGKTIYLHHVRSHT------NLPDPISTF
496 NEYTDSLILApl--------------------------------------
497 ----------
498 >MMLV
499 pdadhtwYTDGSSLLQEGQRKAGAAVTTETeviwaKALDAG---T---SA
500 QRAELIALTQALKMAEgkk-LNVYTDSRYAFATAHIHGEIYRRRGLLTSE
501 GKEIKNKDE---ILALLKALFLPKRLSIIHCPGHQ------KGHSAEARG
502 NRMADQAARKAAITETPDTStll---------------------------
503 ----------
504 >HEPB
505 rpglcQVFADAT------PTGWGLVMGHQRMR---GTFSAPLPIHt----
506 --AELLAACFArsrsgan---IIGTDN-----------------------
507 -------------SVVLSR--------------KYTSFPWLLGCAANWI-
508 LRGTSFVYVPSALNPADDPSrgrlglsrpllrlpfrpttgrtslyadsps
509 vpshlpdrvh
510
511
512
513 This is PHYLIP tree format:
514
515
516 ((HTL2:0.111024,
517 (MMLV:0.078471,
518 ECOL:0.078471):0.032554):0.121218,
519 HEPB:0.232242);
520
521
522
523 Trees can be visualized using the treetool program that is part of
524 Joe Felsenstein's PHYLIP software package:
525
526 http://evolution.genetics.washington.edu/phylip.html
527
528
529 ---------------------------------------------------------------------
530
531 Last update by Burkhard Morgenstern, Goettingen, February 2005
532
533
534
535
536
537