Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Det. Search
Who's who?
Intern. region
Vertex Tracker
Drift chamber
Run Coordination
Contact Experts
Shift Takers Info
Operations Manual
Electronic Logbook
Ops Hypernews
Shift Signup
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

Minutes of the March 5 Background Remediation Meeting

  1. GW gave a report on the discussions held during (and shortly after) the collaboration week. A report was given to the Technical Board and is available here. It contains a description of all what is discussed below.
  2. The Background Sensors table

    This report contains a table of the various sensors foreseen for protection and monitoring. A. McKemey and T. Geld are now responsible of correcting this table, and keeping it up to date with status informations for each sensor. T. Mattison will investigate with PEP-II people (in particular M. Zisman and U. Wienands) whether there is a need for another communication channel besides SAMs and EPICS.

    The action items table.

    This table summarizes on one (dense) page the present list of action items Latest additions/comments are:

    -Shielding improvment for DC electronics. T. Schietinger showed that the expected dose in the DCH elecronics area was not negligeable (Up to 200 rad/year for nonimal background), therefore underlining the need for extra shielding. Richard Boyce has volunteered to look up to the engineering details.

    Operational aspects

    -A discussion is foreseen March 9 in a Technical Board session about the background related operational aspects : decision forums at the various levels (top management, run coordination, shift level), the role and future of the background remediation group.

    The training week March 29/April 1st

    It will consist of the following 8 sessions. The sessions managers indicated below are responsible for organizing their sessions: recruit the proper speakers, publicize in adavnce already existing video or written documentation, collect the material shown for future training sessions, determine the time allocation for their sessions (usually 90 but a lot of freedom exists). If you are listed as an organizer but can not make it, please conatct me asap , preferably with another victim name!

    Session 1 Machine Basics J. Seeman

    Session 2 Background Basics W. Kozanecki

    Session3 BABAR exposure A. Mckemey, C. Hast

    Session 4 Machine Operation, MCC control room R. Erikson

    Session 5 Background sensors P. Burchat, T. Geld

    Session 6 the protection system T. Mattison, P. Burchat

    Session 7 Analysis tools :SCP, EPICS,MATLAB, others J. Olsen, P.Anthony, Ron S.?

    Session 8 Running BABAR I. Karyotakis

    The next training session is scheduled May 3-6. Hopefully, it will contain many videotaped sessions.

    1.5 Start up scenarios

    A detailed list of tasks to be performed at PEP-II/BABAR start up has been prepared by Tom Mattison. We need to elaborate , try to add time allocations to give a rough estimate ,etc..

    The various start up scenarios for machine operation were disucssed during the collab. week and at the tech. Board. If BABAR and PEP-II are in good shape at the beginning, the best scenario would be to take clean data at low machine current, and steadily increase the currents. Otherwise, a initial scrubbing period can be required

    leading to higher luminosity running quicker but to larger integrated doses in BABAR.

  3. Report form other action items

A SIAM will be implemented by C. Hearty to enforce the DCH_ON interlock to injection. The SVT group has agreed to also send a SVT_ON signal to this module.

The BABAR NOT_Injectable_Flag bit will be echoed in the PEP-II logic even when BABAR EPICS is not fully running.