RUN 2B L1CAL MEETING MINUTES
                 4 October, 2005

Present 
o Fermilab      L.Bagby, C.Fantasiam, G.Ginther, B.Hirosky, S.Lammers, 
                M.Mulhearn, Md.Naimuddin, N.Varelas, M.Verzocchi, A.Stone
o FSU           T.Adams
o Indiana       H.Evans
o MSU           C.Brock, D.Edmunds, P.Laurens
o Nevis         J.Parsons
o Northeastern  A.Roe, D.Wood
o SMU           B.Kehoe
o York          S.Beale, W.Taylor

(apologies to those I couldn't see)


Definition of "Stable Operations Mode"
--------------------------------------

During the collaboration meeting last week, we decided to push to
achieve "Stable Operations" with the currently existing splitters and
the full Run IIb L1Cal system.  The goal is to participate in normal
D0 runs using (probably) 16 and/or terms in the TFW (taken from the
currently unused FPS allocation) as test triggers for us


Category-by-Category Discussion of what is Needed
-------------------------------------------------
Please look over this list and the presentations attached to the
agenda and send suggestions for improvement to the L1Cal mailing
list. We are aiming to have a "final" task list prepared by the
meeting next Monday.

1) Hardware & Infrastructure
   - see Infrastructure_Task_List-1.pdf linked off agenda
     . L2 fibers: send all fibers to L2 Test Stand
     . configuration of racks - is it ok to have 2 ADF crates in one
       rack?
       > need to double-check this with Dan
   - see "Core Hardware Functionality of TABs and GAB" off agenda
     . need to define what is an acceptable rate of errors
     . how much D0 downtime is acceptable ?
       > answer: this is exactly the time to minimize the downtime
     . algorithm changes during stable operations
       > these are inevitable - need to limit/clearly define them

   General Questions
   - how do we anticipate running ? 
     . answer: as part of normal D0 running
   - should we move splitters around the calorimeter
     . answer: this is possible
     . could be used to cross-check calibrations in some limited areas
     . note: moving the splitters will affect the examines

2) Required System I/O
   - CalTrack: see "Caltrk operations" off agenda
   - L2: send all fibers to L2 Test Stand
     . do parity checks

3) Online Control Software
   - programming of L1Cal from COOR: program as real system
     . COOR side: should be done by the end of the month
     . TCC: 
       > done for ADF
       > interface defined for TAB/GAB
   - configure system in one click
   - initialization
   - Trigger Database: this is an unknown
     . hopefully will start putting IIb terms into TDB next week
   - initialize readout crate from TCC

4) Interactions with COOR & Triggers
   - see "Data acquisition and monitoring..." off agenda for some
     information here

5) Diagnostic Test Software
   - need to define what diagnostics we need

6) Online Monitoring
   - see "monitoring gui's for stable operations mode" off agenda
   - will meet to define monitoring information next week
   - need to write routines to collect the information
     . esp. from the TABs/GAB

7) Offline Data Access
   - see "Data acquisition and monitoring..." off agenda for some
     information here

8) Examines
   - see "l1cal examine 2b"
   - timescale: early Nov.
     . everything should be straightforward except for the masks
   - may need to add new information from the GAB (requires firmware
     and unpacker mod's)

9) Pulser
   - need to do some checks with Dan
   - need to put in Run IIb unpacker

10) Simulation (impact on operations)
   - implementing changes to agree with firmware
   - see "Data acquisition and monitoring..." off agenda for some
     information here

11) Strategy for "Stable Operations Mode"
    - how do we decide if we have achieved this mode ?
    - what do we want to accomplish during this period ?