DØ Central Fiber Tracker

Level 1 Trigger

Readout to Level 3 How-To


A brief description of how to start a run and dump data from the L1CTT VRB crate.
  • log on to d0ol08; you might want more than one window.
  • setup d0online.
  • setup onl_apps.
  • optional: check presence and/or contents of /online/ioc/ppc/mv2304/d0olctt00/d0olctt00.dbg;
    Should this need editing (configuration change),
    • edit and remake the EPICS database:
      • edit /online/ioc/ppc/mv2304/d0olctt00/d0olctt00.dbg with your favourite editor (e.g. emacs -f tpu-edt & ).
      • setup onl_ioc.
      • gmake install.
    • reboot the processor to force a database reload:
      • telnet to t-d0-mch3.
      • login (as 'ioc' ).
      • connect 15.
      • ctrl_x (or was it ctrl_y ?)(any key during the 1st second after this should bring up the boot prompt; type e.g.'p' for a list of boot parameters).
      • after booting, 'dbl' will list all records in the database .
      • 'ctrl_]' to disconnect from the PowerPC and return to telnet.
      • 'close' to exit telnet.
  • in /home/d0cft/commiss/comics_l1ctt, execute L1cttLoad.py ('python L1cttLoad.py').
    This file controls hardware settings (which VRBs are present, are they in emulation or real data mode, etc.), except for the channel control (1 VRB has eight channels (in D0 mode and D0 trigger mode)), which is done by the pickle file in the /pickle subdirectory. To change channel on/off settings, edit write_pickle.py, and execute it prior to running L1cttLoad.
  • optional: in /online/data/coor/configurations/commissioning/l1ctt, check existence of l1ctt-zero-bias-1.0.xml (or whatever other trigger you want to run with).
  • start a taker ('taker') .
    • in the taker, 'Modify' -> 'Change Trigger'.
    • commissioning/ -> l1ctt/ -> l1ctt-zero-bias-1.0 ; this triggers the download
    • if the download has errors, repeat; if everything's ok so far, proceed to:
    • start the run.
  • start coormon: 'coormon'
  • start daq monitor: 'start_daq_monitor_display'.
    • check that your trigger is running (on L1 page).
    • find the data buffer directory corresponding to your run number (on the datalogger page).
  • check that your are getting any good events at all: open http://d0l3dev.fnal.gov/monitor/ETGSB_display.asp .
    • In the table 'events by trigger bit', find your trigger bit, check whether there are any complete events. (The trigger bit can be found in the output of the taker 'start' procedure; you can also identify it by looking at the 'crates mapped' section of the web page you just opened, and searching for a trigger with crates x13 and x1F).
    • If there are incomplete events for your trigger, check the table 'Times crates have gone missing (hex crate IDs)' for crate x13 (row 'Trigger Ox1', column '3') and crate x1F.
  • open a window on d0olc for data buffer dumping:
    • ssh d0olc.
    • cd /buffer/yourbuffername.
    • dsdump --raw --byteswap yourfilename | less             (using byteswap on d0olc arranges longwords such that the MSB is in the leftmost position, and VBD and VRB headers appear just as printed in the manuals.
    • check the second 32-bit word of the VBD header for the L1CTT crate id '13' in the LSB (refer to the VBD manual , page 15 for the header format).
    • find the first VRB, check the total byte count (first word); use that to find the next one, etc. .
    • for the VRBs present, check the channel word counts (see the VRB manual , page 34, for the VRB header definition).
  • still missing: the mystery of the blinking lights; whom to call if a VRBC turns all its lights off; etc. .
module/system expert phone email
DAQ problems DAQ shifter 8800
scripts, general questions Thomas Nunnemann nunne@fnal.gov
VRBC Daniel Mendoza 4114, 5199 mendoza@fnal.gov
VBD, VRC, other L3 try DAQ shifter first, then:
Sean Mattingly 5266 sean@fnal.gov
Andy Haas
Douglas Chapin 5266 dpchapin@fnal.gov
VRB Mark Bowden (CD/ESE) consult local expertise first
VTM Bill Haynes (CD/ESE) consult local expertise first

 

 

Last modified September 20, 2001, by SG.
Please send questions or comments to Stefan Grünendahl (Stefan@fnal.gov).