more of BRAHMS magnet data updated in RUNDB

From: Konstantin Olchanski (olchansk@ux1.phy.bnl.gov)
Date: Wed Oct 11 2000 - 18:51:13 EDT

  • Next message: Konstantin Olchanski: "Trigger scaledowns stored in run database"

    Here is the latest status:
    
    0) brief CDEV readout history:
       -  1 Aug 2000, run ~2002, Started. Occasionally, data goes stale.
       - 21 Aug 2000, run ~2371, Read the polarity (A/B versus +/-).
       - 23 Aug 2000, run ~2404, RHIC fixed CDEV bug that caused stale data.
       - 31 Aug 2000, run  2492, CDEV readout did not restart after an opus crash
       -  3 Sep 2000, run  2525, CDEV readout restarted.
       -  7 Sep 2000, run  2552, last run with beam.
       - 11 Sep 2000, run >2552, CDEV readout did not restart after an opus crash.
    
    1) The run database was manually corrected to conform with CDEV data,
       with exceptions:
    
    2) Currently known discrepancies between current run
       database (after corrections) and CDEV:
    
       - run 2286, CDEV reports D1 and D2 changing state (off->on)
         in the middle of the run. Run database entries left "undefined"
         for these two magnets. D5 is off (both CDEV and log book agree on this).
       - runs 2355 through 2377. CDEV reports D1 and D2 on, database- off.
       - run 2378, CDEV had read errors, magnet status unknown. This is a debug
         run not sent to HPSS.
       - runs 2388 through 2401, D5 polarity is unknown.
       - runs 2402 through 2411, D5 polarity is known to be "B",
         CDEV reports "A". Database has the correct "B" polarity.
       - runs 2412, 2413, D1 and D2 state unknown. CDEV claims "on",
         database claims "off".
       - run 2418, D1 and D2 cycled in the middle of the run (run down, then up).
       - runs 2433 through 2442, D1 status suspect: CDEV reports "off",
         database claims "on". D2 is on, D5 is on.
       - runs 2437 through 2439, D5 flield is "700/A" in CDEV, "350/A"
         in database. CDEV data is supposed to be reliable in these runs.
       - run 2445, D4 turned on in the middle of the run.
       - runs 2459 through 2462, CDEV: all magnets are off, database: D1, D2, D5
         are on. These are debug runs.
       - run 2468, D1, D2 and D5 turned on in the middle of the run.
       - run 2469, database claims all magnets are off. CDEV claims D1, D2, D5
         are on (turned on during run 2468).
       - runs 2472 through 2487, D3 and D4 are on, database claims they are off.
       - run 2486, D1 and D2 cycled in the middle of the run (turned off, then on).
       - runs 2496, 2497, pedestal runs. Magnets are on, database claims off.
       - runs 2498 through 2525, D5 polarity mismatch: CDEV is "A", while
         database shows "B". CDEV is incorrect- readout was not running.
       - runs 2526, D1, D2, D3, D4 wrong polarity.
    
    3) discrepancies with data from Flemming (log book?):
    
       - on Aug 18th, D1=520/? (same on db), D2=410/? (same in db),
         D5=350/?, while CDEV shows 700/A. These are runs 2337 through 2348.
    
       - run 2337 D5=350/B. cdev shows 700/A (stale data?).
       - run 2289 D5=700/B. cdev shows 700/A (stale data?).
       - run 2286 D5=0. cdev shows 700/A (state data?).
       - run 2278 D5=350/?. cdev shows 700/A (stale data?).
       - on Aug 14th, D1=520/A, D2=410/A, D5=700/A. cdev shows D5=0 for most
         of the day. Runs 2239 through 2250.
    
    K.O.
    
    
    On Mon, Oct 09, 2000 at 12:20:44PM -0400, Flemming Videbaek wrote:
    > Inspection of the log book reveals that on August 14, 2000 the setting were
    > clearly marked
    > as D1 520A  A
    >     D2  409A  A
    >     D5  700A  A
    > with the second A in a seperate column.
    > 
    > Though at run 2278 the notebook clearly says field changed to 350 for D5 but
    > not reflected in cdev
    > readout ?.
    > 2286 correctly say B=0
    > 2289 say change to -4KG  700.03 A
    > 
    > Again run2337 says change to -2KG  B polarity
    > Book#4 page 116
    > On 8/18 the log has a specific readoutof D1,D2,D5 - 520,409 and 350
    > 
    > Thus I conclude the confusion is great.. The field OFF runs seems recorded
    > right (at kleast in some places)
    > but the +- and change from 700->350 seems quite confused even during the
    > runs 22.. -23 .. that are still
    > important dataruns.
    > 
    > Flemming
    > 
    > 
    > >
    > >
    > > Please note that the BRAHMS Magnet settings data (D1, D2 and D5)
    > > for runs 2031 through 2418 (3 - 23 of August 2000) has been updated
    > > in the run database.
    > >
    > > The updated data can be seen in the usual web reports at
    > > http://pii3.brahms.bnl.gov/daq-cgi-bin/cgiRunSummary.perl
    > > linked from the main daq page at http://pii3.brahms.bnl.gov/~daq.
    > >
    > > Starting from run 2418, the magnet data has been entered by the operators
    > > from the "begin run" dialog. These database entries were not changed.
    > >
    > > For runs before run 2418, some magnet data is available from my archive
    > > of CDEV data. These data were manually entered into the run database
    > > with the following caveats:
    > >
    > > - D3 and D4 were marked "off" for all runs between run 2185 and run 2417.
    > >   As I understand these two magnets were not operational at the time
    > >   and were actually locked out.
    > >
    > > - for runs before run 2411, the polarities are "+" and "-" instead of
    > >   the normal "A" and "B". At this time I do not know which is which
    > >   (Polarity "+" is "A" or "B"?), but this will be looked into and the
    > >   database will be updated when I know the answer. Expect "+" and "-"
    > >   to disappear.
    > >
    > > - a number of instances were found where the magnet settings appear to
    > >   have changed during a run.
    > >
    > >   Sometimes the magnet settings changed within a few
    > >   minutes of starting or ending a run. This has been chalked off as
    > >   operator sequencing mistakes and the database will show the magnet
    > >   settings used during the duration of the run.
    > >
    > >   Sometimes the settings appear to change smack in the middle of the run
    > >   and the corresponding database entries were left blank (i.e. run 2378).
    > >   From available CDEV data, it is not clear if the magnet setting change
    > >   was real (operator forgot to start a new run while turning the magnet
    > >   on or off), benign (RHIC went down, the operators turned down the
    > magnets
    > >   but forgot to end the run. Benign because no data were taken with the
    > >   wrong fields), or a CDEV readout malfunction (and I see quite a few of
    > >   them, for example, CDEV data for runs 2387 through 2413 contains mostly
    > >   errors).
    > >
    > > - CDEV magnet data starts at run 2022 and until run 2185 all magnets
    > >   appear to be always off (except for D1 in runs 2031 and 2032). I would
    > >   like somebody (Dana?) to confirm when the first magnets were first
    > >   turned on (when the water system was turned on?) before
    > >   I put this into the database.
    > >
    > >
    > > --
    > > Konstantin Olchanski
    > > Physics Department, Brookhaven National Laboratory, Long Island, New York
    > > olchansk@bnl.gov
    > >
    > 
    
    -- 
    Konstantin Olchanski
    Physics Department, Brookhaven National Laboratory, Long Island, New York
    olchansk@bnl.gov
    



    This archive was generated by hypermail 2b29 : Wed Oct 11 2000 - 18:51:56 EDT