sPHENIX HCal discussion

[pinkenburg <pinkenburg AT bnl.gov>]

    Hi Justin,
    
    before this becomes a gospel - the 2 hours for event building and
    availability of "seconds worth of data" is a guess. There are
    technical considerations which might cause significant longer times.
    E.g. one would have to run a lot of short jobs in sdcc which is not
    made for this. We have limited cpu's,  setting a large enough number
    aside to run this might impact our capability to process enough
    events through our fixed latency reconstruction. I would rather have
    some statements what is needed and some justification (what would
    you do with this information 2 hours after the run has ended? How
    does this affect the data taking compared to having this information
    from a regular q/a pass? Is 2 seconds out of 3600 seconds a
    reasonable sample to base any data taking affecting decision on?
    
    We need an estimate of the number of events required.  The number of
    events needed for e.g. full tower slope fits just exceeds what can
    reasonable be done as a fast check based on a few seconds worth of
    data. Keep in mind the 100Hz we saw in PHENIX (together with the
    fact that only few online monitoring codes actually managed to run
    at that speed), we will likely be better off now but the processing
    time of the monitoring code will make sure you will not get that
    many events (compared to the daq rate).
    
    Chris

On 7/18/2022 9:03 AM, Frantz, Justin via sPHENIX-HCal-l wrote:

        Hi Hcal'ers,
      
        
      
      
        I think a few of the hcal management folks have expressed that
        what I presented last week at the calo calibrations meeting for
        both calos seemed reasonable enough for the Hcal as well, with a
        few exceptions.   Since then there have been some further
        evolution at DAQ mtg and EMcal mtgs I wanted to share, plus just
        give an overall rundown so that we can  come to a consensus at
        tomorrow's calo calib mtg (10:30am), and then present that
        consensus at the Software meeting (which I can do but I would
        welcome any Hcal'er that is interesting in taking the lead on
        this to feel free to become involved even in what we present).  
      
        
      
      
        The main new developement was that it was determined that it
        will indeed be too difficult  to put markers to directly
        identify LED events, so we should plan not to have those.   For
        EMCal it is presumed (although since John Haggerty was on
        vacation, there might not be FINAL confirmation on the possible
        LED firing patterns) that we can probably still identify LED
        events because "ALL"  towers in a ~sector will be fired during
        them.  For Hcal is it possible very central events might  have a
        decent probability of firing all 1500 towers in one event? which
        may hamper-- simply from multiplicity it seems possible... 
        (couple thousand particles per event in most central).   We
        should probably determine this rate, if anyone has data to
        confirm and measure the rate, I can check it in MDC2 Hijing
        maybe not by tomorrow.    Anyway, it's not necessarily that
        important to identify the LED events, I think the verdict is
        still out on that, and we will probably try to as much as
        possible, but we already also seem to have agreed on the other
        fast feedback monitoring methods TOO,  like rolling average hits
        per tower  ie  a map of this, that can serve to probe similar
        info.
      
        
      
      
        So here is the current list of monitoring items (please comment
        or bring discussion to calo mtg tomorrow morning)  the things
        I've highlighted in red are unique for the Hcal, the other items
        are also envisioned for EMcal (e.g. could use common code)
      
        
      
      
        Shift crew :
      
        --------------------
      
        -like emcal monitoring in PHENIX
      
        -2D Channel map (summative info based on below)
      
             -Tower hits /event   per tower based on rolling averges
      
             -Tower energy mean
          (or eqiuv) per tower (rolling avg)
      
      
                  (whole spectra
          per sector?)
      
             -PIN diode data if in data stream?
      
      
              -whatever can be
          gathered from LED events if ID-able
      
              -temperatures,
            leakage currents, etc... ?   
        
      
              -timing t0 check per
            channel
      
         -text with out lying channel warnings
      
        -total global energy
            in each (I&O) whole system per event
      
        
      
      
        Expert  (Onl Mon based)
      
        -----------------------
      
        -mean pedestal for all towers (e.g. 2D map display) from peak
        extraction
      
        -individual 2D Channel maps of above quantities
      
        -Tower slope gain
          drift check per channel (? TBD)
      
        -temperature ,
          leakage currents, etc. NOT here
      
      
        
        
      
        Separate gui --
          Expert/ possibly some for "Voltage Operation Shifter" 
      
      
        ------------------------
      
        -temperature, leakage currents, etc.  from database.
      
        
      
      
        
      
      
        With event-built events on SDCC fast reco pass (~2 hrs delay)
      
        --------------------------
      
        -Total ALL-calo energy per event
      
        -Full tower slope fits
      
        -Calibration items

 ----------------------------------------------  Justin Frantz, Ph. D.  he  RHIC UEC/Diversity Working Group  Brookhaven National Lab, sPHENIX Experiment  Associate Professor  Ohio University Dept. Of Physics and Astronomy     frantz AT ohio.edu     646-228-2539    PERSONAL ZOOM MEETING:  369-910-7530   Password:  1    https://us02web.zoom.us/j/3699107530?pwd=TkZLeU1MY2d5eUpqeTJ5WUJTRHlVUT09  

_______________________________________________
sPHENIX-HCal-l mailing list
sPHENIX-HCal-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/sphenix-hcal-l
    
    
-- 
*************************************************************

Christopher H. Pinkenburg	;    pinkenburg AT bnl.gov
				;    http://www.phenix.bnl.gov/~pinkenbu

Brookhaven National Laboratory	;    phone: (631) 344-5692
Physics Department Bldg 510 C	;    fax:   (631) 344-3253
Upton, NY 11973-5000

*************************************************************