annotate docs/WAC2016/WAC2016.tex @ 726:949185ac04a9

Paper: bits of introduction and remote testing, minor edits
author Brecht De Man <BrechtDeMan@users.noreply.github.com>
date Tue, 29 Sep 2015 23:55:10 +0200
parents 16bafae452a8
children 3b637867eafe
rev   line source
BrechtDeMan@719 1 \documentclass{sig-alternate}
BrechtDeMan@726 2 \usepackage{hyperref}
BrechtDeMan@719 3
BrechtDeMan@719 4 \begin{document}
BrechtDeMan@719 5
BrechtDeMan@719 6 % Copyright
BrechtDeMan@719 7 \setcopyright{waclicense}
BrechtDeMan@719 8
BrechtDeMan@719 9
BrechtDeMan@719 10 %% DOI
BrechtDeMan@719 11 %\doi{10.475/123_4}
BrechtDeMan@719 12 %
BrechtDeMan@719 13 %% ISBN
BrechtDeMan@719 14 %\isbn{123-4567-24-567/08/06}
BrechtDeMan@719 15 %
BrechtDeMan@719 16 %%Conference
BrechtDeMan@719 17 %\conferenceinfo{PLDI '13}{June 16--19, 2013, Seattle, WA, USA}
BrechtDeMan@719 18 %
BrechtDeMan@719 19 %\acmPrice{\$15.00}
BrechtDeMan@719 20
BrechtDeMan@719 21 %
BrechtDeMan@719 22 % --- Author Metadata here ---
BrechtDeMan@719 23 \conferenceinfo{Web Audio Conference WAC-2016,}{April 4--6, 2016, Atlanta, USA}
BrechtDeMan@719 24 \CopyrightYear{2016} % Allows default copyright year (20XX) to be over-ridden - IF NEED BE.
BrechtDeMan@719 25 %\crdata{0-12345-67-8/90/01} % Allows default copyright data (0-89791-88-6/97/05) to be over-ridden - IF NEED BE.
BrechtDeMan@719 26 % --- End of Author Metadata ---
BrechtDeMan@719 27
BrechtDeMan@722 28 \title{Web Audio Evaluation Tool something something}
BrechtDeMan@719 29 %\subtitle{[Extended Abstract]
BrechtDeMan@719 30 %\titlenote{A full version of this paper is available as
BrechtDeMan@719 31 %\textit{Author's Guide to Preparing ACM SIG Proceedings Using
BrechtDeMan@719 32 %\LaTeX$2_\epsilon$\ and BibTeX} at
BrechtDeMan@719 33 %\texttt{www.acm.org/eaddress.htm}}}
BrechtDeMan@719 34 %
BrechtDeMan@719 35 % You need the command \numberofauthors to handle the 'placement
BrechtDeMan@719 36 % and alignment' of the authors beneath the title.
BrechtDeMan@719 37 %
BrechtDeMan@719 38 % For aesthetic reasons, we recommend 'three authors at a time'
BrechtDeMan@719 39 % i.e. three 'name/affiliation blocks' be placed beneath the title.
BrechtDeMan@719 40 %
BrechtDeMan@719 41 % NOTE: You are NOT restricted in how many 'rows' of
BrechtDeMan@719 42 % "name/affiliations" may appear. We just ask that you restrict
BrechtDeMan@719 43 % the number of 'columns' to three.
BrechtDeMan@719 44 %
BrechtDeMan@719 45 % Because of the available 'opening page real-estate'
BrechtDeMan@719 46 % we ask you to refrain from putting more than six authors
BrechtDeMan@719 47 % (two rows with three columns) beneath the article title.
BrechtDeMan@719 48 % More than six makes the first-page appear very cluttered indeed.
BrechtDeMan@719 49 %
BrechtDeMan@719 50 % Use the \alignauthor commands to handle the names
BrechtDeMan@719 51 % and affiliations for an 'aesthetic maximum' of six authors.
BrechtDeMan@719 52 % Add names, affiliations, addresses for
BrechtDeMan@719 53 % the seventh etc. author(s) as the argument for the
BrechtDeMan@719 54 % \additionalauthors command.
BrechtDeMan@719 55 % These 'additional authors' will be output/set for you
BrechtDeMan@719 56 % without further effort on your part as the last section in
BrechtDeMan@719 57 % the body of your article BEFORE References or any Appendices.
BrechtDeMan@719 58
BrechtDeMan@725 59 % FIVE authors instead of four, to leave space between first two authors.
djmoffat@721 60 \numberofauthors{5} % in this sample file, there are a *total*
BrechtDeMan@719 61 % of EIGHT authors. SIX appear on the 'first-page' (for formatting
BrechtDeMan@719 62 % reasons) and the remaining two appear in the \additionalauthors section.
BrechtDeMan@719 63 %
BrechtDeMan@719 64 \author{
BrechtDeMan@719 65 % You can go ahead and credit any number of authors here,
BrechtDeMan@719 66 % e.g. one 'row of three' or two rows (consisting of one row of three
BrechtDeMan@719 67 % and a second row of one, two or three).
BrechtDeMan@719 68 %
BrechtDeMan@719 69 % The command \alignauthor (no curly braces needed) should
BrechtDeMan@719 70 % precede each author name, affiliation/snail-mail address and
BrechtDeMan@719 71 % e-mail address. Additionally, tag each line of
BrechtDeMan@719 72 % affiliation/address with \affaddr, and tag the
BrechtDeMan@719 73 % e-mail address with \email.
BrechtDeMan@719 74 %
BrechtDeMan@719 75 % 1st. author
BrechtDeMan@719 76 \alignauthor Nicholas Jillings\\
BrechtDeMan@719 77 \email{n.g.r.jillings@se14.qmul.ac.uk}
BrechtDeMan@725 78 % dummy author for nicer spacing
BrechtDeMan@725 79 \alignauthor
BrechtDeMan@719 80 % 2nd. author
BrechtDeMan@719 81 \alignauthor Brecht De Man\\
BrechtDeMan@719 82 \email{b.deman@qmul.ac.uk}
BrechtDeMan@719 83 \and % use '\and' if you need 'another row' of author names
BrechtDeMan@719 84 % 3rd. author
BrechtDeMan@719 85 \alignauthor David Moffat\\
BrechtDeMan@719 86 \email{d.j.moffat@qmul.ac.uk}
BrechtDeMan@719 87 % 4th. author
BrechtDeMan@719 88 \alignauthor Joshua D. Reiss\\
BrechtDeMan@719 89 \email{joshua.reiss@qmul.ac.uk}
BrechtDeMan@725 90 \and % new line for address
BrechtDeMan@719 91 \affaddr{Centre for Digital Music}\\
BrechtDeMan@719 92 \affaddr{School of Electronic Engineering and Computer Science}\\
BrechtDeMan@719 93 \affaddr{Queen Mary University of London}\\
BrechtDeMan@719 94 \affaddr{Mile End Road,}
BrechtDeMan@719 95 \affaddr{London E1 4NS}\\
BrechtDeMan@719 96 \affaddr{United Kingdom}\\
BrechtDeMan@719 97 }
BrechtDeMan@719 98 %Centre for Digital Music, School of Electronic Engineering and Computer Science, Queen Mary University of London
BrechtDeMan@719 99 %% 5th. author
BrechtDeMan@719 100 %\alignauthor Sean Fogarty\\
BrechtDeMan@719 101 % \affaddr{NASA Ames Research Center}\\
BrechtDeMan@719 102 % \affaddr{Moffett Field}\\
BrechtDeMan@719 103 % \email{fogartys@amesres.org}
BrechtDeMan@719 104 %% 6th. author
BrechtDeMan@719 105 %\alignauthor Charles Palmer\\
BrechtDeMan@719 106 % \affaddr{Palmer Research Laboratories}\\
BrechtDeMan@719 107 % \affaddr{8600 Datapoint Drive}\\
BrechtDeMan@719 108 % \email{cpalmer@prl.com}
BrechtDeMan@719 109 %}
BrechtDeMan@719 110 % There's nothing stopping you putting the seventh, eighth, etc.
BrechtDeMan@719 111 % author on the opening page (as the 'third row') but we ask,
BrechtDeMan@719 112 % for aesthetic reasons that you place these 'additional authors'
BrechtDeMan@719 113 % in the \additional authors block, viz.
BrechtDeMan@719 114 %\additionalauthors{Additional authors: John Smith (The Th{\o}rv{\"a}ld Group,
BrechtDeMan@719 115 %email: {\texttt{jsmith@affiliation.org}}) and Julius P.~Kumquat
BrechtDeMan@719 116 %(The Kumquat Consortium, email: {\texttt{jpkumquat@consortium.net}}).}
BrechtDeMan@719 117 \date{1 October 2015}
BrechtDeMan@719 118 % Just remember to make sure that the TOTAL number of authors
BrechtDeMan@719 119 % is the number that will appear on the first page PLUS the
BrechtDeMan@719 120 % number that will appear in the \additionalauthors section.
BrechtDeMan@719 121
BrechtDeMan@719 122 \maketitle
BrechtDeMan@719 123 \begin{abstract}
BrechtDeMan@719 124 Here comes the abstract.
BrechtDeMan@719 125 \end{abstract}
BrechtDeMan@719 126
BrechtDeMan@719 127
BrechtDeMan@719 128 \section{Introduction}
BrechtDeMan@726 129
BrechtDeMan@726 130 % Listening tests/perceptual audio evaluation: what are they, why are they important
BrechtDeMan@726 131 % As opposed to limited scope of WAC15 paper: also musical features, realism of sound effects / sound synthesis, performance of source separation and other algorithms...
BrechtDeMan@726 132 Perceptual evaluation of audio, in the form of listening tests, is a powerful way to assess anything from audio codec quality over realism of sound synthesis to the performance of source separation, automated music production and
BrechtDeMan@726 133 In less technical areas, the framework of a listening test can be used to measure emotional response to music or test cognitive abilities. % maybe some references? If there's space.
BrechtDeMan@726 134
BrechtDeMan@726 135 % Why difficult? Challenges? What constitutes a good interface?
BrechtDeMan@726 136 Technical, interfaces, user friendliness, reliability
BrechtDeMan@726 137
BrechtDeMan@726 138 Note that the design of an effective listening test further poses many challenges unrelated to interface design, which are beyond the scope of this paper \cite{bech}.
BrechtDeMan@726 139
BrechtDeMan@726 140 % Why in the browser?
BrechtDeMan@726 141 Web Audio API has made some essential features like sample manipulation of audio streams possible \cite{schoeffler2015mushra}.
BrechtDeMan@719 142
BrechtDeMan@725 143 Situating the Web Audio Evaluation Tool between other currently available evaluation tools, ...
BrechtDeMan@725 144
BrechtDeMan@725 145 % only browser-based?
BrechtDeMan@725 146 \begin{table*}[htdp]
BrechtDeMan@725 147 \caption{Table with existing listening test platforms and their features}
BrechtDeMan@725 148 \begin{center}
BrechtDeMan@725 149 \begin{tabular}{|*{6}{l|}}
BrechtDeMan@725 150 \hline
BrechtDeMan@726 151 \textbf{Name} & \textbf{Ref.} & \textbf{Language} & \textbf{Interfaces} & \textbf{Remote} & \textbf{All UI} \\
BrechtDeMan@725 152 \hline
BrechtDeMan@726 153 APE & \cite{ape} & MATLAB & multiple stimulus one axis & & \\
BrechtDeMan@725 154 BeaqleJS & \cite{beaqlejs} & JavaScript & & not natively supported & \\
BrechtDeMan@726 155 HULTI-GEN & \cite{hultigen} & MAX & & & \checkmark \\
BrechtDeMan@726 156 \textbf{WAET} & \cite{waet} & JavaScript & \textbf{all of the above} & \checkmark & \checkmark \\
BrechtDeMan@725 157 \hline
BrechtDeMan@725 158 \end{tabular}
BrechtDeMan@725 159 \end{center}
BrechtDeMan@725 160 \label{tab:toolboxes}
BrechtDeMan@725 161 \end{table*}%
BrechtDeMan@725 162
BrechtDeMan@725 163 % about BeaqleJS
BrechtDeMan@725 164 ... However, BeaqleJS \cite{beaqlejs} does not make use of the Web Audio API, %requires programming knowledge...
BrechtDeMan@725 165
BrechtDeMan@725 166 %
BrechtDeMan@726 167 Selling points: remote tests, visualisaton, create your own test in the browser, many interfaces, few/no dependencies, flexibility
BrechtDeMan@726 168
BrechtDeMan@726 169 As recruiting participants can be very time-consuming, and as for some tests a large number of participants is needed, browser-based tests \cite{schoeffler2015mushra}. However, to our knowledge, no tool currently exists that allows the creation of a remotely accessible listening test. % I wonder what you can do with Amazon Mechanical Turk and the likes.
BrechtDeMan@726 170
BrechtDeMan@726 171 [Talking about what we do in the various sections of this paper. Referring to \cite{waet}. ]
BrechtDeMan@725 172
BrechtDeMan@725 173
BrechtDeMan@726 174 \section{Architecture} % title? 'back end'? % NICK
BrechtDeMan@719 175 A slightly technical overview of the system. Talk about XML, JavaScript, Web Audio API, HTML5.
BrechtDeMan@725 176 Describe and/or visualise audioholder-audioelement-... structure.
BrechtDeMan@725 177
BrechtDeMan@726 178 % see also SMC12 - less detail here
BrechtDeMan@726 179
BrechtDeMan@726 180 Which type of files? % WAV, anything else? Perhaps not exhaustive list, but say something along the lines of 'whatever browser supports'
BrechtDeMan@724 181
BrechtDeMan@725 182 Streaming audio? % probably not, unless it's easy
BrechtDeMan@725 183
BrechtDeMan@726 184 Compatibility? % not IE, everything else fine?
BrechtDeMan@726 185
BrechtDeMan@726 186
BrechtDeMan@724 187
BrechtDeMan@724 188
BrechtDeMan@725 189 \section{Remote tests} % with previous?
BrechtDeMan@726 190
BrechtDeMan@726 191 If the experimenter is willing to trade some degree of control for a higher number of participants, the test can be hosted on a web server so that subjects can take part remotely. This way, a link can be shared widely in the hope of attracting a large amount of subjects, while listening conditions and subject reliability may be less ideal. However, a sound system calibration page and a wide range of metrics logged during the test mitigate these problems. Note also that in some experiments, it may be preferred that the subject has a `real life', familiar listening set-up, for instance when perceived quality differences on everyday sound systems are investigated.
BrechtDeMan@726 192 Furthermore, a fully browser-based test, where the collection of the results is automatic, is more efficient and technically reliable even when the test still takes place under lab conditions.
BrechtDeMan@726 193
BrechtDeMan@724 194 The following features allow easy and effective remote testing:
BrechtDeMan@724 195 \begin{itemize}
BrechtDeMan@724 196 \item PHP script to collect result XML files
BrechtDeMan@724 197 \item Randomly pick specified number of audioholders
BrechtDeMan@726 198 \item Calibration
BrechtDeMan@724 199 \item Functionality to participate multiple times
BrechtDeMan@724 200 \begin{itemize}
BrechtDeMan@724 201 \item Possible to log in with unique ID (no password)
BrechtDeMan@724 202 \item Pick `new user' (need new, unique ID) or `already participated' (need already available ID)
BrechtDeMan@724 203 \item Store XML on server with IDs plus which audioholders have already been listened to
BrechtDeMan@724 204 \item Don't show `post-test' survey after first time
BrechtDeMan@724 205 \item Pick `new' audioholders if available
BrechtDeMan@724 206 \item Copy survey information first time to new XMLs
BrechtDeMan@724 207 \end{itemize}
BrechtDeMan@724 208 \item Intermediate saves
BrechtDeMan@724 209 \item Collect IP address information (privacy issues?) --> geo-related API?
BrechtDeMan@726 210 \item Time measurement - see before or
BrechtDeMan@724 211 \end{itemize}
BrechtDeMan@724 212
BrechtDeMan@719 213
BrechtDeMan@725 214 \section{Interfaces} % title? 'Front end'? % Dave
BrechtDeMan@725 215 `Build your own test'
BrechtDeMan@725 216
BrechtDeMan@726 217 Elements present to build any of the following interfaces, and many more: axes, markers, labels, anchors, references, reference signal button, stop button, comment boxes, radio buttons, checkboxes, transport/scrubber bar
BrechtDeMan@726 218
BrechtDeMan@726 219 Established tests (see below) included as `presets' in the build-your-own-test page.
BrechtDeMan@726 220
BrechtDeMan@726 221
BrechtDeMan@719 222 We could add more interfaces, such as:
BrechtDeMan@719 223 \begin{itemize}
BrechtDeMan@725 224 \item (APE style) \cite{ape}
BrechtDeMan@719 225 \item Multi attribute ratings
djmoffat@721 226 \item MUSHRA (ITU-R BS. 1534)~\cite{recommendation20031534}
djmoffat@721 227 \item Interval Scale~\cite{zacharov1999round}
djmoffat@721 228 \item Rank Scale~\cite{pascoe1983evaluation}
BrechtDeMan@719 229
djmoffat@721 230 \item 2D Plane rating - e.g. Valence vs. Arousal~\cite{carroll1969individual}
djmoffat@721 231 \item Likert scale~\cite{likert1932technique}
djmoffat@720 232
BrechtDeMan@725 233 \item {\bf All the following are the interfaces available in HULTI-GEN~\cite{hultigen} }
djmoffat@721 234 \item ABC/HR (ITU-R BS. 1116)~\cite{recommendation19971116}
djmoffat@720 235 \begin{itemize}
djmoffat@720 236 \item Continuous Scale (5-1) Imperceptible, Perceptible but not annoying, slightly annoying, annoying, very annoying. (default Inaudible?)
djmoffat@720 237 \end{itemize}
djmoffat@720 238 \item -50 to 50 Bipolar with Ref
djmoffat@720 239 \begin{itemize}
djmoffat@720 240 \item Scale -50 to 50 on Mushra with default values as 0 in middle and a comparison ``Reference'' to compare to 0 value
djmoffat@720 241 \end{itemize}
djmoffat@721 242 \item Absolute Category Rating (ACR) Scale~\cite{rec1996p}
djmoffat@720 243 \begin{itemize}
djmoffat@720 244 \item 5 point Scale - Bad, Poor, Fair, Good, Excellent (Default fair?)
djmoffat@720 245 \end{itemize}
djmoffat@721 246 \item Degredation Category Rating (DCR) Scale~\cite{rec1996p}
djmoffat@720 247 \begin{itemize}
djmoffat@720 248 \item 5 point Scale - Inaudible, Audible but not annoying, slightly annoying, annoying, very annoying. (default Inaudible?) - {\it Basically just quantised ABC/HR?}
djmoffat@720 249 \end{itemize}
djmoffat@721 250 \item Comparison Category Rating (CCR) Scale~\cite{rec1996p}
djmoffat@720 251 \begin{itemize}
djmoffat@720 252 \item 7 point scale: Much Better, Better, Slightly Better, About the same, slightly worse, worse, much worse - Default about the same with reference to compare to
djmoffat@720 253 \end{itemize}
djmoffat@721 254 \item 9 Point Hedonic Category Rating Scale~\cite{peryam1952advanced}
djmoffat@720 255 \begin{itemize}
djmoffat@720 256 \item 9 point scale: Like Extremely, Like Very Much, Like Moderate, Like Slightly, Neither Like nor Dislike, dislike Extremely, dislike Very Much, dislike Moderate, dislike Slightly - Default Neither Like nor Dislike with reference to compare to
djmoffat@720 257 \end{itemize}
djmoffat@721 258 \item ITU-R 5 Point Continuous Impairment Scale~\cite{rec1997bs}
djmoffat@720 259 \begin{itemize}
djmoffat@720 260 \item 5 point Scale (5-1) Imperceptible, Perceptible but not annoying, slightly annoying, annoying, very annoying. (default Inaudible?)- {\it Basically just quantised ABC/HR, or Different named DCR}
djmoffat@720 261 \end{itemize}
djmoffat@721 262 \item Pairwise Comparison (Better/Worse)~\cite{david1963method}
djmoffat@720 263 \begin{itemize}
djmoffat@720 264 \item 2 point Scale - Better or Worse - (not sure how to default this - they default everything to better, which is an interesting choice)
djmoffat@720 265 \end{itemize}
BrechtDeMan@719 266 \end{itemize}
BrechtDeMan@719 267
BrechtDeMan@719 268 There are also the following interfaces, which would require a slightly different `engine' underneath, e.g. loading a different page for every possible pair.
BrechtDeMan@719 269 \begin{itemize}
djmoffat@721 270 \item AB Test~\cite{lipshitz1981great}
djmoffat@721 271 \item ABX Test~\cite{clark1982high}
BrechtDeMan@719 272 \item JND
BrechtDeMan@719 273 \end{itemize}
BrechtDeMan@719 274
BrechtDeMan@719 275 A screenshot would be nice.
BrechtDeMan@719 276
BrechtDeMan@719 277 \section{Analysis and diagnostics}
BrechtDeMan@726 278 % don't mention Python scripts
BrechtDeMan@719 279 It would be great to have easy-to-use analysis tools to visualise the collected data and even do science with it. Even better would be to have all this in the browser. Complete perfection would be achieved if and when only limited setup, installation time, and expertise are required for the average non-CS researcher to use this.
BrechtDeMan@719 280
BrechtDeMan@722 281 The following could be nice:
BrechtDeMan@722 282
BrechtDeMan@722 283 \begin{itemize}
BrechtDeMan@722 284 \item Web page showing all audioholder IDs, file names, subject IDs, audio element IDs, ... in the collected XMLs so far (\texttt{saves/*.xml})
BrechtDeMan@722 285 \item Check/uncheck each of the above for analysis (e.g. zoom in on a certain song, or exclude a subset of subjects)
BrechtDeMan@722 286 \item Click a mix to hear it (follow path in XML setup file, which is also embedded in the XML result file)
BrechtDeMan@722 287 \item Box plot, confidence plot, scatter plot of values (for a given audioholder)
BrechtDeMan@722 288 \item Timeline for a specific subject (see Python scripts), perhaps re-playing the experiment in X times realtime. (If actual realtime, you could replay the audio...)
BrechtDeMan@722 289 \item Distribution plots of any radio button and number questions (drop-down menu with `pretest', `posttest', ...; then drop-down menu with question `IDs' like `gender', `age', ...; make pie chart/histogram of these values over selected range of XMLs)
BrechtDeMan@722 290 \item All `comments' on a specific audioelement
BrechtDeMan@722 291 \item A `download' button for a nice CSV of various things (values, survey responses, comments) people might want to use for analysis, e.g. when XML scares them
BrechtDeMan@724 292 \item Validation of setup XMLs (easily spot `errors', like duplicate IDs or URLs, missing/dangling tags, ...)
BrechtDeMan@722 293 \end{itemize}
BrechtDeMan@722 294
BrechtDeMan@722 295 A subset of the above would already be nice for this paper.
BrechtDeMan@722 296
BrechtDeMan@719 297 Some pictures here please.
BrechtDeMan@719 298
BrechtDeMan@725 299 \section{Concluding remarks and future work}
BrechtDeMan@719 300
BrechtDeMan@726 301 The code and documentation can be pulled or downloaded from \url{code.soundsoftware.ac.uk/projects/webaudioevaluationtool}.
BrechtDeMan@719 302
BrechtDeMan@726 303 [Talking a little bit about what else might happen. Unless we really want to wrap this up. ]
BrechtDeMan@725 304
BrechtDeMan@726 305 Use \cite{schoeffler2015mushra} as a `checklist', even though it only considers subjective evaluation of audio systems (and focuses on the requirements for a MUSHRA test).
BrechtDeMan@726 306 % remote
BrechtDeMan@726 307 % language support (not explicitly stated)
BrechtDeMan@726 308 % crossfades
BrechtDeMan@726 309 % choosing speakers/sound device from within browser?
BrechtDeMan@726 310 % collect information about software and sound system
BrechtDeMan@726 311 % buttons, scales, ... UI elements
BrechtDeMan@726 312 % must be able to load uncompressed PCM
BrechtDeMan@726 313
BrechtDeMan@726 314 [What can we not do? `Method of adjustment', as in \cite{schoeffler2015mushra} is another can of worms, because, like, you could adjust lots of things (volume is just one of them, that could be done quite easily). Same for using input signals like the participant's voice. Either leave out, or mention this requires modification of the code we provide.]
BrechtDeMan@719 315
BrechtDeMan@719 316 %
BrechtDeMan@719 317 % The following two commands are all you need in the
BrechtDeMan@719 318 % initial runs of your .tex file to
BrechtDeMan@719 319 % produce the bibliography for the citations in your paper.
BrechtDeMan@719 320 \bibliographystyle{abbrv}
BrechtDeMan@719 321 \bibliography{WAC2016} % sigproc.bib is the name of the Bibliography in this case
BrechtDeMan@719 322 % You must have a proper ".bib" file
BrechtDeMan@719 323 % and remember to run:
BrechtDeMan@719 324 % latex bibtex latex latex
BrechtDeMan@719 325 % to resolve all references
BrechtDeMan@719 326 %
BrechtDeMan@719 327 % ACM needs 'a single self-contained file'!
BrechtDeMan@719 328 %
BrechtDeMan@719 329 \end{document}