
nickjillings@1642: % -----------------------------------------------
nickjillings@1642: % Template for SMC 2012
nickjillings@1642: % adapted from the template for SMC 2011, which was adapted from that of SMC 2010
nickjillings@1642: % -----------------------------------------------
nickjillings@1642: 
nickjillings@1642: \documentclass{article}
nickjillings@1642: \usepackage{smc2015}
nickjillings@1642: \usepackage{times}
nickjillings@1642: \usepackage{ifpdf}
nickjillings@1642: \usepackage[english]{babel}
nickjillings@1642: \usepackage{cite}
nickjillings@1642: 
b@1672: \hyphenation{Java-script}
b@1672: 
nickjillings@1642: %%%%%%%%%%%%%%%%%%%%%%%% Some useful packages %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
nickjillings@1642: %%%%%%%%%%%%%%%%%%%%%%%% See related documentation %%%%%%%%%%%%%%%%%%%%%%%%%%
nickjillings@1642: %\usepackage{amsmath} % popular packages from Am. Math. Soc. Please use the 
nickjillings@1642: %\usepackage{amssymb} % related math environments (split, subequation, cases,
nickjillings@1642: %\usepackage{amsfonts}% multline, etc.)
nickjillings@1642: %\usepackage{bm}      % Bold Math package, defines the command \bf{}
nickjillings@1642: %\usepackage{paralist}% extended list environments
nickjillings@1642: %%subfig.sty is the modern replacement for subfigure.sty. However, subfig.sty 
nickjillings@1642: %%requires and automatically loads caption.sty which overrides class handling 
nickjillings@1642: %%of captions. To prevent this problem, preload caption.sty with caption=false 
nickjillings@1642: %\usepackage[caption=false]{caption}
nickjillings@1642: %\usepackage[font=footnotesize]{subfig}
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: %user defined variables
b@1669: \def\papertitle{WEB AUDIO EVALUATION TOOL: A BROWSER-BASED LISTENING TEST ENVIRONMENT} %?
nickjillings@1642: \def\firstauthor{Nicholas Jillings}
nickjillings@1642: \def\secondauthor{Brecht De Man}
nickjillings@1642: \def\thirdauthor{David Moffat}
nickjillings@1642: \def\fourthauthor{Joshua D. Reiss}
nickjillings@1642: 
nickjillings@1642: % adds the automatic
nickjillings@1642: % Saves a lot of ouptut space in PDF... after conversion with the distiller
nickjillings@1642: % Delete if you cannot get PS fonts working on your system.
nickjillings@1642: 
nickjillings@1642: % pdf-tex settings: detect automatically if run by latex or pdflatex
nickjillings@1642: \newif\ifpdf
nickjillings@1642: \ifx\pdfoutput\relax
nickjillings@1642: \else
nickjillings@1642:    \ifcase\pdfoutput
nickjillings@1642:       \pdffalse
nickjillings@1642:    \else
nickjillings@1642:       \pdftrue
nickjillings@1642: \fi
nickjillings@1642: 
nickjillings@1642: \ifpdf % compiling with pdflatex
nickjillings@1642:   \usepackage[pdftex,
nickjillings@1642:     pdftitle={\papertitle},
nickjillings@1642:     pdfauthor={\firstauthor, \secondauthor, \thirdauthor},
nickjillings@1642:     bookmarksnumbered, % use section numbers with bookmarks
nickjillings@1642:     pdfstartview=XYZ % start with zoom=100% instead of full screen; 
nickjillings@1642:                      % especially useful if working with a big screen :-)
nickjillings@1642:    ]{hyperref}
nickjillings@1642:   %\pdfcompresslevel=9
nickjillings@1642: 
nickjillings@1642:   \usepackage[pdftex]{graphicx}
nickjillings@1642:   % declare the path(s) where your graphic files are and their extensions so 
nickjillings@1642:   %you won't have to specify these with every instance of \includegraphics
nickjillings@1642:   \graphicspath{{./figures/}}
nickjillings@1642:   \DeclareGraphicsExtensions{.pdf,.jpeg,.png}
nickjillings@1642: 
nickjillings@1642:   \usepackage[figure,table]{hypcap}
nickjillings@1642: 
nickjillings@1642: \else % compiling with latex
nickjillings@1642:   \usepackage[dvips,
nickjillings@1642:     bookmarksnumbered, % use section numbers with bookmarks
nickjillings@1642:     pdfstartview=XYZ % start with zoom=100% instead of full screen
nickjillings@1642:   ]{hyperref}  % hyperrefs are active in the pdf file after conversion
nickjillings@1642: 
nickjillings@1642:   \usepackage[dvips]{epsfig,graphicx}
nickjillings@1642:   % declare the path(s) where your graphic files are and their extensions so 
nickjillings@1642:   %you won't have to specify these with every instance of \includegraphics
nickjillings@1642:   \graphicspath{{./figures/}}
nickjillings@1642:   \DeclareGraphicsExtensions{.eps}
nickjillings@1642: 
nickjillings@1642:   \usepackage[figure,table]{hypcap}
nickjillings@1642: \fi
nickjillings@1642: 
nickjillings@1642: %setup the hyperref package - make the links black without a surrounding frame
nickjillings@1642: \hypersetup{
nickjillings@1642:     colorlinks,%
nickjillings@1642:     citecolor=black,%
nickjillings@1642:     filecolor=black,%
nickjillings@1642:     linkcolor=black,%
nickjillings@1642:     urlcolor=black
nickjillings@1642: }
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: % Title.
nickjillings@1642: % ------
nickjillings@1642: \title{\papertitle}
nickjillings@1642: 
nickjillings@1642: % Authors
nickjillings@1642: % Please note that submissions are NOT anonymous, therefore 
nickjillings@1642: % authors' names have to be VISIBLE in your manuscript. 
nickjillings@1642: %
nickjillings@1642: % Single address
nickjillings@1642: % To use with only one author or several with the same address
nickjillings@1642: % ---------------
nickjillings@1642: %\oneauthor
nickjillings@1642: %   {\firstauthor} {Affiliation1 \\ %
nickjillings@1642: %     {\tt \href{mailto:author1@smcnetwork.org}{author1@smcnetwork.org}}}
nickjillings@1642: 
nickjillings@1642: %Two addresses
nickjillings@1642: %--------------
nickjillings@1642: % \twoauthors
nickjillings@1642: %   {\firstauthor} {Affiliation1 \\ %
nickjillings@1642: %     {\tt \href{mailto:author1@smcnetwork.org}{author1@smcnetwork.org}}}
nickjillings@1642: %   {\secondauthor} {Affiliation2 \\ %
nickjillings@1642: %     {\tt \href{mailto:author2@smcnetwork.org}{author2@smcnetwork.org}}}
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: % FIX!!! 
nickjillings@1642:  \fourauthors
nickjillings@1642:    {\firstauthor} {%Affiliation1 \\
nickjillings@1642:      {\tt \href{mailto:b.deman@qmul.ac.uk}{n.g.r.jillings@se14.qmul.ac.uk, }}}
nickjillings@1642:    {\secondauthor} {%Affiliation2\\ %
nickjillings@1642:      {\tt \href{mailto:n.g.r.jillings@se14.qmul.ac.uk}{\{b.deman,}}}
nickjillings@1642:    {\thirdauthor} {%Affiliation3\\ %
nickjillings@1642:      {\tt \href{mailto:d.j.moffat@qmul.ac.uk}{d.j.moffat, }}}
nickjillings@1642:     {\fourthauthor} {%Affiliation4\\ %
nickjillings@1642:      {\tt \href{mailto:joshua.reiss@qmul.ac.uk}{joshua.reiss\}@qmul.ac.uk}}}
nickjillings@1642: 
nickjillings@1642: % ***************************************** the document starts here ***************
nickjillings@1642: \begin{document}
nickjillings@1642: %
nickjillings@1642: \capstartfalse
nickjillings@1642: \maketitle
nickjillings@1642: \capstarttrue
nickjillings@1642: %
nickjillings@1642: \begin{abstract}
b@1669: New functionality in HTML5, notably its Web Audio API, allow for increasingly powerful applications in the browser. % is this true?
b@1669: Perceptual evaluation tests for audio, where the subject assesses certain qualities of different audio fragments through a graphical user interface and/or text boxes, require playback of audio and rapid switching between different files. % what else? 
b@1669: The advantage of a web application is easy deployment on any platform, without requiring any other application or library, easy storing of results on a server. 
b@1669: [...]
b@1669: %Place your abstract at the top left column on the first page.
b@1669: %Please write about 150-200 words that specifically highlight the purpose of your work,
b@1669: %its context, and provide a brief synopsis of your results.
b@1669: %Avoid equations in this part.\\
b@1669: 
nickjillings@1642: \end{abstract}
nickjillings@1642: %
nickjillings@1642: 
nickjillings@1642: \section{Introduction}\label{sec:introduction}
b@1671: 
b@1669: TOTAL PAPER: Minimum 4 pages, 6 preferred, max. 8 (6 for demos/posters)\\ 
b@1669: 
b@1669: NICK: examples of what kind of audio applications HTML5 has made possible, with references to publications (or website)\\
nickjillings@1642: 
nickjillings@1642: background (types of research where this type of perceptual evaluation of audio is relevant)\\
nickjillings@1642: 
b@1669: multiple stimulus perceptual evaluation \cite{bech}\\
nickjillings@1642: 
nickjillings@1642: prior work: \cite{deman2014b} in MATLAB, much less easy to deploy, and often stops working due to version updates \\ 
nickjillings@1642: 
nickjillings@1642: goal, what are we trying to do? \\
nickjillings@1642: 
b@1669: other background papers (some SMC?)\\
b@1669: 
nickjillings@1642: [Previously, due to limited functionality of HTML, ..., it was not possible to design this type of interfaces with such high quality audio... ]
nickjillings@1642: 
nickjillings@1642: 
b@1670: %\section{Design considerations}\label{sec:designconsiderations} % not necessary? with next (/previous) section?
nickjillings@1642: 
nickjillings@1642: We present a browser-based perceptual evaluation tool for audio that ... \\
nickjillings@1642: 
nickjillings@1642: see \cite{deman2014b}: requirements informed by research on music production (see my work and that of others' in the group), such as randomisation, playback of high quality audio, some degree of flexibility in terms of configuration, ... \\
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: \section{Implementation}\label{sec:implementation}
nickjillings@1642: %[Nick???]
nickjillings@1642: 
nickjillings@1642: %section on overall architecture\\
nickjillings@1642: 
nickjillings@1642: %section with overview of the structure of the input and output files, perhaps with graph or table
nickjillings@1642: 
b@1670: The tool runs entirely inside the browser through the new HTML5 Web Audio API. The API is supported by most major web browsers (with the exception of Internet Explorer) and allows for constructing a chain of audio processing elements to produce a high quality, real time signal process to manipulate audio streams. The API supports multi-channel processing and has an accurate playback timer for precise scheduled playback control. The Web Audio API is controlled through the browser JavaScript and is therefore highly controllable. The Web Audio API processing is all controlled in a separate thread to the main JavaScript thread, meaning there is no blocking due to real time processing. 
b@1669: 
b@1669: \subsection{Interface}\label{sec:interface} %elsewhere?
b@1669: 
b@1670: At this point, we have implemented the interface of the MATLAB-based APE Perceptual Evaluation for Audio toolbox \cite{deman2014b}, which shows one marker for each simultaneously evaluated audio fragment on one or more horizontal axes (to rate/rank the respective fragments), as well as a comment box for every marker, and one extra text box for extra comments. See \ref{fig:interface} for an example of the interface, with 10 fragments and one axis. However, the back end of this test environment allows for many more established and novel interfaces for listening tests, particularly ones where the subject only assesses audio without manipulating it (i.e. method of adjustment, which would require additional features to be implemented). 
b@1669: 
b@1669: \begin{figure*}[htbp]
b@1669: \begin{center}
b@1670: \includegraphics[width=0.9\textwidth]{interface.png}
b@1669: \caption{Example of interface, with 1 axis and 10 fragments}
b@1669: \label{fig:interface}
b@1669: \end{center}
b@1669: \end{figure*}
b@1669: 
b@1669: 
nickjillings@1642: 
nickjillings@1642: \subsection{Architecture}\label{sec:architecture}
nickjillings@1642: 
nickjillings@1642: The web tool itself is split into several files to operate:
nickjillings@1642: \begin{itemize}
b@1670: \item \texttt{apeTool.html}: The main index file to load the scripts, this is the file the browser must request to load. 
b@1670: \item \texttt{core.js}: Contains functions and objects to manage the audio control, audio objects for testing and loading of files. 
b@1669: \item \texttt{ape.js}: Parses setup files to create the interface as instructed, following the same style chain as the MATLAB APE Tool \cite{deman2014b}.
nickjillings@1642: \end{itemize}
nickjillings@1642: 
b@1670: The HTML file loads the \texttt{core.js} file with it along with a few other ancillary files (such as the jQuery JavaScript extensions), at which point the browser JavaScript begins to execute the on-page instructions, which gives the URL of the test setup XML document (outlined in the next section). \texttt{core.js} parses this document and executes the function in \texttt{ape.js} to build the web page with the given audio files. The reason for separating these two files is to allow for further interface designs (such as MUSHRA \cite{mushra} or A-B tests \cite{bech}) to be used, which would still require the same underlying core functions outlined in \texttt{core.js}, see also Section \ref{sec:interface}.
nickjillings@1642: 
b@1670: The \texttt{ape.js} file has only two main functions: \textit{loadInterface(xmlDoc)} and \textit{interfaceXMLSave()}. The first function is called to build the interface once the setup document has been loaded. This includes creating the slider interface to rate the tracks, and creating the comment boxes below it. The markers on the slider at the top of the page are positioned randomly, to minimise the bias that may be introduced when the initial positions are near the beginning, end or middle of the slider. While another approach is to place the markers outside of the slider bar at first and have the subject drag them in, the authors believe this doesn't encourage careful consideration and comparison of the different fragments as the implicit goal of the test becomes to audition and drag each fragment in just once, rather than to compare all fragments rigorously. 
b@1670: \texttt{ape.js} also instructs the audio engine in \texttt{core.js} to create the audio objects. The audio objects are custom built audio nodes built on the Web Audio API. % 'built' twice?
b@1670: They consist of a \textit{bufferSourceNode} (a node which holds a buffer of audio samples for playback) and a \textit{gainNode}. These are then connected to the \textit{audioEngine} (itself a custom web audio node) containing a \textit{gainNode} (where the various Audio Objects connect to) for summation before passing the output to the \textit{destinationNode}, a fixed node created where %through which?
b@1670: the browser then passes the audio information to the system sound device. 
b@1670: % audio object/audioObject/Audio Object: consistency?
nickjillings@1642: 
b@1670: When an \textit{audioObject} is created, it is given the URL of the audio sample to load. This is downloaded into the browser asynchronously using the \textit{XMLHttpRequest} object. This allows for downloading of any file into the JavaScript environment for further processing. It is particularly useful for the Web Audio API because it supports downloading of files in their binary form, allowing a perfect copy. % don't quite understand this
b@1670: Once the asynchronous download is complete, the file is then decoded using the Web Audio API offline decoder. This uses the browser's %browser's? browser-available? available in the browser?
b@1670:  available decoding schemes to decode the audio files into raw float32 arrays, which are in turn passed to the relevant audioObject \textit{bufferSourceNode} for playback.
nickjillings@1642: 
b@1670: % GENERAL QUESTION: would it be hard to support more file types? If so, I think it's much nicer to say 'at the moment we allow ... and ... and ... files'
b@1670: Browsers support various audio file formats and are not consistent in any format. % 'not consistent in any format'? What do you mean exactly?
b@1670: However, all browsers support the WAV format. Although not a compact, web friendly format, most transport systems are of a high enough bandwidth this should not be a problem. 
b@1670: However, one problem is that the browser uses the sample rate assigned by the system sound device, % is this problem particular to WAV? Seems that way from the text
b@1670: and does not have the ability to request a different one. Therefore, the default operation when an audio file is loaded with a different sample rate to that of the system is to convert the sample rate. To provide a check for this, the desired sample rate can be supplied with the setup XML and checked against. If the sample rates do not match, a browser alert window is shown asking for the sample rate to be correctly adjusted. 
b@1670: As this happens before any loading or decoding of audio files, the system will only fetch files as soon as the system's sample rate meets any requirements, avoiding requests for large files until they are actually needed. 
nickjillings@1642: 
b@1669: During playback, the playback nodes loop indefinitely until playback is stopped. The gain nodes in the \textit{audioObject}s enable dynamic muting of nodes. When a bar in the sliding ranking is clicked, the audio engine mutes all \textit{audioObject}s and un-mutes the clicked one. Therefore, if the audio samples are perfectly aligned up and of the same sample length, they will remain perfectly aligned with each other.
b@1669: 
nickjillings@1642: 
b@1670: \subsection{Setup and results formats}\label{sec:setupresultsformats}
nickjillings@1642: 
b@1672: Setup and the results both use the common XML document format to outline the various parameters. The setup file contains all the information needed to initialise a test session. Several nodes can be defined to outline the audio samples to use, questions to be asked and any pre- or post-test questions or instructions. Having one document to modify allows for quick manipulation in a `human readable' form to create new tests, or adjust current ones, without needing to edit which web files. % 'which web files'?
nickjillings@1642: 
b@1672: The results file is dynamically generated by the interface upon clicking the `Submit' button. This also executes checks, depending on the setup file, to ensure that all tracks have been played back, rated and commented on. The XML output returned contains a node per audioObject and contains both the corresponding marker's position and any comments written in the associated comment box. The rating returned is normalised to be a value between 0 and 1, normalising the pixel representation of different browser windows. 
b@1669: 
b@1670: Pre- and post-test dialog boxes allow for comments or questions to be presented before or after the test, to convey listening test instructions, and gather information about the subject, listening environment, and overall experience of the test. These are automatically generated from the setup XML and allow nearly any form of question and comment to be included in a window on its own. Questions are stored and presented in the response section labelled `pretest' and `posttest', along with the question ID and its response, and can be made mandatory. 
b@1670: Further options in the setup file are: 
b@1670: 
b@1670: \begin{itemize}
b@1670: \item \textbf{Snap to corresponding position}: When this is enabled, and a fragment is playing, the playhead skips to the same position in the next fragment that is clicked. If it is not enabled, every fragment is played from the start. 
b@1670: \item \textbf{Loop fragments}: Repeat current fragment when end is reached, until the `Stop audio' or `Submit' button is clicked. 
b@1670: \item \textbf{Comments}: Displays a separate comment box for each fragment in the page.
b@1670: \item \textbf{General comment}: One comment box, additional to the individual comment boxes, to comment on the test or a feature that some or all of the fragments share. 
b@1670: \item \textbf{Resampling}: When this is enabled, tracks are resampled to match the subject's system's sample rate (a default feature of the Web Audio API). When it is not, an error is shown when the system does not match the requested sample rate. 
b@1670: \item \textbf{Randomise page order}: Randomises the order in which different `pages' are presented. % are we calling this 'pages'?
b@1670: \item \textbf{Randomise fragment order}: Randomises the order and numbering of the markers and comment boxes corresponding with the fragments. This permutation is stored as well, to be able to interpret references to the numbers in the comments (such as `this is much [brighter] then 4'). 
b@1670: \item \textbf{Require playback}: Require that each fragment has been played at least once, if not in full. 
b@1670: \item \textbf{Require full playback}: If `Require playback' is active, require that each fragment has been played in full. 
b@1670: \item \textbf{Require moving}: Require that each marker is moved (dragged) at least once. 
b@1670: \item \textbf{Require comments}: This option allows requiring the subject to require a comment for each track. 
b@1672: \item \textbf{Repeat test}: Number of times test should be repeated (none by default), to allow familiarisation with the content and experiment, and to investigate consistency of user and variability due to familiarity.
b@1670: % explanation on how this is implemented? 
b@1670: \end{itemize}
b@1670: 
b@1670: When one of these options is not included in the setup file, they assume a default value. 
b@1670: 
b@1669: % loop, snap to corresponding position, comments, 'general' comment, require same sampling rate, different types of randomisation
b@1669: 
b@1670: 
nickjillings@1642: 
nickjillings@1642: The results will also contain information collected by any defined pre/post questions. These are referenced against the setup XML by using the same ID as well as printing in the same question, so readable responses can be obtained. Future development will also evolve to include any session data, such as the browser the tool was used in, how long the test took and any other metrics. Currently the results files are downloaded on the user side of the browser as a .xml file to be manually returned. However the end goal is to allow the XML files to be submitted over the web to a receiving server to store them, allowing for automated collection.
nickjillings@1642: 
b@1672: Furthermore, each user action (manipulation of any interface element, such as playback or moving a marker) is logged along with a the corresponding time code and stored or sent along with the results. % right? 
b@1670: 
b@1670: %Here is an example of the setup XML and the results XML: % perhaps best to refer to each XML after each section (setup <> results)
b@1669: % Should we include an Example of the input and output XML structure?? --> Sure. 
b@1669: 
b@1669: ADD XML STRUCTURE EXAMPLE
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: \section{Conclusions and future work}\label{sec:conclusions}
nickjillings@1642: 
nickjillings@1642: In this paper we have presented an approach to creating a browser-based listening test environment that can be used for a variety of types of perceptual evaluation of audio. 
nickjillings@1642: Specifically, we discussed the use of the toolbox in the context of assessment of preference for different production practices, with identical source material. 
nickjillings@1642: The purpose of this paper is to outline the design of this tool, to describe our implementation using basic HTML5 functionality, and to discuss design challenges and limitations of our approach. % or something
nickjillings@1642: 
nickjillings@1642: % future work
b@1669: Further work may include the development of other common test designs, such as MUSHRA \cite{mushra}, AB, ABX and method of adjustment tests. 
b@1669: In addition, [...]. 
nickjillings@1642: 
b@1669: %\begin{itemize}
b@1669: %\item Options for MUSHRA style experiment with vertical slide per track
b@1669: %\item APE style experiment where all tracks are on a single horizontal axis % isn't that what we're doing now? 
b@1669: %\item AB test
b@1669: %\item ABX test
b@1669: %\item Method of adjustment tests
b@1669: %\end{itemize}
nickjillings@1642: 
nickjillings@1642: 
b@1672: The source code of this tool can be found on \url{code.soundsoftware.ac.uk/projects/webaudioevaluationtool}. The repository includes an issue tracker, where bug reports and feature requests can inform further development. 
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
nickjillings@1642: %bibliography here
nickjillings@1642: \bibliography{smc2015template}
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: \end{document}
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: % RUBBISH
nickjillings@1642: 
nickjillings@1642: %\subsection{Equations}
nickjillings@1642: %Equations of importance, 
nickjillings@1642: %or to which you refer later,
nickjillings@1642: %should be placed on separated lines and numbered.
nickjillings@1642: %The number should be on the right side, in parentheses.
nickjillings@1642: %\begin{equation}
nickjillings@1642: %E=mc^{2+\delta}.
nickjillings@1642: %\label{eq:Emc2}
nickjillings@1642: %\end{equation}
nickjillings@1642: %Refer to equations like so:
nickjillings@1642: %As (\ref{eq:Emc2}) shows, 
nickjillings@1642: %I do not completely trust Special Relativity.
nickjillings@1642: %
nickjillings@1642: %\subsection{Figures, Tables and Captions}
nickjillings@1642: %\begin{table}[t]
nickjillings@1642: % \begin{center}
nickjillings@1642: % \begin{tabular}{|l|l|}
nickjillings@1642: %  \hline
nickjillings@1642: %  String value & Numeric value \\
nickjillings@1642: %  \hline
nickjillings@1642: %  Hej SMC  & 2015 \\
nickjillings@1642: %  \hline
nickjillings@1642: % \end{tabular}
nickjillings@1642: %\end{center}
nickjillings@1642: % \caption{Table captions should be placed below the table, exactly like this,
nickjillings@1642: % but using words different from these.}
nickjillings@1642: % \label{tab:example}
nickjillings@1642: %\end{table}
nickjillings@1642: 
nickjillings@1642: %\begin{figure}[t]
nickjillings@1642: %\figbox{
nickjillings@1642: %\subfloat[][]{\includegraphics[width=60mm]{figure}\label{fig:subfigex_a}}\\
nickjillings@1642: %\subfloat[][]{\includegraphics[width=80mm]{figure}\label{fig:subfigex_b}}
nickjillings@1642: %}
nickjillings@1642: %\caption{Here's an example using the subfig package.\label{fig:subfigex} }
nickjillings@1642: %\end{figure}
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: 
nickjillings@1642: %\begin{acknowledgments}
nickjillings@1642: %You may acknowledge people, projects, 
nickjillings@1642: %funding agencies, etc. 
nickjillings@1642: %which can be included after the second-level heading
nickjillings@1642: %``Acknowledgments'' (with no numbering).
nickjillings@1642: %\end{acknowledgments} 
nickjillings@1642: 




