Blog from January, 2009

Pass7 todos

This is the list of desired udpates to complete before the Pass7 merit reprocessing (currently targeted for early february)

Recon udpates

  • saturated ToT bug fix (Leon) - available from GR ?
  • energy unbiasing (Michael,Tracy, Leon working on GlastReleasing Carmelo's root macro

Additional merit variables

  • Overlay related
    • Run and event number of the overlay event
    • input overlay event trigger bits
    • number of ACD tiles hit and the energy deposited in them
    • number of CAL crystals hit and the energy in them
    • number of TKR hits
    • Fix to some existing ACD variables. Energy and tile count should be cut on ACD accept bit. This will not affect normal data, which implicitly has this cut. But the tiles in PT events are not zero-suppressed, so we currently get funny numbers when we make "Gleam-skim" PT events.
  • Mc related, to be added in the McTH tool
    • Number of daughters of the primary particle
    • Process that created the daughter particle (currently two daughters, this is a string)
      • We might also look at restructing how the daughters are handled...  right now "daughter1" is really the "best" daughter meaning the one  that produces the most McPositionHits. But we might want to change to  straight order so that if an incident gamma compton scatters first  then we have the compton electorn as the first daughter.
    • Position of the creation point of the daughter (currently two)
    • Initial direction of the daughter (four momentum? curren tly two)
    • Number of McIntegratingHits associated to the primary particle
    • Energy deposited due to McIntegratingHits associated to primary
  • cluster tagging variables (e.g. TkrNumWideClusters) - use GR > v15r53p2.  Done
  • ToT255 bug fix (Leon) - GR ?  Done
  • Lambda magnetic coordinate (JFO definition) - needs implementation in GR  Done
    • Ditto: signing PtMagLat and adding R and B field components  Done
  • Deadtime - needs definition and implementation in GR  Done
  • Rocking angle (JFO+Seth definition) - needs implementation in GR, will be non-backward compatible  Done

Worksheet

  • proton and HI cuts - need defs from Markus, Simona, Maria-Elena need; Carmelo to implement in worksheet
  • separate vetos for P6 leakages - Carmelo to add HI veto from Simona and low energy CAL evts from Riccardo
  • consistent definitions of CTBParticleType and CTBClassLevel over all worksheet

Sundry items

  • physics trigger cuts in IRF
  • Should we use Hiro's new TKR gain constants for Pass7? (and does this imply that we should also use them for generating the PT overlay events now?)

Reason for change

The new version (v5r9p1, as opposed to v5r9p0, previously running in L1Proc 1.70) includes a few more exceptions on TKR hot strips.
The detailed description of the changes is in the last section.

Test Procedure

We have processed monitoring products from real on-orbit data (LPA) locally with this version of AlarmsCfg.

Rollback procedure

The package can be rolled back to the previous version by flipping a soft link. Also note that the package is completely independent from any other package running in the pipeline and will not cause a version change of L1Proc.

CCB Jira

SSC-175@JIRA

Details

v5r9p1

  • Added an exception for tower5, layer 32 in tkrmontrend, alarm Number_layerOcc_TowerPlane.
  • Limits chenged for alarm x_average TkrPlanesHit_TH1_Tower_3. Before tower 0 was handled separately with the low limits slightly lower than all
    the other towers, not tower 3 is treated exactly like 0.
  • Added exception in fastmon_eor, alarm spikes_and_holes on TkrHitsCounter_PlaneGTFE_TH2_Tower_5 for layer 32, GTFE 3.

Reason for change

Added MicroQuasars data; it includes folder in navigation tree and plots when available.

Test Procedure

It has been tested on the test server.

Rollback procedure

Version 0.3.1 can be put back in place.

CCB Jira

SSC-172@JIRA

Details

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Reason for change

The new version (v5r9p0, as opposed to v5r8p8, previously running in L1Proc 1.70) include a very minor change, namely two more exceptions to the calorimeter pedestal alarms.
The detailed description of the changes is in the last section.

Test Procedure

We have processed monitoring products from real on-orbit data (LPA) locally with this version of AlarmsCfg.

Rollback procedure

The package can be rolled back to the previous version by flipping a soft link. Also note that the package is completely independent from any other package running in the pipeline and will not cause a version change of L1Proc.

CCB Jira

SSC-173@JIRA

Details

v5r9p0

  • Added a couple more exception on CAL ped rms values, channel 848.

We should normalize the calibration used in offline and configuration building to the best values from L&EO

 The input files are listed below, along with the various reports

Base path is $LATMonRoot/ACD/FLIGHT aka                                        
/afs/slac.stanford.edu/g/glast/ground/releases/monitor/ACD/FLIGHT              

In each case read                                                              
type_of_calib:         flavor_or_alias         path                            
FlavorPed:                vanilla                  Ped/081208/r0250381744_ped.xml           
FlavorGain:               vanilla                 ElecGain/081208/r0250381744_gain.xml
FlavorHighRange:      vanilla                HighRange/081208/hr_081208_highRange.xml
FlavorCoherentNoise: vanilla               CoherentNoise/081208/r0250381744_coherentNoise.xml

Various reports:
Pedestals                                                               
MIP peaks                                                             
High range calibration                                                      
Coherent Noise Calibration