Previous      Next      Directory 

Folder:   MUON
From:     diehl@d0nt52.fnal.gov
Subject:  Monday Morning Muon Meeting Minutes 10/16/00
Date:     16-OCT-2000 18:39
Expires:  31-OCT-2000 17:39



Muon Commissioning Meeting  10/16/00

Agenda:
News -  Diehl
MFC/MFCTC production/status - Mark Kozlovsky
MFCTC Software Program - Satya Bheesette
Around the Room - All 
AOB



News - Diehl
  Electricians are working on EFS and sometimes working from baskets
  hanging by the crane. Sidewalk access will be unavailable when they 
  are working overhead.
    Next meeting - next week. 

MFC/MFCTC production/status - Mark Kozlovsky
    Muon Fanout cards (MFC's) were shipped to the lab by UPS Next-day air on 
  Friday and are possibly on site today.  The 18 boards are stuffed but not 
  tested. We require 9 more to fill all of our readout crates. 
    The Muon Fanout Card Tester Card is perhaps 50% debugged. Mark 
  was hesitant to make an estimate as to how much work was involved in 
  finishing it. Terry O'Brian is working on it (part time?). Mark was 
  working on it a few hours a week. 
    The plan for the week:  Concentrate on the MFCTC all week long. It 
  is likely Satya Bheesette will have to go back to TIFR at the end of the 
  week.  We should take advantage of his presence at Fermilab. See next 
  talk. 


MFCTest - Muon Fanout Card Tester Card Software - Satya Bheesette
    One of the many things Satya has done for us during his visit is write
  software for the MFCTC (see above). This card operates in a standard 
  D0 muon VME crate with an MFC and a CPU operating VxWorks. The test 
  software that Satya wrote (and is adapting as MFCTC evolves) runs in 
  a PC connecte to the crate.
    The MFCTC is to test functions of the MFC. Specifically, software is to
  test a) initialization procedures, b) memories and registers, c) different
  readout modes (requires MFCTC), d) interrupt responses (requires MFCTC),
  e) diagnostic functions, f) NVRAM management, and g) data browsers and other
  functions.
    Software environment: ethernet connection to processor, typically from
  d0ola at DAB and fasic14 at High Rise.  Exists a console port on the 
  PC through HyperTerminal for High Rise, and a dumb terminal at the 
  PDT test stand (Herman's area). MFCTest (his code) runs in VxWorks. The 
  source can be found at /RunII/home/room2/bsn/mfctest (d0mino). The 
  documentation is at \\D0server4\users\bsn\public. The code is in C and 
  cross compiled on d0mino.  It runs using simple menu driven functions,
  has no GUI's or graphics. It has a maintenance log-file option and 
  provides it's own on-line help.  (You gotta love that! -HTD). 
    Satya listed the MFCTest (software) functions.  They are extensive.
    On the to-do list: 1) testing of code for External and System readout
  modes (MFCTC hardware intensive), 2) testing of code for interrupt modes 
  (also MFCTC intensive?).  It is hard to do this from India, guys, lets
  try to get as far along on the MFCTC hardware as is possible this week!
    See previous talk.


Around the Room:
    HTD is working on EFS cabling with hardware shifters Frederic and 
  Claude. 
    ASI reports no scint runs were taken last week because of the collaboration
  meeting. He will get together with VP and HM to discuss local data-taking
  procedures.
    Bassar S. will work with Lev U. on North A-layer Octants 2 and 3. Cabling
  to continue on N EMC truss.
    Mao is testing HV for Cosmic Cap counters on EFS and EFN. EFS requires
  some Reynolds extensions from Ed Podschweit. 
    Chunhui Luo will assist Neeti on shift Monday and Tuesday.  I don't 
  think anyone is signed up for Wednesday through Friday. 
    Lev U. reports progess to occur this week on using correct (readout?)
  crate ID's and channel addresses for L3 data-taking.
    Rob Mccrosky is working on setting up minimal hardware to support 
  L1 triggers from PDT 231 and 131. This requires timing signals from an
  MCH3 crate. RM is encouraged to use own crate.
    Neeti plans to readout PDT's 231, 221, 211, 131, 121, 111 this week and
  to test the new 1553 download procedure from Fritz Bartlett. 
    Boris strongly suggests we concentrate on identifying readout errors.
  Are there any, he asks, and what is the rate? Of course we believe that 
  chasing these problems NOW should be highest commissioning priority 
  because fixes will require changes to hardware (maybe) and software.
  I agree. 
    Dave Hedin reports Examine code exists that will report crossing 
  and turn number errors but it's not in the release yet. 
    Satya reports an L2 error in scintillation counter events roughly 
  every 500th event.  (That's not good enough. -HTD). 
    Lev U. report no errors in MDT data in local data-taking mode. 
    Dave reports Fortner has put classes together for the 2-hit cosmic 
  cap counter scintillator. 
    HTD reports HH is working with Sten and installing A-layer top 
  east control cards. TM is working in MCH3, I think.  
    

[ Active News || Post a New Message || Search || Archived News || Help ]