Debian Codegraph @

html/quickdos.html

raw
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3 <html>
4 <head>
5 <!-- $Id: quickdos.html 313 2009-06-11 05:44:13Z thomasoa $ -->
6 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
7 <LINK REL="SHORTCUT ICON" HREF="/icon/bridge.ico">
8 <link rev="made" href="mailto:[email protected] (Thomas Andrews)">
9 <link rel="stylesheet" type="text/css" href="look.css">
10
11 <title>
12 Deal - An Introductory Tutorial for Windows
13 </title>
14
15 </head>
16 <body>
17 <div class="back"><a href="index.html">Back to <em>Deal Top Page</em></A></div>
18
19 <TABLE class="toplevel">
20 <TR>
21 <td valign="middle"><img
22 style="border:0;width:225px;height:216px"
23 SRC="graphics/falling_small.jpg" ALT="Plane Dealing image"></td>
24 <td valign="middle"><div class="header"><h1>Deal 3.1</h1>
25 <h2>An Introductory Tutorial for Windows</h2></div>
26 Covering: <UL>
27 <LI> Dealing hands
28 <LI> Stacking hands
29 <LI> Output formats
30 <LI> Basic scripting with Tcl
31 </UL>
32 </td>
33 </tr></table>
34 <div class="toplevel">
35 <hr>
36 <h2> Prologue </h2>
37 First things first, you will need to <a href="downloading.html">download
38 Deal and install it</a>. The rest of this tutorial assumes you have
39 already done this.
40 <p>
41 <img SRC="graphics/warning.gif" ALT="**Warning**"> It takes careful eyes, at least on the version of Netscape I am
42 using, to distinguish between normal parentheses, <span class="code">()</span>, and curly
43 parentheses, <span class="code">{}</span>. Almost all of the parentheses in the script
44 listings below are curly parentheses.
45 <p>Deal only runs in Deal's installed directory. That's because for now it looks in the current directory for <code>deal.tcl</code> and other library files.
46 <h2> <a href="#basic">Basic Dealing - The Command Line </a></h2>
47 <UL>
48 <LI> <a href="#basicbasic">Dealing hands</a>
49 <LI> <a href="#basicstacking">Stacking a hand</a>
50 <LI> <a href="#basicformat">Formatting output</a>
51 </UL>
52 <h2> <a href="#scripting">Basic Dealing - Scripting </a></h2>
53 <UL>
54 <LI> <a href="#first">A first script</a>
55 <LI> <a href="#routines">A partial list of routines</a>
56 <LI> <a href="#second">A second script</a>
57 <LI> <a href="#accept">Revisiting <span class="code">accept</span> and <span class="code">reject</span></a>
58 </UL>
59
60 <h2><a name="basic">Basic Dealing</a></h2>
61
62 <h3><a name="basicbasic">Dealing hands</a></h3>
63 <p>
64 Start Command Prompt window and change your directory
65 to the location where Deal was installed.
66 <pre class="codesample">
67 C:\> <b>cd "C:\deal30"</b>
68
69 C:\deal30>
70 </pre>
71
72 The most basic version of deal runs with no conditions set on the deal,
73 and generates 10 deals:
74 <pre class="codesample">
75 C:\deal30> <b>deal</b>
76 </pre>
77
78 The output probably scrolled off the screen, so you might want to do
79 <pre class="codesample">
80 C:\deal30> <b>deal | more</b>
81 </pre>
82
83 to allow scrolling, or:
84 <pre class="codesample">
85 C:\deal30> <b>deal > out.txt</b>
86 </pre>
87
88 which saves the output from deal to the file, <span class="code">out.txt</span>.
89
90 <p>
91 If you give "deal" a number on the command line, it generates that many
92 deals:
93 <pre class="codesample">
94 C:\deal30> <b>deal 2</b>
95 S : T6542
96 H : A4
97 D : A93
98 C : KT2
99 S : Q83 S : K97
100 H : 9873 H : K52
101 D : JT7 D : Q64
102 C : Q74 C : J863
103 S: AJ
104 H: QJT6
105 D: K852
106 C: A95
107 ---------------------------
108 S : ---
109 H : 975
110 D : AT986
111 C : T9753
112 S : J7 S : AKT6
113 H : T32 H : KJ864
114 D : K32 D : J74
115 C : AJ842 C : 6
116 S: Q985432
117 H: AQ
118 D: Q5
119 C: KQ
120 ---------------------------
121 C:\deal30>
122 </pre>
123 In this example, <strong>Deal</strong> dealt two hands, as requested.
124 <p>
125 <h3><a name="basicstacking">Stacking a hand</a></h3>
126 Okay, let's take another example. Suppose you opened 3H on the following
127 hand in a team game:
128 <pre class="codesample">
129 S: ---
130 H: KQJT62
131 D: T9876
132 C: 84
133 </pre>
134 You stumble into a six heart contract, when in fact, six diamonds has better
135 play opposite partner's hand. Partner swears that opening 3H with this
136 hand loses more often than it wins. You disagree. How do you resolve
137 this?
138 <p>
139 <strong>Deal</strong> can help. Just run it as:
140
141 <pre class="codesample">
142 C:\deal30> <b>deal -S "- KQJT62 T9876 84" 25</b>
143 S : KJ2
144 H : 954
145 D : A5
146 C : AKT65
147 S : T9764 S : AQ853
148 H : A H : 873
149 D : J2 D : KQ43
150 C : QJ973 C : 2
151 S: ---
152 H: KQJT62
153 D: T9876
154 C: 84
155 ---------------------------
156 S : KJT64
157 H : 5
158 D : K42
159 C : AQ65
160 S : 9875 S : AQ32
161 H : A93 H : 874
162 D : AJ5 D : Q3
163 C : KJ9 C : T732
164 S: ---
165 H: KQJT62
166 D: T9876
167 C: 84
168 ---------------------------
169 .... (rest of 25 hands ellided) ...
170 </pre>
171
172 You inspect the 25 hands dealt, guessing how the auction would
173 proceed. Sometimes, your answers will be inconclusive, but more
174 often one or both partners learns something from the simulation.
175 <p>
176 There are, of course, also <span class="code">-N</span>, <span class="code">-E</span>, and <span class="code">-W</span> options
177 for the other three seats.
178 <h3><a name="basicformat">Formatting output</a></h3>
179 Perhaps you'd like the hands to be written in some other format.
180 This can be arranged fairly easily.
181 <p>
182 For example, suppose you wish to deal 8 hands for practice bidding
183 with partner. In that case, you would use the "practice" format:
184
185 <pre class="codesample">
186 C:\deal30> <b>deal -i format/practice 8 > out.all</b>
187 C:\deal30> <b>more out.east</b>
188 east hands
189 ============================================================================
190 *1* *2* *3* *4*
191 S 84 S T7 S QT3 S AJ9654
192 H J8642 H Q65 H Q983 H K8
193 D Q843 D KJ42 D 865 D J
194 C 73 C T842 C AJ9 C K532
195
196 =============================================================================
197 *5* *6* *7* *8*
198 S J7 S 85 S AQT764 S 3
199 H Q9864 H AK4 H K5 H JT4
200 D 874 D A764 D 9 D QJT86
201 C J85 C Q862 C T976 C AK82
202
203 =============================================================================
204 </pre>
205
206
207 The <span class="code">-i</span> flag tells <strong>Deal</strong> to include the named file,
208 in this case, the file named <span class="code">format/practice</span>. This file redefines
209 the output format. At the end of this run, you should get five files:
210 <span class="code">out.north</span>, <span class="code">out.east</span>, <span class="code">out.south</span>,
211 <span class="code">out.west</span>, and <span class="code">out.all</span>.
212 <p>
213 Now you can print out these files, pass them out amongst four people,
214 and practice your bidding, using <span class="code">out.all</span> at the end to make
215 a double dummy assessment of the auction results.
216 <p>
217 What if you only have two people, and you want to practice uninterrupted
218 auctions? You could print out the north and south hands, and practice
219 with those, but that would be an artificial
220 test, because you obviously can't assume an uncontested auction for
221 arbitrary deals.
222 <p>
223 When we learn about writing scripts for <strong>Deal</strong>, we will solve with this problem by filtering out hands we think would lead to competitive
224 bidding.
225 <p>
226 What are the formats that come with the kit? Well, you can simply list
227 the <span class="code">format</span> sub-directory to find out. Here are the ones there
228 as of this writing:
229 <DL>
230 <DT> <span class="code">none</span>
231 <DD> This script set the formatting routine to a null routine.
232 Not useful, so far, but useful, for example, when doing
233 statistical analysis.
234 <DT> <span class="code">numeric</span>
235 <DD> This formatter writes the deal as a line which looks something
236 like:
237 <pre class="codesample">
238 3031333123220300123320212213021202022103101101003113
239 </pre>
240 It's a line of 52 numbers, where 0, 1, 2, and 3 mean
241 north, east, south, and west, respectively.
242 The first digit tells where the ace of spades goes, the
243 second digit tells where the king of spades goes, etc.
244 <DT> <span class="code">okb</span>
245 <DD> This formatter writes the output with the same spacing as the old
246 OKbridge screen.
247 <DT> <span class="code">practice</span>
248 <DD> We've just seen this one - for seperating out hands for
249 practice bidding.
250 </DL>
251 There is one last output format, which, for historical reasons,
252 has its own command line switch, <span class="code">-l</span>.
253
254 <pre class="codesample">
255 C:\deal30> <b>deal -l 3</b>
256 AJ9 976532 K92 A|86 A AT87 987653|Q732 JT8 543 T42|KT54 KQ4 QJ6 KQJ
257 K94 J93 QJ3 7653|A8 A8765 97 KQ98|JT2 Q AKT8654 T4|Q7653 KT42 2 AJ2
258 KJ753 T A4 KQ932|AQ94 AJ92 QT87 J|86 Q764 K9653 74|T2 K853 J2 AT865
259 C:\deal30>
260 </pre>
261
262 In the past, this was the only way to get alternate formats. The
263 user would pipe this output to another program, usually a Perl script,
264 which would parse each line and format the output.
265 <p>
266 With the addition, in v2.0 of <strong>Deal</strong>, of user-configurable formatting,
267 this usage becomes obselete, but I'm leaving the feature because
268 it has one other use, which will be mentioned later.
269
270 <h2> <a name="scripting">Basic Dealing - Scripting </a></h2>
271 <h3><a name="first">Our First Script</a></h3>
272 Let's say we want a selection of deals in which north holds a one spade
273 opener. For now, we will use a crude definition for an opening 1S call -
274 we will require north to have 5 or more spades and 12 or more points.
275 <p>
276 Here is the script we write (to a file we'll call <span class="code">onespade</span>):
277
278 <pre class="codesample">
279 main {
280 if {[spades north]>=5 && [hcp north]>=12} { accept }
281 reject
282 }
283 </pre>
284
285
286 <h4> Running the script</h4>
287 We run this code by saying:
288
289 <pre class="codesample">
290 C:\deal30> <b>deal -i onespade 2</b>
291 S : AKQT5
292 H : A7
293 D : 8542
294 C : AT
295 S : 64 S : J98
296 H : K943 H : 862
297 D : J D : AK963
298 C : KQ8732 C : 54
299 S: 732
300 H: QJT5
301 D: QT7
302 C: J96
303 ---------------------------
304 S : AQT73
305 H : A
306 D : AJ987
307 C : 73
308 S : K5 S : J42
309 H : JT8632 H : KQ95
310 D : Q63 D : KT4
311 C : 85 C : K92
312 S: 986
313 H: 74
314 D: 52
315 C: AQJT64
316 ---------------------------
317 </pre>
318
319 <h4>How the script works</h4>
320 By default, <strong>Deal</strong> accepts all hands. With the <span class="code">main</span> code in
321 <span class="code">onespade</span>, we tell <strong>Deal</strong> to override that behavior.
322 <p>
323 This is similar to the way we used scripts to override <strong>Deal</strong>'s
324 default formatting. Note, we even use the same flag, <span class="code">-i</span>,
325 to load our formatters and <span class="code">onespade</span>.
326 <p>
327 What does this <span class="code">main</span> code do? It is run after every deal
328 is complete, and used to evaluate the hand. In this case, we have only
329 two lines of code:
330
331 <pre class="codesample">
332 if {[spades north]>=5 && [hcp north]>=12} { accept }
333 reject
334 </pre>
335
336 The expression <span class="code">[spades north]</span> returns the number of spades
337 in the north hand. The expression <span class="code">[hcp north]</span> returns
338 the number of HCP (high card points) in the north hand. The "<span class="code">&&</span>"
339 is called a logical "and" operator, which returns true if the conditionals
340 on both sides of it are true.
341 <p>
342 If the entire expression:
343 <pre class="codesample">
344 [spades north]>=5 && [hcp north]>=12
345 </pre>
346 evaluates as true, the "accept" function is called. This causes
347 <strong>Deal</strong> to exit the "main" code and format the hand.
348 <p>
349 If the expression evalutes as false, <strong>Deal</strong> goes to the next line
350 of code, which calls the "reject" function. This tells <strong>Deal</strong> to
351 discard the hand, and exit the "main" code.
352 <p>
353 <strong>Deal</strong> keeps trying until the requested number of deals is accepted.
354 <p>
355 What happens if a deal is not explicitly accepted or rejected?
356 If neither <span class="code">accept</span> nor <span class="code">reject</span> is called, the deal
357 is rejected. That means that in our first script, the <span class="code">reject</span>
358 call was redundant, and we could have simply written the script as:
359
360 <pre class="codesample">
361 main {
362 if {[spades north]>=5 && [hcp north]>=12} { accept }
363 }
364 </pre>
365
366 <h4> Monitoring Deal</h4>
367 You might want to try running this script with the <span class="code">-v</span> switch:
368 <pre class="codesample">
369 C:\deal30> <b>deal -v -i onespade</b>
370 </pre>
371 The <span class="code">-v</span> flag tells <strong>Deal</strong> to give a progress report, which looks
372 like:
373
374 <pre class="codesample">
375 ...
376 Deal 1 found after 2 tries
377 ...
378 Deal 2 found after 21 tries
379 ...
380 Deal 3 found after 31 tries
381 </pre>
382
383 This will give you some idea of how rare your condition is, and
384 also gives a good progress report when <strong>Deal</strong> is
385 writing to a file or running with a "silent" format, like
386 <span class="code">format/none</span>. These status messages are written to "stderr",
387 which means that the output from <strong>Deal</strong> can be
388 redirected to a file without obscuring these messages. <p>
389
390 <h4> Using formats with your script </h4>
391
392 If we wanted to use another output format with this script, we could do so
393 on the command line, as follows:
394 <pre class="codesample">
395 C:\deal30> <b>deal -i format/practice -i onespade</b>
396 </pre>
397 Or, alternately, we could add an explicit "source" command to our
398 script:
399
400 <pre class="codesample">
401 source format/practice
402
403 main {
404 if {[spades north]>=5 && [hcp north]>=12} { accept }
405 }
406 </pre>
407
408
409 In fact, this second format unveils the secret of the <span class="code">-i</span> flag -
410 it is simply a request to "source" a file. In fact, if you were to
411 write your own formatter, you would not have to put the file in
412 the "format" directory.
413 If you put it in the current directory, you could then say:
414 <pre class="codesample">
415 C:\deal30> <b>deal -i myformatter 100</b>
416 </pre>
417 and it would work fine. The "format" subdirectory is just a convenience.
418 You will often want to re-use a format, and placing them in one place
419 lets you find out which formats are available.
420
421 <h4> Stacking hands with a script </h4>
422
423 Let's say you were dealt the hand:
424 <pre class="codesample">
425 S: ---
426 H: 98532
427 D: A864
428 C: T962
429 </pre>
430 the previous day at a Swiss Teams event.
431 <p>
432 Your partner opened 1S, and, playing 2/1 Game Force, you chose to
433 pass. This turns out well for you on this deal, because at the other
434 table, the opponents played in three spades, down 1. Afterwards,
435 you wonder if you really made the right decision. Your intuition
436 tells you that it was the right choice, but you realize there are
437 risks in both passing and bidding, and you know that intuition is
438 very bad at assessing levels of risk.
439 <p>
440 <strong>Deal</strong> can help. Using our script, <span class="code">onespade</span>,
441 we can run the following simulation:
442 <pre class="codesample">
443 C:\deal30> <b>deal -S "- 96532 A864 T962" -i onespade</b>
444 </pre>
445 The <span class="code">-S</span> flag stacks the south hand with the hand you held,
446 and the script runs exactly the same thereafter. You can now peruse
447 the output to see whether it was a good idea or a bad idea to pass.
448 <p>
449 As with the formatting, we can also do our deck-stacking in our script.
450
451 <pre class="codesample">
452 south is - 98532 A864 T962
453
454 main {
455 if {[spades north]>=5 && [hcp north]>=12} { accept }
456 }
457 </pre>
458
459
460 Notice, we do our deck-stacking outside of the evaluation loop.
461 Remember, the <span class="code">main</span> expression is responsible for evaluating the deals
462 <em>after</em> <strong>Deal</strong> finishes dealing the hands.
463 We obviously want the stacking instruction to occur before
464 dealing occurs, so the stacking command must be outside the main
465 evaluation.
466 <p>
467 <h3><a name="routines">A partial list of routines</a></h3>
468 For evaluation routines, we have seen the <span class="code">hcp</span> and <span class="code">spades</span>
469 routines, as well as the "accept" and "reject" directives.
470 Obviously, there are also routines called <span class="code">hearts</span>,
471 <span class="code"> diamonds</span>, and <span class="code">clubs</span> which count their respective
472 suits. The following functions are also built-ins:
473 <dl>
474 <dt> <span class="code">controls</span> <dd> This function computes the number of
475 controls held by a hand.
476 <dt> <span class="code">losers</span> <dd> This function does a crude computation of
477 the losing trick count for a hand (it actually compute's half-losers,
478 so when [losers south] returns 14, that really means 7 losers.)
479 <dt> <span class="code">balanced</span> <dd> This function returns true (1) if the
480 hand name passed is balanced in the usual sense - no shortness, at most
481 one doubleton, and no five-card major. It returns false (0) otherwise.
482 <dt> <span class="code">semibalanced</span> <dd> Returns true (1) if the hand passed
483 has no shortness and no six-card major or seven-card minor, and false
484 (0) otherwise.
485 </dl>
486 The three functions, <span class="code">controls</span>, <span class="code">hcp</span>, and <span class="code">losers</span>,
487 all have the property that we can compute them one suit at a time, and
488 sum the result for the entire hand. The implementation takes advantage
489 of this and allows the user to request these values for specific suits:
490
491 <pre class="codesample">
492 main {
493 if {[hcp south hearts spades]>10} {accept}
494 }
495 </pre>
496
497 This script accepts a deal if south has ten or more points in hearts
498 and spades. <span class="code">controls</span> and <span class="code">losers</span> can be used similarly.
499 Any function of this sort we will call "additive." We will see later that
500 we can define a <a href="advanced.html#vector">wide class of interesting
501 additive functions.</a>
502 <p>
503 The functions <span class="code">balanced</span> and <span class="code">semi_balanced</span> are entirely
504 dependent on the shape of the hand, and not on which cards the hand holds. We
505 will call these "shape functions." We will find out later how to
506 define <a href="advanced.html#shapefunc">incredibly fast shape functions.</a>
507
508 <h3><a name="second">A Second Script - defining Tcl procedures</a></h3>
509
510 Let's say we want to write a script which accepts a deal if north
511 has a strong notrump (15 to 17 range) and south has about invitational
512 values and a 5-card major.
513
514 <p>
515 Our script , which we will call <span class="code">jacobytest</span> might look something like:
516
517
518 <pre class="codesample">
519 # In deal 2.0, you don't need this next line, but deal 3.1 does -
520 # without this line, the "balanced" routine is not defined.
521
522 main {
523 if {![balanced north]} {reject}
524
525 set hn [hcp north]
526 if {$hn>17 || $hn&lt;15} {reject}
527
528 set hs [hcp south]
529 if {$hs&lt;8 || $hs>9} {reject}
530
531 if {[spades south]==5 || [hearts south]==5} { accept }
532 }
533 </pre>
534
535
536 We have used one of our new functions here, <span class="code">balanced</span>, as
537 well as a new Tcl feature, variables. We could, of course, not used
538 variables, but then we would have had to write the lines:
539 <pre class="codesample">
540 if {[hcp north]>17 || [hcp north]&lt;15} {reject}
541 </pre>
542 That is going to be slower, with one more function call. Not appreciable
543 today, with a simple query, but when you might be processing a million or
544 more hands at a time, you learn to be frugal.
545 <p>
546 Suddenly, you realize you want to test this situation with a 12-14 notrump,
547 instead. Or you realize you often want to reuse this concept. You
548 can do so by defining Tcl procedures.
549 <p>
550
551 <pre class="codesample">
552 proc notrump {hand min max} {
553 if {![balanced $hand]} {return 0}
554
555 set hc [hcp $hand]
556 if {$hc &lt; $min || $hc>$max} { return 0}
557
558 return 1
559 }
560
561 proc jacobyinvite {hand ntmin ntmax} {
562
563 if {[spades $hand]!=5 && [hearts $hand]!=5} {return 0}
564
565 set hc [hcp $hand]
566 if {$hc+$ntmin &lt;= 25 && $hc+$ntmax>=24} { return 1 }
567
568 return 0
569
570 }
571
572 set NTmin 12
573 set NTmax 14
574
575 main {
576 if {![notrump north $NTmin $NTmax]} { reject }
577 if {[jacobyinvite south $NTmin $NTmax]} { accept }
578 }
579 </pre>
580
581 You are unlikely to need the <span class="code">jacobyinvite</span> function
582 beyond this script, but the <span class="code">notrump</span> function will be something
583 you will want
584 to use again and again. You might even put it in a library of routines, called
585 <span class="code">mylibrary</span> and source that library every time you need one or more
586 of the routines for a script:
587 <pre class="codesample">
588 source mylibrary
589 </pre>
590 rather than rewriting the routine every time.
591 <p>
592 In fact, the <strong>Deal</strong> kit comes with a file called <span class="code">lib/utility.tcl</span>, which is just such a library of routines the author of <strong>Deal
593 </strong> found himself re-using.
594
595 <h3> <a name="accept">Revisiting <span class="code">accept</span> and <span class="code">reject</span></a></h3>
596 The directives, <span class="code">accept</span> and <span class="code">reject</span>, can be used
597 in more complicated ways that are sometimes more efficient and
598 sometimes more readable.
599 <p>
600 Here is the <span class="code">main</span> script from the <span class="code">notrump</span> example
601 using some odd constructs:
602 <pre class="codesample">
603 main {
604 reject unless {[notrump north $NTmin $NTmax]}
605 accept if {[jacobyinvite south $NTmin $NTmax]}
606 }
607 </pre>
608 Some people might find this more readable. The first line says
609 we are going to reject the deal <em>unless</em> the condition
610 is true. The second conditional says we are going to accept
611 the deal <em>if</em> the expression evaluates as true.
612 <p>
613 Multiple arguments are allowed. The following command:
614 <pre class="codesample">
615 reject unless {<em>expr1</em>} {<em>expr2</em>} ... {<em>exprn</em>}
616 </pre>
617 runs through all of the expressions until it finds one which evaluates
618 as "true". If it does not find a true value, it rejects the hand.
619 Otherwise, deal goes on to the next line in evaluating <span class="code">main</span>.
620 <p>
621 For <span class="code">reject if</span> the deal is rejected if any one of the expressions
622 is true. Similarly, <span class="code">accept if</span> accepts a deal if one of the
623 expressions is true. For <span class="code">accept unless</span>, the deal is accepted
624 <em>unless</em> the one of the expressions is true.
625
626 <hr>
627 This concludes the <a href="#head">Introductory Tutorial</a>. I hope
628 it inspires you to check out the <a href="advanced.html">Deal - Advanced
629 Guide</a> and to <a href="ext-ref.html#tclptrs">learn more about Tcl.</a>
630 Or check out the <a href="commands.html">index of all deal commands.</a>
631 <hr>
632 <table><tr><td><a href="http://bridge.thomasoandrews.com/" class="image">
633 <img style="border:0;width:40px;height:56px" alt="Silhouette" src="graphics/StampSm.gif"></a><td>
634 Thomas Andrews
635 (<a href="mailto:deal&#64;thomasoandrews.com">deal&#64;thomasoandrews.com</a>)
636 Copyright 1996-2010. Deal is covered by the
637 <a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public License.</a>
638 <p>
639 <a href="graphics/falling.jpg"><em>Plane Dealing</em></a> graphic
640 above created using
641 <a href="http://www.povray.org/">POV-Ray.</a>
642 </tr></table>
643 </div>