Mercurial > hg > webaudioevaluationtool
comparison docs/WAC2016/WAC2016.tex @ 312:8aefcf569e7b WAC2016
Paper: added ideas for in-the-browser visualisation, diagnostics and analysis
author | Brecht De Man <b.deman@qmul.ac.uk> |
---|---|
date | Wed, 23 Sep 2015 14:42:02 +0200 |
parents | 1b168b627cb9 |
children | ffd14d1f9ad7 464ca23d5f39 |
comparison
equal
deleted
inserted
replaced
310:1b168b627cb9 | 312:8aefcf569e7b |
---|---|
23 \conferenceinfo{Web Audio Conference WAC-2016,}{April 4--6, 2016, Atlanta, USA} | 23 \conferenceinfo{Web Audio Conference WAC-2016,}{April 4--6, 2016, Atlanta, USA} |
24 \CopyrightYear{2016} % Allows default copyright year (20XX) to be over-ridden - IF NEED BE. | 24 \CopyrightYear{2016} % Allows default copyright year (20XX) to be over-ridden - IF NEED BE. |
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. | 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. |
26 % --- End of Author Metadata --- | 26 % --- End of Author Metadata --- |
27 | 27 |
28 \title{Latex Template for WAC 2016} | 28 \title{Web Audio Evaluation Tool something something} |
29 %\subtitle{[Extended Abstract] | 29 %\subtitle{[Extended Abstract] |
30 %\titlenote{A full version of this paper is available as | 30 %\titlenote{A full version of this paper is available as |
31 %\textit{Author's Guide to Preparing ACM SIG Proceedings Using | 31 %\textit{Author's Guide to Preparing ACM SIG Proceedings Using |
32 %\LaTeX$2_\epsilon$\ and BibTeX} at | 32 %\LaTeX$2_\epsilon$\ and BibTeX} at |
33 %\texttt{www.acm.org/eaddress.htm}}} | 33 %\texttt{www.acm.org/eaddress.htm}}} |
185 A screenshot would be nice. | 185 A screenshot would be nice. |
186 | 186 |
187 \section{Analysis and diagnostics} | 187 \section{Analysis and diagnostics} |
188 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. | 188 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. |
189 | 189 |
190 The following could be nice: | |
191 | |
192 \begin{itemize} | |
193 \item Web page showing all audioholder IDs, file names, subject IDs, audio element IDs, ... in the collected XMLs so far (\texttt{saves/*.xml}) | |
194 \item Check/uncheck each of the above for analysis (e.g. zoom in on a certain song, or exclude a subset of subjects) | |
195 \item Click a mix to hear it (follow path in XML setup file, which is also embedded in the XML result file) | |
196 \item Box plot, confidence plot, scatter plot of values (for a given audioholder) | |
197 \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...) | |
198 \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) | |
199 \item All `comments' on a specific audioelement | |
200 \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 | |
201 \end{itemize} | |
202 | |
203 A subset of the above would already be nice for this paper. | |
204 | |
190 Some pictures here please. | 205 Some pictures here please. |
191 | 206 |
192 \section{Concluding remarks} | 207 \section{Concluding remarks} |
193 Perhaps an `engineering brief' such as this one doesn't really have a lot of conclusion, except `We made this'. | 208 Perhaps an `engineering brief' such as this one doesn't really have a lot of conclusion, except `We made this'. |
194 | 209 |