User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720)
I want to make a proposal for the structure of the two-hour "analysis
software discussions" session on Satuday morning. This I believe is
along the lines of Ashot's original idea for this period, but I wanted
to make it a bit more explicit (only a bit).
The overall idea is to have time devoted to discussion as opposed to
straight one-way presentation. But what to discuss? I am proposing that
we develop a list of topics, centered around analysis and analysis
software, with the development period starting now and continuing
through to the Saturday session. These topics could be:
o Things that were presented on Friday, but were not discussed fully due
to time constraints.
o Things that people are working on and would like some guidance and/or
feedback from the group.
o Complaints that people have about features of the current analysis or
analysis framework.
o Things that we should do differently the next time we run that would
make the analysis easier.
To start with Dustin has a list of a dozen items that, in hindsight,
would have been very helpful to have been done during the run. Another
topic is a scheme Aram and I have discussed for a configuration file for
the analysis program so that user's can set cuts and communicate those
settings easily. Another topic is how we should approach the whole issue
of beam position and angle calibration. Another topic is how we should
use the bookkeeping database Dustin has developed. So that is four
topics already (the first of which actually has dozen or so sub-topics).
I will compile the list and present it more formally. Please send me
your contributions.