sPHENIX HCal discussion

[Martin Purschke <purschke AT bnl.gov>]

John, all,

That's great. I guess there is a master spreadsheet somewhere?

Let me add some timeline about what "environmental data" we are logging
right now, and what was added when.

Just for everyone's info, I already explained that we log most of the
SiPM controller board parameters for each run. This is largely for
forensics in case something doesn't look right, but who knows. There are
quite a number of packets in the begin-run in the 950/60/70/80 series,
and 1050/60/70/80 ranges in normal events every 2 minutes. We also log
pictures of the setup from 4 cameras/vantage points in each begin-run.

With the 2006...2016 "nose down" runs which were taken Sunday evening,
we unfortunately missed out on a feature b/c I learned only on Monday
how to get at and log the data from the accelerator - the equivalent of
RHIC's "cdev" data.

As of Monday noon-ish, starting with run 2035, we log those data, which
contain the energy, scaler values, the EmCal table horizontal and
verical positions, the temperature and humidity in the EmCal enclosure,
and the Cherenkov pressures.

> S:MTNRG  = -8     GeV 
> F:MT6SC1 =  10265     Cnts
> F:MT6SC2 =  8691      Cnts
> F:MT6SC3 =  6537      Cnts
> F:MT6SC4 =  0         Cnts
> F:MT6SC5 =  76466     Cnts
> E:2CH    =  1063  mm  
> E:2CV    =  130.9 mm  
> E:2CMT6T =  72.91 F   
> E:2CMT6H =  29.93 %Hum
> F:MT5CP2 =  .0183 Psia
> F:MT6CP2 =  .7248 Psia

These values are contained in begin-run packet 910 as text, and 911 as
directly accessible numbers. I will retroactively fill them into the
database so we have easier access to them.

The scalers in the begrun are not particularly useful because the run
starts when it starts. I later cobbled together a small board that feeds
the end of spill signal into a computer so we can capture the data from
each spill. We log the same set of values after each spill in packet
1110 (text) and 1111 (numbers). This starts as of Run 2046 (about 10pm
Monday).

It is unlikely that we will use the scalers for any kind of
spill-intensity corrections (although one never knows). The most useful
aspect I see is that it allows us to catch an inadvertent change in beam
energy or any other parameter throughout a run (Tom is logging the same
data in his DAQ and that has saved him a lot of trouble). An inadvertent
change during a run triggers a warning in the onl. monitoring and can be
caught later offline as well.

Also as of Run 2046 we log the SiPM controller boards' "GR" (0 and 1)
parameters (I'm drawing a blank what those mean exactly). They were left
out initially.

Finally, as of run 2053 (11;30pm Monday) we added the Emcal "A0"
parameter which tells if the emcal gain setting was normal or high.


        Martin


On 4/12/16 23:27, John Haggerty wrote:
> Due to the efforts of many people both here at Fermilab and at many
> sPHENIX institutions, the beam tests of the calorimeters is moving along
> well along the plan.  The ORC was signed off by the laboratory on Friday
> evening, and we were triggering and timed in that night and since then
> have been studying the detector and taking the data we came for.  We
> have come a long way in four days, and I count 80 shifts to go.
> 
> One lesson from last time is to maintain a list of the best runs we take
> while we take them.  Although we have been pretty good about recording
> things in the elog, you know the most about the runs around teh time you
> take them, so I have attached what I think are the runs that are worth
> looking at.  Additions?  Comments?  Questions?
> 
> 
> 
> _______________________________________________
> Sphenix-emcal-l mailing list
> Sphenix-emcal-l AT lists.bnl.gov
> https://lists.bnl.gov/mailman/listinfo/sphenix-emcal-l
> 


-- 
Martin L. Purschke, Ph.D.        ;   purschke AT bnl.gov
                                 ;   http://www.phenix.bnl.gov/~purschke
                                 ;
Brookhaven National Laboratory   ;   phone: +1-631-344-5244
Physics Department Bldg 510 C    ;   fax:   +1-631-344-3253
Upton, NY 11973-5000             ;   skype: mpurschke
-----------------------------------------------------------------------