

\documentclass[11pt]{amsart}


\title{EMBS Meeting notes}
\author{cgarcia}
\date{13/9/2012}                                           % Activate to display a given date or no date



\begin{document}

Rob reading through the forms:

\begin{itemize}
\item contact people before the workshop (using mailing list) maybe a week before: repeat the requirements, advertise more what is needed: laptop etc
\item at the beginning of the lab: need 30min for installation and set up so people can�t and feel left behind - or pair people up
\item too ambiguous in demo about what they should be doing (sometime they will follow, sometime just watch) so we need to be clear : �this is watch and see and then you�ll have the opportunity� or have a follow along: �everybody does  \item that, are we all good: so that they move as the presenter do and should be ready to move on after the follow on demo
\item have backup laptops around (specially if we know ahead of time)
\item running software from the command line is something people don�t always know how to do: should we have a quick introduction on command lines? or set up an easy window interface (more advantages for a general audience)?
\item lack of dissemination of knowledge from PhD students: we can be pro active: we should have pre requisite / identify target of participants: we expect people to have this level of background, and also allows to adapt as we hear of their \item lacks. we can also send them links to where to find info before attending.
\item talks structure: follow Rob�s format (description, what the software helps with etc...) maybe have all presentations follow the same structure.
\item people who give their email address -> mailing list
\item spend more time to explain the pipeline! maybe have a longer workshop?

\item someone: would like to see more demo (we only had demo... !)
\item review the Biomesh part: which examples, decide if we want the demo to be more interactive
\item problem to run on Microsoft Windows: Seg3D and Imagevis get affected if bad driver quality
\item best thing: the case studies, visualization works
\end{itemize}


Feedback from CIBC team
\begin{itemize}
\item starting with a tutorial, having everybody on the same page 
\item set up time at the beginning
\item to be less dependent to the mailing list, but if we had a registration page, we would know the emails before. Need to coordinate with conference to see if we could do that.
\item Seyhmus: Tutorials for people with less experience: run the software in front desk during lab session. Biomesh / SCIRun: could we do SCIRun first, and then Biomesh (avoid confusions)
\item Is the time for each section adequate? This time we didn�t hear back form participants that the timing was wrong. Maybe not enough time for people on their own data : maybe on 1day we should not tell them to bring their data because you don�t really have time to work on it anyway. Discourage use of their data until the last hour for example. 
\item Shapeworks (Biomesh): we need some package for it: CIBC Project. Plan on no internet connection.
\item Embarrassing: drivers crashing, technical difficulties. We are already working on it, and we continue to make it more robust.
\item build on the case study format
\item it�s an expensive marketing activity, but it�s worth getting all the feedback.
\end{itemize}






\end{document}  