-
Notifications
You must be signed in to change notification settings - Fork 4
/
algorithms.dtx
1432 lines (1413 loc) · 48.7 KB
/
algorithms.dtx
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
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
% \iffalse
%<*generation>
\begingroup
\input docstrip
\keepsilent
\usedir{tex/latex/algorithms}
\askforoverwritefalse
\preamble
Copyright 1994-2004 Peter Williams <[email protected]>
Copyright 2005-2017 Rogerio Theodoro de Brito <[email protected]>
This document file is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
This document file is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser
General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with this document file; if not, write to the Free Software
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301
USA.
\endpreamble
\nopostamble
\generate{\file{algorithm.sty}{\from{algorithms.dtx}{algorithm}}}
\generate{\file{algorithmic.sty}{\from{algorithms.dtx}{algorithmic}}}
% The following two lines are a trick from wspr
\def\tempa{plain}
\ifx\tempa\fmtname\endgroup\expandafter\bye\fi
\endgroup
%</generation>
%<*driver>
\documentclass{ltxdoc}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{mathpazo}
\usepackage[pdfstartview={FitH}]{hyperref}
\usepackage{algorithm}
\usepackage{algorithmic}
\usepackage{multicol}
\EnableCrossrefs
\CodelineIndex
\RecordChanges
\begin{document}
\DocInput{\jobname.dtx}
\end{document}
%</driver>
%<*algorithms>
\NeedsTeXFormat{LaTeX2e}[1999/12/01]
\ProvidesPackage{algorithm}
[2017/11/08 v0.3 Document Style `algorithm' - floating environment]
%</algorithms>
%<*algorithmic>
\NeedsTeXFormat{LaTeX2e}[1999/12/01]
\ProvidesPackage{algorithmic}
[2017/11/08 v0.3 Document Style `algorithmic']
%</algorithmic>
% % The ``documentation'' follows below the ``fi'' command.
% \fi
%\CheckSum{0}
% \CharacterTable
% {Upper-case \A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z
% Lower-case \a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z
% Digits \0\1\2\3\4\5\6\7\8\9
% Exclamation \! Double quote \" Hash (number) \#
% Dollar \$ Percent \% Ampersand \&
% Acute accent \' Left paren \( Right paren \)
% Asterisk \* Plus \+ Comma \,
% Minus \- Point \. Solidus \/
% Colon \: Semicolon \; Less than \<
% Equals \= Greater than \> Question mark \?
% Commercial at \@ Left bracket \[ Backslash \\
% Right bracket \] Circumflex \^ Underscore \_
% Grave accent \` Left brace \{ Vertical bar \|
% Right brace \} Tilde \~}
%
% \changes{v0.1}{2009/08/24}{Migrated the package to .ins and .dtx format}
% \changes{v0.2}{2009/11/15}{Migrated the package to a single .dtx file}
%
% \GetFileInfo{algorithm.sty}
% \GetFileInfo{algorithmic.sty}
% \DoNotIndex{\#,\$,\%,\&,\@,\\,\{,\},\^,\_,\~,\ }
% \DoNotIndex{\@ne}
% \DoNotIndex{\advance,\begingroup,\catcode,\closein}
% \DoNotIndex{\closeout,\day,\def,\edef,\else,\empty,\endgroup}
%
% \title{The \textsf{algorithms} bundle\thanks{This document
% corresponds to \textsf{algorithms}~\fileversion,
% dated~\filedate.}}
% \author{Rog\'erio Theodoro de Brito\\
% \href{mailto:[email protected]}{\texttt{[email protected]}}}
%
% \newcommand{\keyword}[1]{\texttt{#1}}
% \newcommand{\nameoffile}[1]{\texttt{#1}}
%
% \setcounter{tocdepth}{2}
%
% \addtocontents{toc}{\protect\begin{multicols}{2}}
% \maketitle
% \tableofcontents
% \listofalgorithms
%
% % \newtheorem{warning}{Warning}
% \renewcommand{\thewarning}{}
%
% \section{Introduction}
%
% This package provides two environments, \keyword{algorithmic} and
% \keyword{algorithm}, which are designed to be used together but may,
% depending on the necessities of the user, be used separately.
%
% The \keyword{algorithmic} environment provides an environment for
% describing algorithms and the \keyword{algorithm} environment provides
% a ``float'' wrapper for algorithms (implemented using
% \keyword{algorithmic} or some other method at the users's option).
% The reason for two environments being provided is to allow the user
% maximum flexibility.
%
% This work may be distributed and/or modified under the conditions of
% the GNU Lesser General Public License, either version 2 of the
% License, or (at your option) any later version, as published by the
% Free Software Foundation. See the file \nameoffile{COPYING} included
% in this package for further details.
%
% Currently, this package consists of the following files:
% \begin{itemize}
% \item \nameoffile{algorithms.dtx}: the source file
% \item \nameoffile{COPYING}: the license file
% \item \nameoffile{README}: remarks about the package
% \item \nameoffile{THANKS}: mentions of contributions
% \end{itemize}
%
% Starting with with the 2009-08-24 release, the package is now
% versioned and this document corresponds to version~\fileversion.
%
% If you use this package, the author would kindly appreciate if you
% mentioned it in your documents, so as to let the package be better
% known and have more contributors, to make it better for the community
% itself. This is \emph{not} required by the license: it's just a
% friendly request.
%
% \subsection{Development and Support}
%
% The source code for the bunde is currently hosted in a \texttt{git}
% repository at \url{http://github.com/rbrito/algorithms}.
%
% The author welcomes any contribution and also tries to address any bugs or
% feature requests that may be filed on the issue tracker at
% \url{http://github.com/rbrito/algorithms/issues}.
%
% \section{Installation}
%
% The installation procedure of \textsf{algorithms} consists basically
% of two steps:
% \begin{quote}
% \texttt{tex algorithms.dtx}
% \end{quote}
% and the \nameoffile{.sty} files will be generated. Copy them to a
% place that is referenced by your \LaTeX{} distribution. To generate
% the documentation, type:
% \begin{quote}
% \texttt{latex algorithms.dtx}
% \end{quote}
%
% \section[Environment: \keyword{algorithmic}]%
% {The \keyword{algorithmic} Environment}
% \label{sec:algorithmic-envir}
% Within an \keyword{algorithmic} a number of commands for typesetting
% popular algorithmic constructs are available. In general, the
% commands provided can be arbitrarily nested to describe quite complex
% algorithms. An optional argument to the \verb+\begin{algorithmic}+
% statement can be used to turn on line numbering by giving a positive
% integer indicating the required frequency of line numbering. For
% example, \verb+\begin{algorithmic}[5]+ would cause every fifth line
% to be numbered.
%
% \subsection{The Simple Statement}
%
% The simple statement takes the form
% \begin{verbatim}
% \STATE <text>
% \end{verbatim}
% and is used for simple statements. For example,
% \begin{verbatim}
% \begin{algorithmic}
% \STATE $S \leftarrow 0$
% \end{algorithmic}
% \end{verbatim}
% would produce
% \begin{algorithmic}
% \STATE $S \leftarrow 0$
% \end{algorithmic}
% With line numbering selected for every line, using,
% \begin{verbatim}
% \begin{algorithmic}[1]
% \STATE $S \leftarrow 0$
% \end{algorithmic}
% \end{verbatim}
% we would get
% \begin{algorithmic}[1]
% \STATE $S \leftarrow 0$
% \end{algorithmic}
%
% \begin{warning}
% For users of earlier versions of \keyword{algorithmic} this
% construct is a cause of an incompatibility. In the earlier version,
% instead of starting simple statements with the \verb+\STATE+
% command, simple statements were entered as free text and terminated
% with \verb+\\+ command. Unfortunately, this simpler method failed
% to survive the modifications necessary for statement numbering.
% However, the \verb+\\+ command can still be used to force a line
% break within a simple statement.
% \end{warning}
%
%\subsection{The \emph{if-then-else} Statement}
%
% The \emph{if-then-else} construct takes the forms:
% \begin{verbatim}
% \IF{<condition>} <text> \ENDIF
% \IF{<condition>} <text1> \ELSE <text2> \ENDIF
% \IF{<condition1>} <text1> \ELSIF{<condition2>} <text2> \ELSE <text3> \ENDIF
% \end{verbatim}
%
% In the third of these forms there is no limit placed on the number of
% \verb+\ELSIF{<condition>}+ that may be used. For example,
% \begin{verbatim}
% \begin{algorithmic}
% \IF{some condition is true}
% \STATE do some processing
% \ELSIF{some other condition is true}
% \STATE do some different processing
% \ELSIF{some even more bizarre condition is met}
% \STATE do something else
% \ELSE
% \STATE do the default actions
% \ENDIF
% \end{algorithmic}
% \end{verbatim}
% would produce
% \begin{algorithmic}
% \IF{some condition is true}
% \STATE do some processing
% \ELSIF{some other condition is true}
% \STATE do some different processing
% \ELSIF{some even more bizarre condition is met}
% \STATE do something else
% \ELSE
% \STATE do the default actions
% \ENDIF
% \end{algorithmic}
% with appropriate indentations.
%
% \subsection{The \emph{for} Loop}
%
% The \emph{for} loop takes two forms. Namely:
% \begin{verbatim}
% \FOR{<condition>} <text> \ENDFOR
% \FORALL{<condition>} <text> \ENDFOR
% \end{verbatim}
%
% \noindent For example,
% \begin{verbatim}
% \begin{algorithmic}
% \FOR{$i=0$ to $10$}
% \STATE carry out some processing
% \ENDFOR
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \FOR{$i=0$ to $10$}
% \STATE carry out some processing
% \ENDFOR
% \end{algorithmic}
% and
% \begin{verbatim}
% \begin{algorithmic}[1]
% \FORALL{$i$ such that $0\leq i\leq 10$}
% \STATE carry out some processing
% \ENDFOR
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}[1]
% \FORALL{$i$ such that $0\leq i\leq 10$}
% \STATE carry out some processing
% \ENDFOR
% \end{algorithmic}
%
% \subsubsection{The \emph{to} Connective}
% As may be clear from the usage of loops above, we usually want to
% specify ranges over which a variable will assume values. To help make
% this typographically distinct, the \keyword{algorithmic} package now
% supports the \algorithmicto{} connective, which can be used like:
% \begin{verbatim}
% \begin{algorithmic}
% \FOR{$i=0$ \TO $10$}
% \STATE carry out some processing
% \ENDFOR
% \end{algorithmic}
% \end{verbatim}
% to produce the output
% \begin{algorithmic}
% \FOR{$i=0$ \TO $10$}
% \STATE carry out some processing
% \ENDFOR
% \end{algorithmic}
%
% \subsection{The \emph{while} Loop}
%
% The \emph{while} loop takes the form
% \begin{verbatim}
% \WHILE{<condition>} <text> \ENDWHILE
% \end{verbatim}
% For example,
% \begin{verbatim}
% \begin{algorithmic}
% \WHILE{some condition holds}
% \STATE carry out some processing
% \ENDWHILE
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \WHILE{some condition holds}
% \STATE carry out some processing
% \ENDWHILE
% \end{algorithmic}
%
% \subsection{The \emph{repeat-until} Loop}
%
% The \emph{repeat-until} loop takes the form.
% \begin{verbatim}
% \REPEAT <text> \UNTIL{<condition>}
% \end{verbatim}
% For example,
% \begin{verbatim}
% \begin{algorithmic}
% \REPEAT
% \STATE carry out some processing
% \UNTIL{some condition is met}
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \REPEAT
% \STATE carry out some processing
% \UNTIL{some condition is met}
% \end{algorithmic}
%
% \subsection{The Infinite Loop}
%
% The infinite loop takes the form.
% \begin{verbatim}
% \LOOP <text> \ENDLOOP
% \end{verbatim}
% For example,
% \begin{verbatim}
% \begin{algorithmic}
% \LOOP
% \STATE this processing will be repeated forever
% \ENDLOOP
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \LOOP
% \STATE this processing will be repeated forever
% \ENDLOOP
% \end{algorithmic}
%
% \subsection{Loop Control -- \emph{break} and \emph{continue}}
%
% There are two specific commands used to control any loop structure. These
% commands are present in most of programming languages and can be used for
% algorithm description.
%
% The first one is \emph{break}, used to terminate immediately the loop.
%
% \emph{break} can be used with the follow form:
% \begin{verbatim}
% \BREAK
% \end{verbatim}
%
% The second one is \emph{continue}, used to jump to the next iteration of the
% loop. All the commands after \emph{continue} will not run for the current loop
% cycle.
%
% \emph{continue} can be used with the follow form:
% \begin{verbatim}
% \CONTINUE
% \end{verbatim}
%
% \subsection{The Logical Connectives}
%
% The connectives \algorithmicand, \algorithmicor, \algorithmicxor{} and
% \algorithmicnot{} can be used in boolean expressions in the familiar,
% expected way:
% \begin{verbatim}
% <expression> \AND <expression>
% <expression> \OR <expression>
% <expression> \XOR <expression>
% \NOT <expression>
% \end{verbatim}
% according to their arity.\footnote{But there is nothing that prevents
% the user from violating the arity, from a syntatic point of view.}
% For example,
% \begin{verbatim}
% \begin{algorithmic}
% \IF{\NOT ($year \bmod 400$ \XOR $year \bmod 100$ \XOR $year \bmod 4$)}
% \STATE $year$ does not represent a leap year.
% \ENDIF
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \IF{\NOT ($year \bmod 400$ \XOR $year \bmod 100$ \XOR $year \bmod 4$)}
% \STATE $year$ does not represent a leap year.
% \ENDIF
% \end{algorithmic}
%
% \subsection{The Precondition}
%
% The precondition (that must be met if an algorithm is to correctly
% execute) takes the form:
% \begin{verbatim}
% \REQUIRE <text>
% \end{verbatim}
% For example,
% \begin{verbatim}
% \begin{algorithmic}
% \REQUIRE $x \neq 0$ and $n \geq 0$
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \REQUIRE $x \neq 0$ and $n \geq 0$
% \end{algorithmic}
%
% \subsection{The Postcondition}
%
% The postcondition (that must be met after an algorithm has correctly
% executed) takes the form:
% \begin{verbatim}
% \ENSURE <text>
% \end{verbatim}
% For example,
% \begin{verbatim}
% \begin{algorithmic}
% \ENSURE $x \neq 0$ and $n \geq 0$
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \ENSURE $x \neq 0$ and $n \geq 0$
% \end{algorithmic}
%
% \subsection{Returning Values}
%
% The \keyword{algorithmic} environment offers a special statement for
% explicitly returning values in algorithms. It has the syntax:
% \begin{verbatim}
% \RETURN <text>
% \end{verbatim}
% For example,
% \begin{verbatim}
% \begin{algorithmic}
% \RETURN $(x+y)/2$
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \RETURN $(x+y)/2$
% \end{algorithmic}
%
%
% \subsubsection{The ``true'' and ``false'' Values}
%
% Since many algorithms have the necessity of returning \emph{true} or
% \emph{false} values, \keyword{algorithms}, starting with version
% 2006-06-02, includes the keywords \verb+\TRUE+ and \verb+\FALSE+,
% which are intented to print the values in a standard fashion, like the
% following snippet of an algorithm to decide if an integer $n$ is even or
% odd:
% \begin{verbatim}
% \begin{algorithmic}
% \IF{$n$ is odd}
% \RETURN \TRUE
% \ELSE
% \RETURN \FALSE
% \ENDIF
% \end{algorithmic}
% \end{verbatim}
% The code above produces the following output:
% \begin{algorithmic}
% \IF{$n$ is odd}
% \RETURN \TRUE
% \ELSE
% \RETURN \FALSE
% \ENDIF
% \end{algorithmic}
%
% \subsection{Printing Messages}
%
% Another feature of the \keyword{algorithmic} environment is that it
% currently provides a standard way of printing values (which is an
% operation used enough to merit its own keyword). It has the syntax:
% \begin{verbatim}
% \PRINT <text>
% \end{verbatim}
% For example,
% \begin{verbatim}
% \begin{algorithmic}
% \PRINT \texttt{``Hello, World!''}
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \PRINT \texttt{``Hello, World!''}
% \end{algorithmic}
%
% \subsection{Comments}
%
% Comments may be inserted at most points in an algorithm using the form:
% \begin{verbatim}
% \COMMENT{<text>}
% \end{verbatim}
% For example,
% \begin{verbatim}
% \begin{algorithmic}
% \STATE do something \COMMENT{this is a comment}
% \end{algorithmic}
% \end{verbatim}
% produces
% \begin{algorithmic}
% \STATE do something \COMMENT{this is a comment}
% \end{algorithmic}
% Because the mechanisms used to build the various algorithmic structures
% make it difficult to use the above mechanism for placing comments at the
% end of the first line of a construct, the commands \verb+\IF+,
% \verb+\ELSIF+, \verb+\ELSE+, \verb+\WHILE+, \verb+\FOR+, \verb+\FORALL+,
% \verb+\REPEAT+ and \verb+\LOOP+ all take an optional argument which will
% be treated as a comment to be placed at the end of the line on which
% they appear. For example,
% \begin{algorithmic}
% \REPEAT[this is comment number one]
% \IF[this is comment number two]{condition one is met}
% \STATE do something
% \ELSIF[this is comment number three]{condition two is met}
% \STATE do something else
% \ELSE[this is comment number four]
% \STATE do nothing
% \ENDIF
% \UNTIL{hell freezes over}
% \end{algorithmic}
%
% \subsection{An Example}
%
% The following example demonstrates the use of the \keyword{algorithmic}
% environment to describe a complete algorithm. The following input
% \begin{verbatim}
% \begin{algorithmic}
% \REQUIRE $n \geq 0$
% \ENSURE $y = x^n$
% \STATE $y \leftarrow 1$
% \STATE $X \leftarrow x$
% \STATE $N \leftarrow n$
% \WHILE{$N \neq 0$}
% \IF{$N$ is even}
% \STATE $X \leftarrow X \times X$
% \STATE $N \leftarrow N / 2$
% \ELSE[$N$ is odd]
% \STATE $y \leftarrow y \times X$
% \STATE $N \leftarrow N - 1$
% \ENDIF
% \ENDWHILE
% \end{algorithmic}
% \end{verbatim}
% will produce
% \begin{algorithmic}
% \REQUIRE $n \geq 0$
% \ENSURE $y = x^n$
%
% \STATE $y \leftarrow 1$
% \STATE $X \leftarrow x$
% \STATE $N \leftarrow n$
% \WHILE{$N \neq 0$}
% \IF{$N$ is even}
% \STATE $X \leftarrow X \times X$
% \STATE $N \leftarrow N / 2$
% \ELSE[$N$ is odd]
% \STATE $y \leftarrow y \times X$
% \STATE $N \leftarrow N - 1$
% \ENDIF
% \ENDWHILE
% \end{algorithmic}
% which is an algorithm for finding the value of a number taken to a
% non-negative power.
%
% \subsection[Options/Customization]%
% {Options and Customization}
%
% There is a single option, \keyword{noend}\label{kwd:noend} that may be
% invoked when the \texttt{algorithmic} package is loaded. With this
% option invoked the \emph{end} statements are omitted in the output.
% This allows space to be saved in the output document when this is an
% issue.
%
% \subsubsection{Changing Indentation}
% \label{sec:changing-indentation}
% In the spirit of saving vertical space (which is especially important
% when submitting a paper for a journal, where space is frequently limited
% for authors), the \keyword{algorithmic} environment offers, beginning
% with the version released in 2005-05-08, a way to control the amount of
% indentation that is used by a given algorithm.
%
% The amount of indentation to be used is given by the command
% \begin{verbatim}
% \algsetup{indent=length}
% \end{verbatim}
% where \emph{length} is any valid length used by \TeX. The default value
% of the indentation used by the \keyword{algorithmic} environment is $1$
% em (for ``backward compatibility reasons''), but a value of $2$ em or
% more is recommended, depending on the publication. For example, the
% snippet
% \begin{verbatim}
% \algsetup{indent=2em}
% \begin{algorithmic}[1]
% \STATE $a \leftarrow 1$
% \IF{$a$ is even}
% \PRINT ``$a$ is even''
% \ELSE
% \PRINT ``$a$ is odd''
% \end{algorithmic}
% \end{verbatim}
% produces
% \algsetup{indent=2em}
% \begin{algorithmic}[1]
% \STATE $a \leftarrow 1$
% \IF{$a$ is even}
% \PRINT ``$a$ is even''
% \ELSE
% \PRINT ``$a$ is odd''
% \ENDIF
% \end{algorithmic}
% while
% \begin{verbatim}
% \algsetup{indent=5em}
% \begin{algorithmic}[1]
% \STATE $a \leftarrow 1$
% \IF{$a$ is even}
% \PRINT ``$a$ is even''
% \ELSE
% \PRINT ``$a$ is odd''
% \end{algorithmic}
% \end{verbatim}
% would produce
% \algsetup{indent=5em}
% \begin{algorithmic}[1]
% \STATE $a \leftarrow 1$
% \IF{$a$ is even}
% \PRINT ``$a$ is even''
% \ELSE
% \PRINT ``$a$ is odd''
% \ENDIF
% \end{algorithmic}
% \algsetup{indent=1em}
%
% The intended use of this option is to allow the author to omit the
% \emph{end} (see Section~\ref{kwd:noend} for details) statements without
% loosing readability, by increasing the amount of indentation to a
% suitable level.
%
% \subsubsection{Changing Line Numbering}
%
% As mentioned in Section~\ref{sec:algorithmic-envir} and illustrated in
% Section~\ref{sec:changing-indentation}, \keyword{algorithms} already
% provides you with the possibility of numbering lines.
%
% Starting with the version released in 2005-07-05, you can now change two
% aspects of line numbering: the size of the line numbers (which, by
% default, is \verb+\footnotesize+) and the delimiter used to separate the
% line number from the code (which, by default, is \verb+:+, i.e., a
% colon).
%
% You can change the size of the line numbers using the command:
% \begin{verbatim}
% \algsetup{linenosize=size}
% \end{verbatim}
% where \emph{size} is any of the various commands provided by \LaTeX\ to
% change the size of the font to be used. Among others, useful values are
% \verb+\tiny+, \verb+\scriptsize+, \verb+\footnotesize+ and
% \verb+\small+. Please see the complete list of sizes in your \LaTeX\
% documentation.
%
% As another frequently requested feature, you can change the delimiter
% used with the line numbers by issuing the command:
% \begin{verbatim}
% \algsetup{linenodelimiter=delimiter}
% \end{verbatim}
% where \emph{delimiter} is any ``well-formed'' string, including the
% empty string. With this command, you can change the colon to a period
% (\verb+.+) by issuing the command
% \begin{verbatim}
% \algsetup{linenodelimiter=.}
% \end{verbatim}
% or even omit the delimiter, by specifying the empty string or a space
% (\verb+\ +), whatever seems best for your document.
%
% As an example of such commands, the code produced by
% \begin{verbatim}
% \algsetup{
% linenosize=\small,
% linenodelimiter=.
% }
% \begin{algorithmic}[1]
% \STATE $i \leftarrow 10$
% \RETURN $i$
% \end{algorithmic}
% \end{verbatim}
% would be something like
%
% \algsetup{
% linenosize=\small,
% linenodelimiter=.
% }
% \begin{algorithmic}[1]
% \STATE $i \leftarrow 10$
% \RETURN $i$
% \end{algorithmic}
% \algsetup{linenosize=\footnotesize,
% linenodelimiter=:}
%
% \subsubsection{Customization}
%
% In order to facilitate the use of this package with foreign languages,
% all of the words in the output are produced via redefinable macro
% commands. The default definitions of these macros are:
% \begin{verbatim}
% \newcommand{\algorithmicrequire}{\textbf{Require:}}
% \newcommand{\algorithmicensure}{\textbf{Ensure:}}
% \newcommand{\algorithmicend}{\textbf{end}}
% \newcommand{\algorithmicif}{\textbf{if}}
% \newcommand{\algorithmicthen}{\textbf{then}}
% \newcommand{\algorithmicelse}{\textbf{else}}
% \newcommand{\algorithmicelsif}{\algorithmicelse\ \algorithmicif}
% \newcommand{\algorithmicendif}{\algorithmicend\ \algorithmicif}
% \newcommand{\algorithmicfor}{\textbf{for}}
% \newcommand{\algorithmicforall}{\textbf{for all}}
% \newcommand{\algorithmicdo}{\textbf{do}}
% \newcommand{\algorithmicendfor}{\algorithmicend\ \algorithmicfor}
% \newcommand{\algorithmicwhile}{\textbf{while}}
% \newcommand{\algorithmicendwhile}{\algorithmicend\ \algorithmicwhile}
% \newcommand{\algorithmicloop}{\textbf{loop}}
% \newcommand{\algorithmicendloop}{\algorithmicend\ \algorithmicloop}
% \newcommand{\algorithmicupon}{\textbf{upon}}
% \newcommand{\algorithmicendupon}{\algorithmicend\ \algorithmicupon}
% \newcommand{\algorithmicproc}{\textbf{procedure}}
% \newcommand{\algorithmicendproc}{\algorithmicend\ \algorithmicproc}
% \newcommand{\algorithmicrepeat}{\textbf{repeat}}
% \newcommand{\algorithmicendrepeat}{\algorithmicend\ \algorithmicrepeat}
% \newcommand{\algorithmicuntil}{\textbf{until}}
% \newcommand{\algorithmicprint}{\textbf{print}}
% \newcommand{\algorithmiccontinue}{\textbf{continue}}
% \newcommand{\algorithmicbreak}{\textbf{break}}
% \newcommand{\algorithmicreturn}{\textbf{return}}
% \newcommand{\algorithmictrue}{\textbf{true}}
% \newcommand{\algorithmicfalse}{\textbf{false}}
% \end{verbatim}
%
% If you would like to change the definition of these commands to another
% content, then you should use, in your own document, the standard
% \LaTeX{} command \keyword{renewcommand}, with an usage like this:
% \begin{verbatim}
% \renewcommand{\algorithmicrequire}{\textbf{Input:}}
% \renewcommand{\algorithmicensure}{\textbf{Output:}}
% \end{verbatim}
%
% \paragraph{About the Way Comments Are Formatted}
%
% The formatting of comments is implemented via a single argument command
% macro which may also be redefined. The default definition is
% \begin{verbatim}
% \newcommand{\algorithmiccomment}[1]{\{#1\}}
% \end{verbatim}
% and another option that may be interesting for users familiar with
% C-like languages is to redefine the comments to be
% \begin{verbatim}
% \renewcommand{\algorithmiccomment}[1]{// #1}
% \end{verbatim}
% Comments produced this way would be like this:
% \renewcommand{\algorithmiccomment}[1]{// #1}
% \begin{algorithmic}
% \STATE $i \leftarrow i + 1$ \COMMENT{Increments $i$}
% \end{algorithmic}
% This second way to present comments may become the default in a future
% version of this package.
%
% \section[Environment: \keyword{algorithm}]%
% {The \keyword{algorithm} Environment}
%
% \subsection{General}
%
% When placed within the text without being encapsulated in a floating
% environment \texttt{algorithmic} environments may be split over a page
% boundary, greatly detracting from their appearance.\footnote{This is the
% expected behaviour for floats in \LaTeX. If you don't care about
% having your algorithm split between pages, then one option that you
% have is to ignore the \texttt{algorithm} environment.} In addition, it
% is useful to have algorithms numbered for reference and for lists of
% algorithms to be appended to the list of contents. The
% \texttt{algorithm} environment is meant to address these concerns by
% providing a floating environment for algorithms.
%
% \subsection{An Example}
% To illustrate the use of the \texttt{algorithm} environment, the
% following text
% \begin{verbatim}
% \begin{algorithm}
% \caption{Calculate $y = x^n$}
% \label{alg1}
% \begin{algorithmic}
% \REQUIRE $n \geq 0 \vee x \neq 0$
% \ENSURE $y = x^n$
% \STATE $y \leftarrow 1$
% \IF{$n < 0$}
% \STATE $X \leftarrow 1 / x$
% \STATE $N \leftarrow -n$
% \ELSE
% \STATE $X \leftarrow x$
% \STATE $N \leftarrow n$
% \ENDIF
% \WHILE{$N \neq 0$}
% \IF{$N$ is even}
% \STATE $X \leftarrow X \times X$
% \STATE $N \leftarrow N / 2$
% \ELSE[$N$ is odd]
% \STATE $y \leftarrow y \times X$
% \STATE $N \leftarrow N - 1$
% \ENDIF
% \ENDWHILE
% \end{algorithmic}
% \end{algorithm}
% \end{verbatim}
% produces Algorithm~\ref{alg1} which is a slightly modified version of
% the earlier algorithm for determining the value of a number taken to an
% integer power. In this case, provided the power may be negative
% provided the number is not zero.
%
% \begin{algorithm}[H]
% \caption{Calculate $y = x^n$}
% \label{alg1}
% \begin{algorithmic}
% \REQUIRE $n \geq 0 \vee x \neq 0$
% \ENSURE $y = x^n$
%
% \STATE $y \leftarrow 1$
% \IF{$n < 0$}
% \STATE $X \leftarrow 1 / x$
% \STATE $N \leftarrow -n$
% \ELSE
% \STATE $X \leftarrow x$
% \STATE $N \leftarrow n$
% \ENDIF
%
% \WHILE{$N \neq 0$}
% \IF{$N$ is even}
% \STATE $X \leftarrow X \times X$
% \STATE $N \leftarrow N / 2$
% \ELSE[$N$ is odd]
% \STATE $y \leftarrow y \times X$
% \STATE $N \leftarrow N - 1$
% \ENDIF
% \ENDWHILE
% \end{algorithmic}
% \end{algorithm}
%
% The command \verb+\listofalgorithms+ may be used to produce a list of
% algorithms as part of the table contents as shown at the beginning of
% this document. An auxiliary file with a suffix of \texttt{.loa} is
% produced when this feature is used.
%
% \subsection{Options}
%
% The appearance of the typeset algorithm may be changed by use of the
% options: \texttt{plain}, \texttt{boxed} or \texttt{ruled} during the
% loading of the \texttt{algorithm} package. The default option is
% \texttt{ruled}.
%
% The numbering of algorithms can be influenced by providing the name of
% the document component within which numbering should be recommenced.
% The legal values for this option are: \texttt{part}, \texttt{chapter},
% \texttt{section}, \texttt{subsection}, \texttt{subsubsection} or
% \texttt{nothing}. The default value is \texttt{nothing} which causes
% algorithms to be numbered sequentially throughout the document.
%
% \subsection{Customization}
%
% In order to facilitate the use of this package with foreign languages,
% methods have been provided to facilitate the necessary modifications.
%
% The title used in the caption within \texttt{algorithm} environment can
% be set by use of the standard \verb+\floatname+ command which is
% provided as part of the \texttt{float} package which was used to
% implement this package. For example,
% \begin{verbatim}
% \floatname{algorithm}{Procedure}
% \end{verbatim}
% would cause \textbf{Procedure} to be used instead of \textbf{Algorithm}
% within the caption of algorithms.
%
% In a manner analogous to that available for the built in floating
% environments, the heading used for the list of algorithms may be changed
% by redefining the command \verb+listalgorithmname+. The default
% definition for this command is
% \begin{verbatim}
% \newcommand{\listalgorithmname}{List of Algorithms}
% \end{verbatim}
%
% \subsubsection{Placement of Algorithms}
%
% One important fact that many users may not have noticed is that the
% \texttt{algorithm} environment is actually built with the \texttt{float}
% package and \texttt{float}, in turn, uses David Carlisle's \textsf{here}
% style option. This means that the floats generated by the
% \texttt{algorithm} environment accept a special option, namely,
% \textbf{[H]}, with a capital `H', instead of the usual `h' offered by
% plain \LaTeX.
%
% This option works as a stronger request of ``please put the float
% here'': instead of just a suggestion for \LaTeX, it actually means ``put
% this float HERE'', which is something desired by many. The two
% algorithms typeset in this document use this option.
%
% \medskip
% \begin{warning}
% You \emph{can't} use the `H' positioning option together with the
% usual `h' (for ``here''), `b' (for ``bottom'') etc. This is a
% limitation (as far as I know) of the \texttt{float.sty} package.
% \end{warning}
%
% \section[References in Algorithms]%
% {Labels and References in Algorithms}
%
% With the release of 2005-07-05, now \keyword{algorithmic} accepts labels
% and references to specific lines of a given algorithm, so you don't have
% to hardcode the line numbers yourself when trying to explain what the
% code does in your texts. Thanks to Arnaud Legrand for the suggestion
% and patch for this highly missed feature.
%
% An example of its use is shown in Algorithm~\ref{alg2}.
% \begin{algorithm}[H]
% \caption{Calculate $y = x^n$}
% \label{alg2}
% \begin{algorithmic}[1]
% \REQUIRE $n \geq 0 \vee x \neq 0$
% \ENSURE $y = x^n$
% \STATE $y \leftarrow 1$
% \IF{$n < 0$}
% \STATE $X \leftarrow 1 / x$
% \STATE $N \leftarrow -n$
% \ELSE
% \STATE $X \leftarrow x$
% \STATE $N \leftarrow n$
% \ENDIF
% \WHILE{$N \neq 0$}
% \IF{$N$ is even}\label{alg:n-is-even}
% \STATE $X \leftarrow X \times X$
% \STATE $N \leftarrow N / 2$
% \ELSE\label{alg:n-is-odd}
% \STATE $y \leftarrow y \times X$
% \STATE $N \leftarrow N - 1$
% \ENDIF
% \ENDWHILE
% \end{algorithmic}
% \end{algorithm}
% See that, in line~\ref{alg:n-is-even}, we deal with the case of $N$
% being even, while, in line~\ref{alg:n-is-odd}, we give treatment to the
% case of $N$ being odd. The numbers you see on this document were
% generated automatically from the source document.
%
%
% \section[Known Issues]{Issues Between \texttt{algorithms} and
% \href{http://www.ctan.org/tex-archive/help/Catalogue/entries/tocbibind.html}{\texttt{tocbibind}}
% or \href{http://www.ctan.org/tex-archive/help/Catalogue/entries/memoir.html}{\texttt{memoir}}}
%
% It
% \href{http://groups.google.com/group/comp.text.tex/browse_thread/thread/4094e0c4f4fbd83e/a80a3f4666c794f0?fwc=1}{has
% been discussed} in late 2005 that \texttt{algorithms} may have bad
% interactions with the
% \href{http://www.ctan.org/tex-archive/help/Catalogue/entries/tocbibind.html}{\texttt{tocbibind}}
% or the
% \href{http://www.ctan.org/tex-archive/help/Catalogue/entries/memoir.html}{\texttt{memoir}}