• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT
    Make New Entry, Make Followup Entry

    User name dalton

    Log entry time 17:20:56 on October 07, 2009

    Entry number 293698

    keyword=Hall C beam burp cut

    I am attempting to add a Hall C beam burp cut but it appears that the
    "extent" of the cut is not being handled properly.

    For example in run 13041 the database includes the following:
    # Default cuts
        lobeam    22000
        lobeamc   0.02
        burpcut   600
        cburpcut  0.03
        monsatcut 132000
        ncuts 8
        cutnames Low_beam Beam_burp Evt_seq Pair_seq Startup Mon_Saturate
    Low_beam_c C_burp
        extlo 10   10 25 25 0 30   10  10
        exthi 1200 40 25 25 0 30 1200  40
    

    But looking at the output of the pan replay, the extent of the 8th
    cut hasn't been understood. So too in the data, this cut doesn't
    extend as it should.
       Number of cuts used :  8
         Cut name  Low_beam
         Cut name  Beam_burp
         Cut name  Evt_seq
         Cut name  Pair_seq
         Cut name  Startup
         Cut name  Mon_Saturate
         Cut name  Low_beam_c
         Cut name  C_burp
       Low beam cut :  22000
       Low beam C cut :  0.02
       Burp cut :  600
       Det saturation cut :  0
       Mon saturation cut :  132000
       Hall C Burp cut :  0.03
       Position Burp Cut : 
       Energy Burp Cut : 
       Hall C Burp cut :  0.03
       Detector weights :  1 0.33 0 
       Blumi weights :  1 1 1 1 1 1 1 1 
       Flumi weights :  0 0 
       Num of (non-zero) cut extensions :  7
        cut     extlo     exthi
          0      10       1200
          1      10       40
          2      25       25
          3      25       25
          4      0       0
          5      30       30
          6      10       1200
       Number of cut intervals :  0
    


    A copy of this log entry has been emailed to: rsholmes@jlab.org, rom@jlab.org, paschke@jlab.org