comparison docs/SMC15/smc2015template.tex @ 228:ec0eb2da8dc0

SMC Paper: increased XML size, condensed XML content and rest of paper.

 \setitemize{noitemsep,topsep=0pt,parsep=0pt,partopsep=0pt}
 
 
 
 \usepackage{color}
-\definecolor{gray}{rgb}{0.4,0.4,0.4}
+\definecolor{grey}{rgb}{0.1,0.1,0.1}
 \definecolor{darkblue}{rgb}{0.0,0.0,0.6}
 \definecolor{cyan}{rgb}{0.0,0.6,0.6}
 
 
 \hyphenation{Java-script}

 
 \lstset{
   basicstyle=\ttfamily,
   columns=fullflexible,
   showstringspaces=false,
-  commentstyle=\color{gray}\upshape
+  commentstyle=\color{grey}\upshape
 }
 
 \lstdefinelanguage{XML}
 {
   morestring=[b]",

   identifierstyle=\color{darkblue} \bfseries,
   keywordstyle=\color{cyan} \bfseries,
   morekeywords={xmlns,version,type}, 
   breaklines=true% list your attributes here
 }
-\tiny
+\scriptsize
 \lstset{language=XML}
 
 \begin{lstlisting}
 <?xml version="1.0" encoding="utf-8"?>
 <BrowserEvalProjectDocument>

 			<title>Example Test Question</title>
 			<scale position="0">Min</scale>
 			<scale position="100">Max</scale>
 			<commentBoxPrefix>Comment on fragment</commentBoxPrefix>
 		</interface>
-		<audioElements url="0.wav" id="elem0"/>
 		<audioElements url="1.wav" id="elem1"/>
 		<audioElements url="2.wav" id="elem2"/>
 		<audioElements url="3.wav" id="elem3"/>
 		<CommentQuestion id="generalExperience" type="text">General Comments</CommentQuestion>
 		<PreTest/>

 </BrowserEvalProjectDocument>
 
 \end{lstlisting}
 
 \normalsize
+\vspace{-1em}
 
 \subsection{Setup and configurability}
 
 The setup document has several defined nodes and structure which are documented with the source code. For example, there is a section for general setup options where any pre-test and post-test questions and statements can be defined. Pre- and post-test dialogue 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. In the example set up document above, a question box with the id `location' is added, which is set to be mandatory to answer. The question is in the PreTest node meaning it will appear before any testing will begin. When the result for the  entire test is shown, the response will appear in the PreTest node with the id `location' allowing it to be found easily, provided the id values are meaningful.
 

 
 \subsection{Results}
 
 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 fragment 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. The results also contain information collected by any defined pre/post questions. An excerpt of an output file is presented below detailing the data collected for a single audioElement.
 
-\tiny
+\scriptsize
 \lstset{language=XML}
 
 \begin{lstlisting}
 <browserevaluationresult>
 	<datetime>

 		<comment id="location">Control Room</comment>
 	</pretest>
 	<audioholder>
 		<pretest></pretest>
 		<posttest>
-			<comment id="songGenre">Alternative-Rock</comment>
+			<comment id="songGenre">Pop</comment>
 		</posttest>
 		<metric>
-			<metricresult id="testTime">813.328</metricresult>
+			<metricresult id="testTime">813.32</metricresult>
 		</metric>
-		<audioelement id="elem0">
+		<audioelement id="elem1">
 			<comment>
-				<question>Comment on track 0</question>
-				<response>Like the reverb length and style, however Vocals get lost in the mix.</response>
+				<question>Comment on track 1</question>
+				<response>Good, but vocals too quiet.</response>
 			</comment>
 			<value>0.639010989010989</value>
 			<metric>
-				<metricresult id="elementTimer">111.05066666666663</metricresult>
+				<metricresult id="elementTimer">111.05</metricresult>
 				<metricresult id="elementTrackerFull">
 					<timepos id="0">
-						<time>61.602666666666664</time>
-						<position>0.639010989010989</position>
+						<time>61.60</time>
+						<position>0.6390</position>
 					</timepos>
 				</metricresult>
-				<metricresult id="elementInitialPosition">0.6571428571428571</metricresult>
+				<metricresult id="elementInitialPosition">0.6571</metricresult>
 				<metricresult id="elementFlagListenedTo">true</metricresult>
-				<metricresult id="elementFlagMoved">true</metricresult>
 			</metric>
 		</audioelement>
 	</audioHolder>
 </browserevaluationresult>
 
 \end{lstlisting}
 
 \normalsize
-
-Each page of testing is returned with the results of the entire page included in the structure. One \texttt{audioelement} node is created per audio fragment per page, along with its ID. This includes several child nodes including the rating between 0 and 1, the comment, and any other collected metrics including how long the element was listened for, the initial position, boolean flags if the element was listened to, if the element was moved and if the element comment box had any comment. Furthermore, each user action (manipulation of any interface element, such as playback or moving a marker) can be logged along with a the corresponding time code.
+\vspace{-.5em}
+Each page of testing is returned with the results of the entire page included in the structure. One \texttt{audioelement} node is created per audio fragment per page, along with its ID. This includes several child nodes including the rating between 0 and 1, the comment, and any other collected metrics including how long the element was listened for, the initial position, and boolean flags showing if the element was listened to, moved and commented on. Furthermore, each user action (manipulation of any interface element, such as playback or moving a marker) can be logged along with a the corresponding time code.
 We also store session data such as the time the test took place and the duration of the test.
 We provide the option to store the results locally, and/or to have them sent to a server. 
 
 %Here is an example of the set up XML and the results XML: % perhaps best to refer to each XML after each section (set up <> results)
 % Should we include an Example of the input and output XML structure?? --> Sure.