From BFMAIL@SLACVM.BITNET Thu Mar  2 18:14:59 1995
Received: from SERV02.SLAC.STANFORD.EDU (SERV02.SLAC.Stanford.EDU [134.79.16.10]) by mailbox.SLAC.Stanford.EDU (8.6.9/8.6.9) with SMTP id SAA25603; Thu, 2 Mar 1995 18:14:50 -0800
Received: from DIRECTORY-DAEMON by SERV02.SLAC.STANFORD.EDU
 (PMDF V4.3-10 #6987) id <01HNO4AQ6HWG001EF1@SERV02.SLAC.STANFORD.EDU>; Thu,
 02 Mar 1995 18:12:25 -0800 (PST)
Received: from SLACVM.SLAC.STANFORD.EDU (MAILER@SLACVM)
 by SERV02.SLAC.STANFORD.EDU (PMDF V4.3-10 #6987)
 id <01HNO42NUU9C001EF1@SERV02.SLAC.STANFORD.EDU>; Thu,
 02 Mar 1995 18:06:27 -0800 (PST)
Received: from SLACVM.SLAC.STANFORD.EDU (BFMAIL) by SLACVM.SLAC.STANFORD.EDU
 (Mailer R2.08 R208004) with BSMTP id 4636; Thu, 02 Mar 95 18:00:07 PST
Date: Thu, 02 Mar 1995 17:58 -0800 (PST)
From: witherel@MAILBOX.SLAC.Stanford.EDU
Subject: Organization of analysis
To: Distribution@SERV02.SLAC.Stanford.EDU (RASORG EXECBOARD TECHBOARD COMPUTING)
Message-id: <01HNO438BWSI001EF1@SERV02.SLAC.STANFORD.EDU>
X-Envelope-to: boeheim@MAILBOX.SLAC.Stanford.EDU,
 chee@MAILBOX.SLAC.Stanford.EDU, claus@MAILBOX.SLAC.Stanford.EDU,
 cottrell@MAILBOX.SLAC.Stanford.EDU, dragon@MAILBOX.SLAC.Stanford.EDU,
 ESR@MAILBOX.SLAC.Stanford.EDU, gounder@MAILBOX.SLAC.Stanford.EDU,
 gxh@MAILBOX.SLAC.Stanford.EDU, jlw@MAILBOX.SLAC.Stanford.EDU,
 jxh@MAILBOX.SLAC.Stanford.EDU, ljm@MAILBOX.SLAC.Stanford.EDU,
 mcgrath@MAILBOX.SLAC.Stanford.EDU, ralph@MAILBOX.SLAC.Stanford.EDU,
 randym@MAILBOX.SLAC.Stanford.EDU, snyder@MAILBOX.SLAC.Stanford.EDU,
 tkb@MAILBOX.SLAC.Stanford.EDU, wbj@MAILBOX.SLAC.Stanford.EDU
Content-transfer-encoding: 7BIT
Status: RO

Draft Proposal on Organization of the Reconstruction
and Analysis Software Effort.


This is a proposal developed by consensus among four members
of an ad hoc subcommittee of the Executive Board:
Fry, Giorgi, Witherell, Wormser,
after a meeting with interested parties, many one-on-one
conversations, written comments, and a document submitted by
the computing group.

There was an extraordinarily wide range of opinion on how these
structures should be set up.  The following proposal was
reached by building on those areas in which there was
a fairly wide consensus.  Although most people we have
talked to agree with much of this proposal, many disagree
with at least one aspect of it.  Most often the disagreeing
views are of opposite direction.

We are going to be discussing this proposal in the Executive
Board next week at the collaboration meeting.  If you have
strong objections to parts or all of this proposal, or even
if you want to express your agreement with it, you should communicate
by e-mail to one or all of the four people mentioned above.*  Or, if you
would prefer, you can send comment to the Executive Board
as a whole through the BFMAIL list.

*[fry@cernvm.cern.ch,wormser@frcpn11.in2p3.fr,giorgi@pisa.infn.it,
witherell@sbhep.physics.ucsb.edu]

------------------------------------------------------------------------------
There are three positions which would be appointed
by the Exec. Board.  The rest of the organization
would be worked out by them, and with the computing group.
The three positions would be
1)Reconstruction manager.
2)DST analysis manager.
3)Physics coordinator.
These are discussed in turn.

1)RECONSTRUCTION MANAGER

This person is responsible for the content of the
reconstruction program, for coordinating the reconstruction
efforts of the various detector groups,
for recruiting people to take responsibilities in this area, and
for making sure that the reconstruction program
is completely integrated into the software system
developed by the computing group.

The reconstruction manager will be co-head of an analysis software
group, separate from the computing group,
although reporting to the computing group on the computing
system aspects.  He or she will convene meetings of reconstruction leaders
from each detector group.  In addition,
the reconstruction manager should report to the computing
group on the integration of the reconstruction package into
the software system, since the ultimate responsibility
for the standards of the software system is with the
managers of the computing group.  The primacy of
the computing group on setting these standards must
be understood from the beginning.

The reconstruction manager is a full time position,
and the person who takes on the job
should have no other significant responsibilities on
BABAR or another experiment.  It requires the same commmitment
as a system manager, during the time of appointment.
The reconstruction manager should be appointed
for a two year period, renewable.

There will also be a simulation manager,
who will operate as an assistant to the reconstruction manager,
and as such will not be included in the initial three appointments.

2. DATA SUMMARY TAPE (DST) ANALYSIS MANAGER

This person is responsible for taking the reconstructed
data and getting it ready for everybody in the experiment
to do physics analysis with.  It therefore involves coordinating work on
developing analysis tools needed for DST analysis,
especially those using information from multiple detectors.
This would involve coordination
with the computing group and with the reconstruction manager.

The DST Analysis Manager would be co-leader of the analysis software group.
It is also a full time position, with no other significant
responsibilities during the time of the appointment.
The manager is appointed for two years, renewable.

SUMMARY of 1 and 2:
The analysis software group would have two co-leaders,
the Reconstruction Manager and the DST Analysis Manager.

3.PHYSICS COORDINATOR
The third position is someone worrying about the physics
of the experiment in the purest sense.  The work he would
be coordinating might include
a working group to study various strategies for measuring
the third mixing angle, or to study the proper tests to diagnose
non-standard CP violation, or to consider the highest priority
tau physics problems that should be taken up by BABAR at turn on.
This also is the focus of contact with theorists
working on BABAR physics problems.

This person is NOT responsible for developing a large
software structure during the construction period,
as the first two persons are.  Thus it is called a coordinator.


NOTE: A separate Phyics analysis board or panel may be
of interest, to work with the physics coordinator.
The consensus was to not set such a board up until
we reach agreement on the above positions, and possibly
until the physics coordinator is in place.







Distribution to: DISTRIBUTION

