+\r
+%% bare_adv.tex\r
+%% V1.3\r
+%% 2007/01/11\r
+%% by Michael Shell\r
+%% See: \r
+%% http://www.michaelshell.org/\r
+%% for current contact information.\r
+%%\r
+%% This is a skeleton file demonstrating the advanced use of IEEEtran.cls\r
+%% (requires IEEEtran.cls version 1.7 or later) with an IEEE Computer\r
+%% Society journal paper.\r
+%%\r
+%% Support sites:\r
+%% http://www.michaelshell.org/tex/ieeetran/\r
+%% http://www.ctan.org/tex-archive/macros/latex/contrib/IEEEtran/\r
+%% and\r
+%% http://www.ieee.org/\r
+\r
+%%*************************************************************************\r
+%% Legal Notice:\r
+%% This code is offered as-is without any warranty either expressed or\r
+%% implied; without even the implied warranty of MERCHANTABILITY or\r
+%% FITNESS FOR A PARTICULAR PURPOSE! \r
+%% User assumes all risk.\r
+%% In no event shall IEEE or any contributor to this code be liable for\r
+%% any damages or losses, including, but not limited to, incidental,\r
+%% consequential, or any other damages, resulting from the use or misuse\r
+%% of any information contained here.\r
+%%\r
+%% All comments are the opinions of their respective authors and are not\r
+%% necessarily endorsed by the IEEE.\r
+%%\r
+%% This work is distributed under the LaTeX Project Public License (LPPL)\r
+%% ( http://www.latex-project.org/ ) version 1.3, and may be freely used,\r
+%% distributed and modified. A copy of the LPPL, version 1.3, is included\r
+%% in the base LaTeX documentation of all distributions of LaTeX released\r
+%% 2003/12/01 or later.\r
+%% Retain all contribution notices and credits.\r
+%% ** Modified files should be clearly indicated as such, including **\r
+%% ** renaming them and changing author support contact information. **\r
+%%\r
+%% File list of work: IEEEtran.cls, IEEEtran_HOWTO.pdf, bare_adv.tex,\r
+%% bare_conf.tex, bare_jrnl.tex, bare_jrnl_compsoc.tex\r
+%%*************************************************************************\r
+\r
+% *** Authors should verify (and, if needed, correct) their LaTeX system ***\r
+% *** with the testflow diagnostic prior to trusting their LaTeX platform ***\r
+% *** with production work. IEEE's font choices can trigger bugs that do ***\r
+% *** not appear when using other class files. ***\r
+% The testflow support page is at:\r
+% http://www.michaelshell.org/tex/testflow/\r
+\r
+\r
+\r
+% IEEEtran V1.7 and later provides for these CLASSINPUT macros to allow the\r
+% user to reprogram some IEEEtran.cls defaults if needed. These settings\r
+% override the internal defaults of IEEEtran.cls regardless of which class\r
+% options are used. Do not use these unless you have good reason to do so as\r
+% they can result in nonIEEE compliant documents. User beware. ;)\r
+%\r
+%\newcommand{\CLASSINPUTbaselinestretch}{1.0} % baselinestretch\r
+%\newcommand{\CLASSINPUTinnersidemargin}{1in} % inner side margin\r
+%\newcommand{\CLASSINPUToutersidemargin}{1in} % outer side margin\r
+%\newcommand{\CLASSINPUTtoptextmargin}{1in} % top text margin\r
+%\newcommand{\CLASSINPUTbottomtextmargin}{1in}% bottom text margin\r
+\r
+\r
+\r
+% Note that the a4paper option is mainly intended so that authors in\r
+% countries using A4 can easily print to A4 and see how their papers will\r
+% look in print - the typesetting of the document will not typically be\r
+% affected with changes in paper size (but the bottom and side margins will).\r
+% Use the testflow package mentioned above to verify correct handling of\r
+% both paper sizes by the user's LaTeX system.\r
+%\r
+% Also note that the "draftcls" or "draftclsnofoot", not "draft", option\r
+% should be used if it is desired that the figures are to be displayed in\r
+% draft mode.\r
+%\r
+\documentclass[12pt,journal,compsoc]{IEEEtran}\r
+% The Computer Society requires 12pt.\r
+% If IEEEtran.cls has not been installed into the LaTeX system files,\r
+% manually specify the path to it like:\r
+% \documentclass[10pt,journal,compsoc]{../sty/IEEEtran}\r
+\r
+\r
+% For Computer Society journals, IEEEtran defaults to the use of \r
+% Palatino/Palladio as is done in IEEE Computer Society journals.\r
+% To go back to Times Roman, you can use this code:\r
+%\renewcommand{\rmdefault}{ptm}\selectfont\r
+\r
+\r
+\r
+\r
+\r
+% Some very useful LaTeX packages include:\r
+% (uncomment the ones you want to load)\r
+\r
+\r
+\r
+% *** MISC UTILITY PACKAGES ***\r
+%\r
+%\usepackage{ifpdf}\r
+% Heiko Oberdiek's ifpdf.sty is very useful if you need conditional\r
+% compilation based on whether the output is pdf or dvi.\r
+% usage:\r
+% \ifpdf\r
+% % pdf code\r
+% \else\r
+% % dvi code\r
+% \fi\r
+% The latest version of ifpdf.sty can be obtained from:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/oberdiek/\r
+% Also, note that IEEEtran.cls V1.7 and later provides a builtin\r
+% \ifCLASSINFOpdf conditional that works the same way.\r
+% When switching from latex to pdflatex and vice-versa, the compiler may\r
+% have to be run twice to clear warning/error messages.\r
+\r
+\r
+\r
+\r
+\r
+\r
+% *** CITATION PACKAGES ***\r
+%\r
+\ifCLASSOPTIONcompsoc\r
+ % IEEE Computer Society needs nocompress option\r
+ % requires cite.sty v4.0 or later (November 2003)\r
+ % \usepackage[nocompress]{cite}\r
+\else\r
+ % normal IEEE\r
+ % \usepackage{cite}\r
+\fi\r
+% cite.sty was written by Donald Arseneau\r
+% V1.6 and later of IEEEtran pre-defines the format of the cite.sty package\r
+% \cite{} output to follow that of IEEE. Loading the cite package will\r
+% result in citation numbers being automatically sorted and properly\r
+% "compressed/ranged". e.g., [1], [9], [2], [7], [5], [6] without using\r
+% cite.sty will become [1], [2], [5]--[7], [9] using cite.sty. cite.sty's\r
+% \cite will automatically add leading space, if needed. Use cite.sty's\r
+% noadjust option (cite.sty V3.8 and later) if you want to turn this off.\r
+% cite.sty is already installed on most LaTeX systems. Be sure and use\r
+% version 4.0 (2003-05-27) and later if using hyperref.sty. cite.sty does\r
+% not currently provide for hyperlinked citations.\r
+% The latest version can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/cite/\r
+% The documentation is contained in the cite.sty file itself.\r
+%\r
+% Note that some packages require special options to format as the Computer\r
+% Society requires. In particular, Computer Society papers do not use\r
+% compressed citation ranges as is done in typical IEEE papers\r
+% (e.g., [1]-[4]). Instead, they list every citation separately in order\r
+% (e.g., [1], [2], [3], [4]). To get the latter we need to load the cite\r
+% package with the nocompress option which is supported by cite.sty v4.0\r
+% and later. Note also the use of a CLASSOPTION conditional provided by\r
+% IEEEtran.cls V1.7 and later.\r
+\r
+\r
+\r
+\r
+\r
+% *** GRAPHICS RELATED PACKAGES ***\r
+%\r
+\ifCLASSINFOpdf\r
+ % \usepackage[pdftex]{graphicx}\r
+ % declare the path(s) where your graphic files are\r
+ % \graphicspath{{../pdf/}{../jpeg/}}\r
+ % and their extensions so you won't have to specify these with\r
+ % every instance of \includegraphics\r
+ % \DeclareGraphicsExtensions{.pdf,.jpeg,.png}\r
+\else\r
+ % or other class option (dvipsone, dvipdf, if not using dvips). graphicx\r
+ % will default to the driver specified in the system graphics.cfg if no\r
+ % driver is specified.\r
+ % \usepackage[dvips]{graphicx}\r
+ % declare the path(s) where your graphic files are\r
+ % \graphicspath{{../eps/}}\r
+ % and their extensions so you won't have to specify these with\r
+ % every instance of \includegraphics\r
+ % \DeclareGraphicsExtensions{.eps}\r
+\fi\r
+% graphicx was written by David Carlisle and Sebastian Rahtz. It is\r
+% required if you want graphics, photos, etc. graphicx.sty is already\r
+% installed on most LaTeX systems. The latest version and documentation can\r
+% be obtained at: \r
+% http://www.ctan.org/tex-archive/macros/latex/required/graphics/\r
+% Another good source of documentation is "Using Imported Graphics in\r
+% LaTeX2e" by Keith Reckdahl which can be found as epslatex.ps or\r
+% epslatex.pdf at: http://www.ctan.org/tex-archive/info/\r
+%\r
+% latex, and pdflatex in dvi mode, support graphics in encapsulated\r
+% postscript (.eps) format. pdflatex in pdf mode supports graphics\r
+% in .pdf, .jpeg, .png and .mps (metapost) formats. Users should ensure\r
+% that all non-photo figures use a vector format (.eps, .pdf, .mps) and\r
+% not a bitmapped formats (.jpeg, .png). IEEE frowns on bitmapped formats\r
+% which can result in "jaggedy"/blurry rendering of lines and letters as\r
+% well as large increases in file sizes.\r
+%\r
+% You can find documentation about the pdfTeX application at:\r
+% http://www.tug.org/applications/pdftex\r
+\r
+\r
+\r
+%\usepackage{ps4pdf}\r
+% dvi->ps workflow is required to use such packages as psfrag.sty and\r
+% pstricks.sty. However, Rolf Niepraschk's ps4pdf.sty provides a way to\r
+% apply psfrag/pstricks effects to .eps figures and then get the resultant\r
+% figures in .pdf form. Thus, providing an easier way for migrating from\r
+% .eps to .pdf figures. After ps4pdf.sty loads, if:\r
+% 1. producing .dvi output: the output file will consist ONLY of the\r
+% figures (or other constructs encased within \PSforPDF commands)\r
+% 2. producing .pdf output: pdflatex will look in the filename-pics.pdf\r
+% file, where filename is the basename of the tex document, for the\r
+% graphics (or other constructs encased within \PSforPDF commands).\r
+% NOTE: If you ever change your figures, you must remember to remake\r
+% the filename-pics.pdf file.\r
+%\r
+% This way you can do a:\r
+% \r
+% latex filename\r
+% dvips -Ppdf -o filename-pics.ps filename.dvi\r
+% ps2pdf filename-pics.ps filename-pics.pdf\r
+% \r
+% to produce a filename-pics.pdf graphics container that contains\r
+% .pdf versions of the graphics with psfrag, pstricks, etc. features.\r
+% Note that you will not typically be able to view the figures in \r
+% filename-pics.ps because of an offset. However, you will be able to\r
+% view them in filename-pics.pdf. Also, note that when ps4pdf is in effect\r
+% with .dvi output, you may get harmless over/under full box warnings - \r
+% ignore them. \r
+% Then, run pdflatex:\r
+% \r
+% pdflatex filename\r
+% \r
+% to use pdflatex to make PDF output, automatically using the figures in\r
+% filename-pics.pdf. Alternatively, you could use dvips -i option to\r
+% obtain separate .pdf files for each figure:\r
+%\r
+% dvips -Ppdf -i -E -o fig filename\r
+%\r
+% then convert each figure to pdf via a command such as epstopdf and then\r
+% use pdflatex with these pdf figures and then to dispense with ps4pdf.\r
+%\r
+% Remember to rerun through latex/dvips/ps2pdf if you ever change your\r
+% figures so that filename-pics.pdf gets updated.\r
+% ps4pdf requires David Kastrup's preview-latex and a recent LaTeX system\r
+% (circa 2001 or later). The ps4pdf package and documentation can be\r
+% obtained at: http://www.ctan.org/tex-archive/macros/latex/contrib/ps4pdf/\r
+% The preview-latex package and documentation can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/preview/\r
+%\r
+% provide a bogus \PSforPDF, even when not loading pd4pdf. This way we can\r
+% stop loading ps4pdf.sty if we choose to make separate .pdf versions of\r
+% each of our figures.\r
+\providecommand{\PSforPDF}[1]{#1}\r
+% Note that in order for ps4pdf to work, all commands related to psfrag,\r
+% pstricks, etc. must be called within the PSforPDF command. This applies\r
+% even when *loading* via \usepackage psfrag.sty, etc.\r
+\r
+\r
+%\PSforPDF{\usepackage{psfrag}}\r
+% psfrag.sty was written by Craig Barratt, Michael C. Grant, and\r
+% David Carlisle. It allows you to substitute LaTeX commands for text in\r
+% imported EPS graphic files. In this way, LaTeX symbols can be placed into\r
+% graphics that have been generated by other applications. You must use\r
+% latex->dvips->ps2pdf workflow (not direct pdf output from pdflatex) if\r
+% you wish to use this capability because it works via some PostScript\r
+% tricks. Alternatively, the graphics could be processed as separate files\r
+% via psfrag and dvips, then converted to PDF for inclusion in the main file\r
+% which uses pdflatex. ps4pdf.sty (above) provides a way of doing this all\r
+% at once within the main file.\r
+% Docs are in "The PSfrag System" by Michael C. Grant and David Carlisle.\r
+% There is also some information about using psfrag in "Using Imported\r
+% Graphics in LaTeX2e" by Keith Reckdahl which documents the graphicx\r
+% package (see above). The psfrag package and documentation can be obtained\r
+% at: http://www.ctan.org/tex-archive/macros/latex/contrib/psfrag/\r
+% \r
+% Note that the current version of psfrag does not "turn itself off" when\r
+% running under pdf output. This will result in a harmless warning\r
+% about a non-PDF \special. However, to silence this, a bogus psfrag\r
+% command can be provided instead of loading psfrag.sty when PDF output\r
+% is being used. Thus, a more complex alternative conditional loading scheme\r
+% can be employed instead of the straightforword way above:\r
+%\r
+%\ifCLASSINFOpdf\r
+% if outputting PDF, do not use or load psfrag.sty as current versions\r
+% output a non-PDF special that generates a harmless, but annoying warning.\r
+% Instead, we provide a bogus \psfrag command that does nothing with\r
+% its arguments. This is a tad tricky because \psfrag can have up to six\r
+% arguments four of which are optional: \psfrag{}[][][][]{}\r
+% Code based on that in psfrag.sty\r
+%\makeatletter\r
+%\def\psfrag{\@ifstar{\@BOGUSpsfraga}{\@BOGUSpsfraga}}\r
+%\def\@BOGUSpsfraga{\begingroup\r
+% \@makeother\"\@makeother\*\@makeother\!\@makeother\~%\r
+% \@makeother\:\@makeother\\\@makeother\%\@makeother\#%\r
+% \@makeother\ \@BOGUSpsfragb}\r
+%\def\@BOGUSpsfragb#1{\endgroup\r
+% \@ifnextchar [{\@BOGUSpsfragc}%\r
+% {\@BOGUSpsfrag}}\r
+%\def\@BOGUSpsfragc[#1]{\@ifnextchar [{\@BOGUSpsfragd}%\r
+% {\@BOGUSpsfrag}}\r
+%\def\@BOGUSpsfragd[#1]{\@ifnextchar [{\@BOGUSpsfrage}%\r
+% {\@BOGUSpsfrag}}\r
+%\def\@BOGUSpsfrage[#1]{\@ifnextchar [{\@BOGUSpsfragf}%\r
+% {\@BOGUSpsfrag}}\r
+%\def\@BOGUSpsfragf[#1]{\@BOGUSpsfrag}\r
+%\def\@BOGUSpsfrag#1{\ignorespaces}\r
+%\makeatother\r
+%\else\r
+% using dvi output, load psfrag, but funnel it through PSforPDF\r
+% as required by ps4pdf.sty\r
+%\PSforPDF{\usepackage{psfrag}}\r
+%\fi\r
+\r
+\r
+\r
+\r
+\r
+% *** MATH PACKAGES ***\r
+%\r
+%\usepackage[cmex10]{amsmath}\r
+% A popular package from the American Mathematical Society that provides\r
+% many useful and powerful commands for dealing with mathematics. If using\r
+% it, be sure to load this package with the cmex10 option to ensure that\r
+% only type 1 fonts will utilized at all point sizes. Without this option,\r
+% it is possible that some math symbols, particularly those within\r
+% footnotes, will be rendered in bitmap form which will result in a\r
+% document that can not be IEEE Xplore compliant!\r
+%\r
+% Also, note that the amsmath package sets \interdisplaylinepenalty to 10000\r
+% thus preventing page breaks from occurring within multiline equations. Use:\r
+%\interdisplaylinepenalty=2500\r
+% after loading amsmath to restore such page breaks as IEEEtran.cls normally\r
+% does. amsmath.sty is already installed on most LaTeX systems. The latest\r
+% version and documentation can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/required/amslatex/math/\r
+\r
+\r
+\r
+\r
+\r
+% *** SPECIALIZED LIST PACKAGES ***\r
+%\usepackage{acronym}\r
+% acronym.sty was written by Tobias Oetiker. This package provides tools for\r
+% managing documents with large numbers of acronyms. (You don't *have* to\r
+% use this package - unless you have a lot of acronyms, you may feel that\r
+% such package management of them is bit of an overkill.)\r
+% Do note that the acronym environment (which lists acronyms) will have a\r
+% problem when used under IEEEtran.cls because acronym.sty relies on the\r
+% description list environment - which IEEEtran.cls has customized for\r
+% producing IEEE style lists. A workaround is to declared the longest\r
+% label width via the IEEEtran.cls \IEEEiedlistdecl global control:\r
+%\r
+% \renewcommand{\IEEEiedlistdecl}{\IEEEsetlabelwidth{SONET}}\r
+% \begin{acronym}\r
+%\r
+% \end{acronym}\r
+% \renewcommand{\IEEEiedlistdecl}{\relax}% remember to reset \IEEEiedlistdecl\r
+%\r
+% instead of using the acronym environment's optional argument.\r
+% The latest version and documentation can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/acronym/\r
+\r
+\r
+%\usepackage{algorithmic}\r
+% algorithmic.sty was written by Peter Williams and Rogerio Brito.\r
+% This package provides an algorithmic environment fo describing algorithms.\r
+% You can use the algorithmic environment in-text or within a figure\r
+% environment to provide for a floating algorithm. Do NOT use the algorithm\r
+% floating environment provided by algorithm.sty (by the same authors) or\r
+% algorithm2e.sty (by Christophe Fiorio) as IEEE does not use dedicated\r
+% algorithm float types and packages that provide these will not provide\r
+% correct IEEE style captions. The latest version and documentation of\r
+% algorithmic.sty can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithms/\r
+% There is also a support site at:\r
+% http://algorithms.berlios.de/index.html\r
+% Also of interest may be the (relatively newer and more customizable)\r
+% algorithmicx.sty package by Szasz Janos:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/algorithmicx/\r
+\r
+\r
+\r
+\r
+% *** ALIGNMENT PACKAGES ***\r
+%\r
+%\usepackage{array}\r
+% Frank Mittelbach's and David Carlisle's array.sty patches and improves\r
+% the standard LaTeX2e array and tabular environments to provide better\r
+% appearance and additional user controls. As the default LaTeX2e table\r
+% generation code is lacking to the point of almost being broken with\r
+% respect to the quality of the end results, all users are strongly\r
+% advised to use an enhanced (at the very least that provided by array.sty)\r
+% set of table tools. array.sty is already installed on most systems. The\r
+% latest version and documentation can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/required/tools/\r
+\r
+\r
+%\usepackage{mdwmath}\r
+%\usepackage{mdwtab}\r
+% Also highly recommended is Mark Wooding's extremely powerful MDW tools,\r
+% especially mdwmath.sty and mdwtab.sty which are used to format equations\r
+% and tables, respectively. The MDWtools set is already installed on most\r
+% LaTeX systems. The lastest version and documentation is available at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/mdwtools/\r
+\r
+\r
+% IEEEtran contains the IEEEeqnarray family of commands that can be used to\r
+% generate multiline equations as well as matrices, tables, etc., of high\r
+% quality.\r
+\r
+\r
+%\usepackage{eqparbox}\r
+% Also of notable interest is Scott Pakin's eqparbox package for creating\r
+% (automatically sized) equal width boxes - aka "natural width parboxes".\r
+% Available at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/eqparbox/\r
+\r
+\r
+\r
+\r
+\r
+% *** SUBFIGURE PACKAGES ***\r
+%\ifCLASSOPTIONcompsoc\r
+%\usepackage[tight,normalsize,sf,SF]{subfigure}\r
+%\else\r
+%\usepackage[tight,footnotesize]{subfigure}\r
+%\fi\r
+% subfigure.sty was written by Steven Douglas Cochran. This package makes it\r
+% easy to put subfigures in your figures. e.g., "Figure 1a and 1b". For IEEE\r
+% work, it is a good idea to load it with the tight package option to reduce\r
+% the amount of white space around the subfigures. Computer Society papers\r
+% use a larger font and \sffamily font for their captions, hence the\r
+% additional options needed under compsoc mode. subfigure.sty is already\r
+% installed on most LaTeX systems. The latest version and documentation can\r
+% be obtained at:\r
+% http://www.ctan.org/tex-archive/obsolete/macros/latex/contrib/subfigure/\r
+% subfigure.sty has been superceeded by subfig.sty.\r
+\r
+\r
+%\ifCLASSOPTIONcompsoc\r
+% \usepackage[caption=false]{caption}\r
+% \usepackage[font=normalsize,labelfont=sf,textfont=sf]{subfig}\r
+%\else\r
+% \usepackage[caption=false]{caption}\r
+% \usepackage[font=footnotesize]{subfig}\r
+%\fi\r
+% subfig.sty, also written by Steven Douglas Cochran, is the modern\r
+% replacement for subfigure.sty. However, subfig.sty requires and\r
+% automatically loads Axel Sommerfeldt's caption.sty which will override\r
+% IEEEtran.cls handling of captions and this will result in nonIEEE style\r
+% figure/table captions. To prevent this problem, be sure and preload\r
+% caption.sty with its "caption=false" package option. This is will preserve\r
+% IEEEtran.cls handing of captions. Version 1.3 (2005/06/28) and later \r
+% (recommended due to many improvements over 1.2) of subfig.sty supports\r
+% the caption=false option directly:\r
+%\ifCLASSOPTIONcompsoc\r
+% \usepackage[caption=false,font=normalsize,labelfont=sf,textfont=sf]{subfig}\r
+%\else\r
+% \usepackage[caption=false,font=footnotesize]{subfig}\r
+%\fi\r
+%\r
+% The latest version and documentation can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/subfig/\r
+% The latest version and documentation of caption.sty can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/caption/\r
+\r
+\r
+\r
+\r
+% *** FLOAT PACKAGES ***\r
+%\r
+%\usepackage{fixltx2e}\r
+% fixltx2e, the successor to the earlier fix2col.sty, was written by\r
+% Frank Mittelbach and David Carlisle. This package corrects a few problems\r
+% in the LaTeX2e kernel, the most notable of which is that in current\r
+% LaTeX2e releases, the ordering of single and double column floats is not\r
+% guaranteed to be preserved. Thus, an unpatched LaTeX2e can allow a\r
+% single column figure to be placed prior to an earlier double column\r
+% figure. The latest version and documentation can be found at:\r
+% http://www.ctan.org/tex-archive/macros/latex/base/\r
+\r
+\r
+%\usepackage{stfloats}\r
+% stfloats.sty was written by Sigitas Tolusis. This package gives LaTeX2e\r
+% the ability to do double column floats at the bottom of the page as well\r
+% as the top. (e.g., "\begin{figure*}[!b]" is not normally possible in\r
+% LaTeX2e). It also provides a command:\r
+%\fnbelowfloat\r
+% to enable the placement of footnotes below bottom floats (the standard\r
+% LaTeX2e kernel puts them above bottom floats). This is an invasive package\r
+% which rewrites many portions of the LaTeX2e float routines. It may not work\r
+% with other packages that modify the LaTeX2e float routines. The latest\r
+% version and documentation can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/sttools/\r
+% Documentation is contained in the stfloats.sty comments as well as in the\r
+% presfull.pdf file. Do not use the stfloats baselinefloat ability as IEEE\r
+% does not allow \baselineskip to stretch. Authors submitting work to the\r
+% IEEE should note that IEEE rarely uses double column equations and\r
+% that authors should try to avoid such use. Do not be tempted to use the\r
+% cuted.sty or midfloat.sty packages (also by Sigitas Tolusis) as IEEE does\r
+% not format its papers in such ways.\r
+\r
+\r
+%\ifCLASSOPTIONcaptionsoff\r
+% \usepackage[nomarkers]{endfloat}\r
+% \let\MYoriglatexcaption\caption\r
+% \renewcommand{\caption}[2][\relax]{\MYoriglatexcaption[#2]{#2}}\r
+%\fi\r
+% endfloat.sty was written by James Darrell McCauley and Jeff Goldberg.\r
+% This package may be useful when used in conjunction with IEEEtran.cls'\r
+% captionsoff option. Some IEEE journals/societies require that submissions\r
+% have lists of figures/tables at the end of the paper and that\r
+% figures/tables without any captions are placed on a page by themselves at\r
+% the end of the document. If needed, the draftcls IEEEtran class option or\r
+% \CLASSINPUTbaselinestretch interface can be used to increase the line\r
+% spacing as well. Be sure and use the nomarkers option of endfloat to\r
+% prevent endfloat from "marking" where the figures would have been placed\r
+% in the text. The two hack lines of code above are a slight modification of\r
+% that suggested by in the endfloat docs (section 8.3.1) to ensure that\r
+% the full captions always appear in the list of figures/tables - even if\r
+% the user used the short optional argument of \caption[]{}.\r
+% IEEE papers do not typically make use of \caption[]'s optional argument,\r
+% so this should not be an issue. A similar trick can be used to disable\r
+% captions of packages such as subfig.sty that lack options to turn off\r
+% the subcaptions:\r
+% For subfig.sty:\r
+% \let\MYorigsubfloat\subfloat\r
+% \renewcommand{\subfloat}[2][\relax]{\MYorigsubfloat[]{#2}}\r
+% For subfigure.sty:\r
+% \let\MYorigsubfigure\subfigure\r
+% \renewcommand{\subfigure}[2][\relax]{\MYorigsubfigure[]{#2}}\r
+% However, the above trick will not work if both optional arguments of\r
+% the \subfloat/subfig command are used. Furthermore, there needs to be a\r
+% description of each subfigure *somewhere* and endfloat does not add\r
+% subfigure captions to its list of figures. Thus, the best approach is to\r
+% avoid the use of subfigure captions (many IEEE journals avoid them anyway)\r
+% and instead reference/explain all the subfigures within the main caption.\r
+% The latest version of endfloat.sty and its documentation can obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/endfloat/\r
+%\r
+% The IEEEtran \ifCLASSOPTIONcaptionsoff conditional can also be used\r
+% later in the document, say, to conditionally put the References on a \r
+% page by themselves.\r
+\r
+\r
+\r
+\r
+\r
+% *** PDF, URL AND HYPERLINK PACKAGES ***\r
+%\r
+%\usepackage{url}\r
+% url.sty was written by Donald Arseneau. It provides better support for\r
+% handling and breaking URLs. url.sty is already installed on most LaTeX\r
+% systems. The latest version can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/misc/\r
+% Read the url.sty source comments for usage information. Basically,\r
+% \url{my_url_here}.\r
+\r
+\r
+% NOTE: PDF thumbnail features are not required in IEEE papers\r
+% and their use requires extra complexity and work.\r
+%\ifCLASSINFOpdf\r
+% \usepackage[pdftex]{thumbpdf}\r
+%\else\r
+% \usepackage[dvips]{thumbpdf}\r
+%\fi\r
+% thumbpdf.sty and its companion Perl utility were written by Heiko Oberdiek.\r
+% It allows the user a way to produce PDF documents that contain fancy\r
+% thumbnail images of each of the pages (which tools like acrobat reader can\r
+% utilize). This is possible even when using dvi->ps->pdf workflow if the\r
+% correct thumbpdf driver options are used. thumbpdf.sty incorporates the\r
+% file containing the PDF thumbnail information (filename.tpm is used with\r
+% dvips, filename.tpt is used with pdftex, where filename is the base name of\r
+% your tex document) into the final ps or pdf output document. An external\r
+% utility, the thumbpdf *Perl script* is needed to make these .tpm or .tpt\r
+% thumbnail files from a .ps or .pdf version of the document (which obviously\r
+% does not yet contain pdf thumbnails). Thus, one does a:\r
+% \r
+% thumbpdf filename.pdf \r
+%\r
+% to make a filename.tpt, and:\r
+%\r
+% thumbpdf --mode dvips filename.ps\r
+%\r
+% to make a filename.tpm which will then be loaded into the document by\r
+% thumbpdf.sty the NEXT time the document is compiled (by pdflatex or\r
+% latex->dvips->ps2pdf). Users must be careful to regenerate the .tpt and/or\r
+% .tpm files if the main document changes and then to recompile the\r
+% document to incorporate the revised thumbnails to ensure that thumbnails\r
+% match the actual pages. It is easy to forget to do this!\r
+% \r
+% Unix systems come with a Perl interpreter. However, MS Windows users\r
+% will usually have to install a Perl interpreter so that the thumbpdf\r
+% script can be run. The Ghostscript PS/PDF interpreter is also required.\r
+% See the thumbpdf docs for details. The latest version and documentation\r
+% can be obtained at.\r
+% http://www.ctan.org/tex-archive/support/thumbpdf/\r
+% Be sure and use only version 3.8 (2005/07/06) or later of thumbpdf as\r
+% earlier versions will not work properly with recent versions of pdfTeX\r
+% (1.20a and later).\r
+\r
+\r
+% NOTE: PDF hyperlink and bookmark features are not required in IEEE\r
+% papers and their use requires extra complexity and work.\r
+% *** IF USING HYPERREF BE SURE AND CHANGE THE EXAMPLE PDF ***\r
+% *** TITLE/SUBJECT/AUTHOR/KEYWORDS INFO BELOW!! ***\r
+\newcommand\MYhyperrefoptions{bookmarks=true,bookmarksnumbered=true,\r
+pdfpagemode={UseOutlines},plainpages=false,pdfpagelabels=true,\r
+colorlinks=true,linkcolor={black},citecolor={black},pagecolor={black},\r
+urlcolor={black},\r
+pdftitle={Bare Demo of IEEEtran.cls for Computer Society Journals},%<!CHANGE!\r
+pdfsubject={Typesetting},%<!CHANGE!\r
+pdfauthor={Michael D. Shell},%<!CHANGE!\r
+pdfkeywords={Computer Society, IEEEtran, journal, LaTeX, paper,\r
+ template}}%<^!CHANGE!\r
+%\ifCLASSINFOpdf\r
+%\usepackage[\MYhyperrefoptions,pdftex]{hyperref}\r
+%\else\r
+%\usepackage[\MYhyperrefoptions,breaklinks=true,dvips]{hyperref}\r
+%\usepackage{breakurl}\r
+%\fi\r
+% One significant drawback of using hyperref under DVI output is that the\r
+% LaTeX compiler cannot break URLs across lines or pages as can be done\r
+% under pdfLaTeX's PDF output via the hyperref pdftex driver. This is\r
+% probably the single most important capability distinction between the\r
+% DVI and PDF output. Perhaps surprisingly, all the other PDF features\r
+% (PDF bookmarks, thumbnails, etc.) can be preserved in\r
+% .tex->.dvi->.ps->.pdf workflow if the respective packages/scripts are\r
+% loaded/invoked with the correct driver options (dvips, etc.). \r
+% As most IEEE papers use URLs sparingly (mainly in the references), this\r
+% may not be as big an issue as with other publications.\r
+%\r
+% That said, recently Vilar Camara Neto introduced his breakurl.sty\r
+% package which permits hyperref to easily break URLs even in dvi\r
+% mode. Note that breakurl, unlike most other packages, must be loaded\r
+% AFTER hyperref. The latest version of breakurl and its documentation can\r
+% be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/breakurl/\r
+% breakurl.sty is not for use under pdflatex pdf mode. Versions 1.10 \r
+% (September 23, 2005) and later are recommened to avoid bugs in earlier\r
+% releases.\r
+%\r
+% The advanced features offer by hyperref.sty are not required for IEEE\r
+% submission, so users should weigh these features against the added\r
+% complexity of use. Users who wish to use hyperref *must* ensure that\r
+% their hyperref version is 6.72u or later *and* IEEEtran.cls is version\r
+% 1.6b or later.\r
+% The package options above demonstrate how to enable PDF bookmarks\r
+% (a type of table of contents viewable in Acrobat Reader) as well as\r
+% PDF document information (title, subject, author and keywords) that is\r
+% viewable in Acrobat reader's Document_Properties menu. PDF document\r
+% information is also used extensively to automate the cataloging of PDF\r
+% documents. The above set of options ensures that hyperlinks will not be\r
+% colored in the text and thus will not be visible in the printed page,\r
+% but will be active on "mouse over". USING COLORS OR OTHER HIGHLIGHTING\r
+% OF HYPERLINKS CAN RESULT IN DOCUMENT REJECTION BY THE IEEE, especially if\r
+% these appear on the "printed" page. IF IN DOUBT, ASK THE RELEVANT\r
+% SUBMISSION EDITOR. You may need to add the option hypertexnames=false if\r
+% you used duplicate equation numbers, etc., but this should not be needed\r
+% in normal IEEE work.\r
+% The latest version of hyperref and its documentation can be obtained at:\r
+% http://www.ctan.org/tex-archive/macros/latex/contrib/hyperref/\r
+\r
+\r
+\r
+\r
+\r
+% *** Do not adjust lengths that control margins, column widths, etc. ***\r
+% *** Do not use packages that alter fonts (such as pslatex). ***\r
+% There should be no need to do such things with IEEEtran.cls V1.6 and later.\r
+% (Unless specifically asked to do so by the journal or conference you plan\r
+% to submit to, of course. )\r
+\r
+\r
+% correct bad hyphenation here\r
+\hyphenation{op-tical net-works semi-conduc-tor}\r
+\r
+\r
+\begin{document}\r
+%\r
+% paper title\r
+% can use linebreaks \\ within to get better formatting as desired\r
+\title{Bare Advanced Demo of IEEEtran.cls\\ for Computer Society Journals}\r
+%\r
+%\r
+% author names and IEEE memberships\r
+% note positions of commas and nonbreaking spaces ( ~ ) LaTeX will not break\r
+% a structure at a ~ so this keeps an author's name from being broken across\r
+% two lines.\r
+% use \thanks{} to gain access to the first footnote area\r
+% a separate \thanks must be used for each paragraph as LaTeX2e's \thanks\r
+% was not built to handle multiple paragraphs\r
+%\r
+%\r
+%\IEEEcompsocitemizethanks is a special \thanks that produces the bulleted\r
+% lists the Computer Society journals use for "first footnote" author\r
+% affiliations. Use \IEEEcompsocthanksitem which works much like \item\r
+% for each affiliation group. When not in compsoc mode,\r
+% \IEEEcompsocitemizethanks becomes like \thanks and\r
+% \IEEEcompsocthanksitem becomes a line break with idention. This\r
+% facilitates dual compilation, although admittedly the differences in the\r
+% desired content of \author between the different types of papers makes a\r
+% one-size-fits-all approach a daunting prospect. For instance, compsoc \r
+% journal papers have the author affiliations above the "Manuscript\r
+% received ..." text while in non-compsoc journals this is reversed. Sigh.\r
+\r
+\author{Michael~Shell,~\IEEEmembership{Member,~IEEE,}\r
+ John~Doe,~\IEEEmembership{Fellow,~OSA,}\r
+ and~Jane~Doe,~\IEEEmembership{Life~Fellow,~IEEE}% <-this % stops a space\r
+\IEEEcompsocitemizethanks{\IEEEcompsocthanksitem M. Shell is with the Department\r
+of Electrical and Computer Engineering, Georgia Institute of Technology, Atlanta,\r
+GA, 30332.\protect\\\r
+% note need leading \protect in front of \\ to get a newline within \thanks as\r
+% \\ is fragile and will error, could use \hfil\break instead.\r
+E-mail: see http://www.michaelshell.org/contact.html\r
+\IEEEcompsocthanksitem J. Doe and J. Doe are with Anonymous University.}% <-this % stops a space\r
+\thanks{Manuscript received April 19, 2005; revised January 11, 2007.}}\r
+\r
+% note the % following the last \IEEEmembership and also \thanks - \r
+% these prevent an unwanted space from occurring between the last author name\r
+% and the end of the author line. i.e., if you had this:\r
+% \r
+% \author{....lastname \thanks{...} \thanks{...} }\r
+% ^------------^------------^----Do not want these spaces!\r
+%\r
+% a space would be appended to the last name and could cause every name on that\r
+% line to be shifted left slightly. This is one of those "LaTeX things". For\r
+% instance, "\textbf{A} \textbf{B}" will typeset as "A B" not "AB". To get\r
+% "AB" then you have to do: "\textbf{A}\textbf{B}"\r
+% \thanks is no different in this regard, so shield the last } of each \thanks\r
+% that ends a line with a % and do not let a space in before the next \thanks.\r
+% Spaces after \IEEEmembership other than the last one are OK (and needed) as\r
+% you are supposed to have spaces between the names. For what it is worth,\r
+% this is a minor point as most people would not even notice if the said evil\r
+% space somehow managed to creep in.\r
+\r
+\r
+\r
+% The paper headers\r
+\markboth{Journal of \LaTeX\ Class Files,~Vol.~6, No.~1, January~2007}%\r
+{Shell \MakeLowercase{\textit{et al.}}: Bare Advanced Demo of IEEEtran.cls for Journals}\r
+% The only time the second header will appear is for the odd numbered pages\r
+% after the title page when using the twoside option.\r
+% \r
+% *** Note that you probably will NOT want to include the author's ***\r
+% *** name in the headers of peer review papers. ***\r
+% You can use \ifCLASSOPTIONpeerreview for conditional compilation here if\r
+% you desire.\r
+\r
+\r
+\r
+% The publisher's ID mark at the bottom of the page is less important with\r
+% Computer Society journal papers as those publications place the marks\r
+% outside of the main text columns and, therefore, unlike regular IEEE\r
+% journals, the available text space is not reduced by their presence.\r
+% If you want to put a publisher's ID mark on the page you can do it like\r
+% this:\r
+%\IEEEpubid{0000--0000/00\$00.00~\copyright~2007 IEEE}\r
+% or like this to get the Computer Society new two part style.\r
+%\IEEEpubid{\makebox[\columnwidth]{\hfill 0000--0000/00/\$00.00~\copyright~2007 IEEE}%\r
+%\hspace{\columnsep}\makebox[\columnwidth]{Published by the IEEE Computer Society\hfill}}\r
+% Remember, if you use this you must call \IEEEpubidadjcol in the second\r
+% column for its text to clear the IEEEpubid mark (Computer Society jorunal\r
+% papers don't need this extra clearance.)\r
+\r
+\r
+\r
+% use for special paper notices\r
+%\IEEEspecialpapernotice{(Invited Paper)}\r
+\r
+\r
+\r
+% for Computer Society papers, we must declare the abstract and index terms\r
+% PRIOR to the title within the \IEEEcompsoctitleabstractindextext IEEEtran\r
+% command as these need to go into the title area created by \maketitle.\r
+\IEEEcompsoctitleabstractindextext{%\r
+\begin{abstract}\r
+%\boldmath\r
+The abstract goes here.\r
+\end{abstract}\r
+% IEEEtran.cls defaults to using nonbold math in the Abstract.\r
+% This preserves the distinction between vectors and scalars. However,\r
+% if the journal you are submitting to favors bold math in the abstract,\r
+% then you can use LaTeX's standard command \boldmath at the very start\r
+% of the abstract to achieve this. Many IEEE journals frown on math\r
+% in the abstract anyway. In particular, the Computer Society does\r
+% not want either math or citations to appear in the abstract.\r
+\r
+% Note that keywords are not normally used for peerreview papers.\r
+\begin{IEEEkeywords}\r
+Computer Society, IEEEtran, journal, \LaTeX, paper, template.\r
+\end{IEEEkeywords}}\r
+\r
+\r
+% make the title area\r
+\maketitle\r
+\r
+\r
+% To allow for easy dual compilation without having to reenter the\r
+% abstract/keywords data, the \IEEEcompsoctitleabstractindextext text will\r
+% not be used in maketitle, but will appear (i.e., to be "transported")\r
+% here as \IEEEdisplaynotcompsoctitleabstractindextext when compsoc mode\r
+% is not selected <OR> if conference mode is selected - because compsoc\r
+% conference papers position the abstract like regular (non-compsoc)\r
+% papers do!\r
+\IEEEdisplaynotcompsoctitleabstractindextext\r
+% \IEEEdisplaynotcompsoctitleabstractindextext has no effect when using\r
+% compsoc under a non-conference mode.\r
+\r
+\r
+% For peer review papers, you can put extra information on the cover\r
+% page as needed:\r
+% \ifCLASSOPTIONpeerreview\r
+% \begin{center} \bfseries EDICS Category: 3-BBND \end{center}\r
+% \fi\r
+%\r
+% For peerreview papers, this IEEEtran command inserts a page break and\r
+% creates the second title. It will be ignored for other modes.\r
+\IEEEpeerreviewmaketitle\r
+\r
+\r
+\r
+\section{Introduction}\r
+% Computer Society journal papers do something a tad strange with the very\r
+% first section heading (almost always called "Introduction"). They place it\r
+% ABOVE the main text! IEEEtran.cls currently does not do this for you.\r
+% However, You can achieve this effect by making LaTeX jump through some\r
+% hoops via something like:\r
+%\r
+%\ifCLASSOPTIONcompsoc\r
+% \noindent\raisebox{2\baselineskip}[0pt][0pt]%\r
+% {\parbox{\columnwidth}{\section{Introduction}\label{sec:introduction}%\r
+% \global\everypar=\everypar}}%\r
+% \vspace{-1\baselineskip}\vspace{-\parskip}\par\r
+%\else\r
+% \section{Introduction}\label{sec:introduction}\par\r
+%\fi\r
+%\r
+% Admittedly, this is a hack and may well be fragile, but seems to do the\r
+% trick for me. Note the need to keep any \label that may be used right\r
+% after \section in the above as the hack puts \section within a raised box.\r
+\r
+\r
+\r
+% The very first letter is a 2 line initial drop letter followed\r
+% by the rest of the first word in caps (small caps for compsoc).\r
+% \r
+% form to use if the first word consists of a single letter:\r
+% \IEEEPARstart{A}{demo} file is ....\r
+% \r
+% form to use if you need the single drop letter followed by\r
+% normal text (unknown if ever used by IEEE):\r
+% \IEEEPARstart{A}{}demo file is ....\r
+% \r
+% Some journals put the first two words in caps:\r
+% \IEEEPARstart{T}{his demo} file is ....\r
+% \r
+% Here we have the typical use of a "T" for an initial drop letter\r
+% and "HIS" in caps to complete the first word.\r
+\IEEEPARstart{T}{his} demo file is intended to serve as a ``starter file''\r
+for IEEE Computer Society journal papers produced under \LaTeX\ using\r
+IEEEtran.cls version 1.7 and later.\r
+% You must have at least 2 lines in the paragraph with the drop letter\r
+% (should never be an issue)\r
+I wish you the best of success.\r
+\r
+\hfill mds\r
+ \r
+\hfill January 11, 2007\r
+\r
+\subsection{Subsection Heading Here}\r
+Subsection text here.\r
+\r
+% needed in second column of first page if using \IEEEpubid\r
+%\IEEEpubidadjcol\r
+\r
+\subsubsection{Subsubsection Heading Here}\r
+Subsubsection text here.\r
+\r
+\r
+% An example of a floating figure using the graphicx package.\r
+% Note that \label must occur AFTER (or within) \caption.\r
+% For figures, \caption should occur after the \includegraphics.\r
+% Note that IEEEtran v1.7 and later has special internal code that\r
+% is designed to preserve the operation of \label within \caption\r
+% even when the captionsoff option is in effect. However, because\r
+% of issues like this, it may be the safest practice to put all your\r
+% \label just after \caption rather than within \caption{}.\r
+%\r
+% Reminder: the "draftcls" or "draftclsnofoot", not "draft", class\r
+% option should be used if it is desired that the figures are to be\r
+% displayed while in draft mode.\r
+%\r
+%\begin{figure}[!t]\r
+%\centering\r
+%\includegraphics[width=2.5in]{myfigure}\r
+% where an .eps filename suffix will be assumed under latex, \r
+% and a .pdf suffix will be assumed for pdflatex; or what has been declared\r
+% via \DeclareGraphicsExtensions.\r
+%\caption{Simulation Results}\r
+%\label{fig_sim}\r
+%\end{figure}\r
+\r
+% Note that IEEE typically puts floats only at the top, even when this\r
+% results in a large percentage of a column being occupied by floats.\r
+% However, the Computer Society has been known to put floats at the bottom.\r
+\r
+\r
+% An example of a double column floating figure using two subfigures.\r
+% (The subfig.sty package must be loaded for this to work.)\r
+% The subfigure \label commands are set within each subfloat command, the\r
+% \label for the overall figure must come after \caption.\r
+% \hfil must be used as a separator to get equal spacing.\r
+% The subfigure.sty package works much the same way, except \subfigure is\r
+% used instead of \subfloat.\r
+%\r
+%\begin{figure*}[!t]\r
+%\centerline{\subfloat[Case I]\includegraphics[width=2.5in]{subfigcase1}%\r
+%\label{fig_first_case}}\r
+%\hfil\r
+%\subfloat[Case II]{\includegraphics[width=2.5in]{subfigcase2}%\r
+%\label{fig_second_case}}}\r
+%\caption{Simulation results}\r
+%\label{fig_sim}\r
+%\end{figure*}\r
+%\r
+% Note that often IEEE papers with subfigures do not employ subfigure\r
+% captions (using the optional argument to \subfloat), but instead will\r
+% reference/describe all of them (a), (b), etc., within the main caption.\r
+\r
+\r
+% An example of a floating table. Note that, for IEEE style tables, the \r
+% \caption command should come BEFORE the table. Table text will default to\r
+% \footnotesize as IEEE normally uses this smaller font for tables.\r
+% The \label must come after \caption as always.\r
+%\r
+%\begin{table}[!t]\r
+%% increase table row spacing, adjust to taste\r
+%\renewcommand{\arraystretch}{1.3}\r
+% if using array.sty, it might be a good idea to tweak the value of\r
+% \extrarowheight as needed to properly center the text within the cells\r
+%\caption{An Example of a Table}\r
+%\label{table_example}\r
+%\centering\r
+%% Some packages, such as MDW tools, offer better commands for making tables\r
+%% than the plain LaTeX2e tabular which is used here.\r
+%\begin{tabular}{|c||c|}\r
+%\hline\r
+%One & Two\\\r
+%\hline\r
+%Three & Four\\\r
+%\hline\r
+%\end{tabular}\r
+%\end{table}\r
+\r
+\r
+% Note that IEEE does not put floats in the very first column - or typically\r
+% anywhere on the first page for that matter. Also, in-text middle ("here")\r
+% positioning is not used. Most IEEE journals use top floats exclusively.\r
+% However, Computer Society journals sometimes do use bottom floats - bear\r
+% this in mind when choosing appropriate optional arguments for the\r
+% figure/table environments.\r
+% Note that, LaTeX2e, unlike IEEE journals, places footnotes above bottom\r
+% floats. This can be corrected via the \fnbelowfloat command of the\r
+% stfloats package.\r
+\r
+\r
+\r
+\section{Conclusion}\r
+The conclusion goes here.\r
+\r
+\r
+\r
+\r
+\r
+% if have a single appendix:\r
+%\appendix[Proof of the Zonklar Equations]\r
+% or\r
+%\appendix % for no appendix heading\r
+% do not use \section anymore after \appendix, only \section*\r
+% is possibly needed\r
+\r
+% use appendices with more than one appendix\r
+% then use \section to start each appendix\r
+% you must declare a \section before using any\r
+% \subsection or using \label (\appendices by itself\r
+% starts a section numbered zero.)\r
+%\r
+\r
+\r
+\appendices\r
+\section{Proof of the First Zonklar Equation}\r
+Appendix one text goes here.\r
+\r
+% you can choose not to have a title for an appendix\r
+% if you want by leaving the argument blank\r
+\section{}\r
+Appendix two text goes here.\r
+\r
+\r
+% use section* for acknowledgement\r
+\ifCLASSOPTIONcompsoc\r
+ % The Computer Society usually uses the plural form\r
+ \section*{Acknowledgments}\r
+\else\r
+ % regular IEEE prefers the singular form\r
+ \section*{Acknowledgment}\r
+\fi\r
+\r
+\r
+The authors would like to thank...\r
+\r
+\r
+% Can use something like this to put references on a page\r
+% by themselves when using endfloat and the captionsoff option.\r
+\ifCLASSOPTIONcaptionsoff\r
+ \newpage\r
+\fi\r
+\r
+\r
+\r
+% trigger a \newpage just before the given reference\r
+% number - used to balance the columns on the last page\r
+% adjust value as needed - may need to be readjusted if\r
+% the document is modified later\r
+%\IEEEtriggeratref{8}\r
+% The "triggered" command can be changed if desired:\r
+%\IEEEtriggercmd{\enlargethispage{-5in}}\r
+\r
+% references section\r
+\r
+% can use a bibliography generated by BibTeX as a .bbl file\r
+% BibTeX documentation can be easily obtained at:\r
+% http://www.ctan.org/tex-archive/biblio/bibtex/contrib/doc/\r
+% The IEEEtran BibTeX style support page is at:\r
+% http://www.michaelshell.org/tex/ieeetran/bibtex/\r
+%\bibliographystyle{IEEEtran}\r
+% argument is your BibTeX string definitions and bibliography database(s)\r
+%\bibliography{IEEEabrv,../bib/paper}\r
+%\r
+% <OR> manually copy in the resultant .bbl file\r
+% set second argument of \begin to the number of references\r
+% (used to reserve space for the reference number labels box)\r
+\begin{thebibliography}{1}\r
+\r
+\bibitem{IEEEhowto:kopka}\r
+H.~Kopka and P.~W. Daly, \emph{A Guide to {\LaTeX}}, 3rd~ed.\hskip 1em plus\r
+ 0.5em minus 0.4em\relax Harlow, England: Addison-Wesley, 1999.\r
+\r
+\end{thebibliography}\r
+\r
+% biography section\r
+% \r
+% If you have an EPS/PDF photo (graphicx package needed) extra braces are\r
+% needed around the contents of the optional argument to biography to prevent\r
+% the LaTeX parser from getting confused when it sees the complicated\r
+% \includegraphics command within an optional argument. (You could create\r
+% your own custom macro containing the \includegraphics command to make things\r
+% simpler here.)\r
+%\begin{biography}[{\includegraphics[width=1in,height=1.25in,clip,keepaspectratio]{mshell}}]{Michael Shell}\r
+% or if you just want to reserve a space for a photo:\r
+\r
+\begin{IEEEbiography}{Michael Shell}\r
+Biography text here.\r
+\end{IEEEbiography}\r
+\r
+% if you will not have a photo at all:\r
+\begin{IEEEbiographynophoto}{John Doe}\r
+Biography text here.\r
+\end{IEEEbiographynophoto}\r
+\r
+% insert where needed to balance the two columns on the last page with\r
+% biographies\r
+%\newpage\r
+\r
+\begin{IEEEbiographynophoto}{Jane Doe}\r
+Biography text here.\r
+\end{IEEEbiographynophoto}\r
+\r
+% You can push biographies down or up by placing\r
+% a \vfill before or after them. The appropriate\r
+% use of \vfill depends on what kind of text is\r
+% on the last page and whether or not the columns\r
+% are being equalized.\r
+\r
+%\vfill\r
+\r
+% Can be used to pull up biographies so that the bottom of the last one\r
+% is flush with the other column.\r
+%\enlargethispage{-5in}\r
+\r
+\r
+\r
+% that's all folks\r
+\end{document}\r
+\r
+\r
