Return-Path: Sender: dsl@stanford.edu Date: Sun, 29 Jul 2001 00:20:07 -0700 From: Dave Lauben X-Accept-Language: en To: Heather Kelly , Dan Wood , djt@egret.gsfc.nasa.gov, scott@razzle.Stanford.EDU, Bob Schaefer Subject: bfem NSBF pre-ship and post-ship event files Heather, I've just now uploaded six 10-minute run Bfem event files to: /nfs/farm/g/glast/bfem/data/evt/. The first three were taken before shipping to NSBF: -rw-rw-rw- 1 balloon other 20949740 Jul 21 09:21 0995718299_0000.evt -rw-rw-rw- 1 balloon other 20071040 Jul 21 09:25 0995718899_0000.evt -rw-rw-rw- 1 balloon other 20344724 Jul 21 09:30 0995719499_0000.evt The second three upon arrival at NSBF: -rw-rw-rw- 1 balloon other 19779560 Jul 27 18:35 0996271259_0000.evt -rw-rw-rw- 1 balloon other 19531836 Jul 27 18:38 0996271859_0000.evt -rw-rw-rw- 1 balloon other 19625244 Jul 27 18:42 0996272459_0000.evt [Note: These listings are on the Sun Gse; on the Slac Farm they will have Jul 28 dates and be owned by dsl. Pls. check sizes.] The Bfem was in nominal configuration (upright, tracker 3-in-row trig config 0). However, as Bob's note mentions, we already know that one Acd channel (Ritz #310) shows intermitent pedestal rise in the second set of three files. Bob's note regarding the new Acd channel which fixes this problem will apply to future files. Nonetheless all six should be converted to root and inspected for other anomolies, in a "before/after" sense. In other words, are there any significant changes in Bfem characterstics between the first set of three and the second set of three? If you need more specific info about the config, I'll have to refer you to Dave T. or Dan W., who can best interpret the log book entries for these particular files. Regards, -Dave.