changeset 8:19860a7f547f

More smallish updates

--- a/cannam.tex	Thu Sep 22 10:36:09 2011 +0100
+++ b/cannam.tex	Thu Sep 22 11:12:34 2011 +0100
@@ -109,7 +109,7 @@
 this field appears limited.  In our survey of UK audio and music
 researchers (see section \ref{sec:survey}), the majority of
 respondents said either that they took no steps to ensure
-reproducibility, or that they only made code or data available on
+reproducibility or that they only made code or data available on
 request.  Obstacles cited included lack of time, copyright
 restrictions, and the potential for commercial use of the code
 \cite{ssamrsurvey}.  In addition to these, a broader case study by the
@@ -129,17 +129,19 @@
 skills or desire to write their own code or to make someone else's
 code work, and where they do write their own code, they work on
 different platforms and use a wide variety of batch and real-time
-environments.  A study in 2009 found that scientists typically
+environments.  A study in 2009 found a great deal of variation in the
+level of understanding of standard software engineering concepts by
+scientists, and found that for developing and using scientific
+software, informal self-study or learning from peers was commonplace
+\cite{gwilson2009}.  The study found that scientists typically
 developed and used software on their personal computers rather than
-dedicated servers, that there was a great deal of variation in the
-level of understanding of standard software engineering concepts by
-scientists, and that for developing and using scientific software,
-informal self-study or learning from peers was commonplace
-\cite{gwilson2009}.  Our survey found MATLAB and numerous MATLAB
-toolboxes, C++, Max/MSP, OpenFrameworks, Juce, HTK and MPTK,
-SuperCollider, Clojure and R amongst environments and toolkits used
-\cite{ssamrsurvey}, and recent publications from our group have also
-used Python \cite{fazekas} and Prolog \cite{raimond}.
+dedicated servers, and our own survey also found that most respondents
+kept code on their own machines and did not develop collaboratively
+\cite{ssamrsurvey}.  We found a variety of environments and toolkits
+used, including MATLAB and numerous MATLAB toolboxes, C++, Max/MSP,
+OpenFrameworks, Juce, HTK and MPTK, SuperCollider, Clojure and
+R. Recent publications from our group have also made use of Python
+\cite{fazekas} and Prolog \cite{raimond}.
 
 As a consequence of the lack of publication and variety of platforms
 used, software developed in earlier research is not always readily
@@ -174,23 +176,41 @@
 
 \subsection{Education and Confidence With Code}
 
+introductory note here: the barrier is that people lack software
+development skills
+
 \subsubsection{SoundSoftware/Software Carpentry Autumn School}
 \label{sec:autumnschool}
+
+In November 2010 we organised an Autumn School for researchers,
+presented by Dr Greg Wilson and based on the Software Carpentry
+materials \cite{softwarecarpentry}.  This week-long residential course
+for 20 audio and music researchers from groups around the UK taught
+fundamentals of software development and good practice including
+version control, unit testing, Python syntax and structure, and
+managing small result databases with sqlite.
+
 \subsubsection{Videos and Tutorials}
 
 \subsection{Facilities and Tools}
+
+introductory note here: the barrier is that people lack facilities
+or don't use them
+
 \subsubsection{SoundSoftware Code Site}
 \label{sec:codesite}
 
-\subsubsubsection{Public and private projects}
-\subsubsubsection{Linking publications with code}
-\subsubsubsection{Tracking external projects}
+
+(Public and private projects; Linking publications with code; Tracking external projects)
 
 \subsubsection{Version control and EasyMercurial}
 \label{sec:easyhg}
 
 \subsection{Platforms and Reuse}
 
+introductory note here: the barrier is that software that is published
+is not always usable
+
 \subsubsection{Sonic Visualiser and Vamp Plugins}
 \label{subsubsec:sv}
 
@@ -245,11 +265,6 @@
 \subsubsection{Auditory Image Models}
 \label{subsubsec:aim}
 
-\subsubsection{AudioDB}
-\label{subsubsec:audiodb}
-
-\section{Evaluation}
-\label{sec:evaluation}
 \section{Future work}
 \label{sec:future}