...
- Pedestals output to XML
- MIP Peak values output to XML
To Do
- Create AcdCalibSvc building off of Joanne's Calibration infrastructure which initially will serve the creation of AcdHits in AcdRecon.
- Consider further necessary calibrations: VETO settings, ribbon light attenuation, loss near tile edges...
- CNO calibration
Reconstruction
Considers all ACD detectors present in the AcdDigiCol, irrespective of the setting of the veto discriminator (hit map bit). This has been confirmed with Bill who explains that we are interested in background rejection at this level and desire to utilize all information available.
Status
- AcdTkrIntersection
Projection of each track returned by TkrRecon to the ACD tile expected to be hit (whether or not a hit was registered in the AcdDigiCol) - AcdHit collection
AcdDigis with added an additional piece of data: calibrated MIP values per PMT - AcdPoca (Point of Closest Approach)
Eric's talk from Dec 16 2005
...
- Update Active Distance calculations to handle updates to the geometry, include curvature of the top tiles.ACD
- Extend AcdTkrIntersection to utilize a proximity map to determine "near" hits
- Add Ribbon DOCA to AcdValTools
utilize list of track intersections and knowledge of geometry for calculations in AnaTup Calibration Service
Seem to be questions revolving around what gets stored and where. - Remove old DOCA and original Active Distance calculations and their ntuple entries.
What does this mean? We will eliminate the following summary ntuple variables: AcdDoca, AcdDocaTileEnergy, AcdGammaDoca and their siblings located in the recon.root files. - Add TkrIntersection quantities to the summary ntuple
Suggested names?
Should check that what has propagated into SVAC ntuple has a cousin in the summary ntuple if desired. - Update Ribbon Active Distance calculation
Currently views ribbons as lines
...
- Add a series of ACD specific systests to exercise the geometry, digitization and reconstruction.
Already received a few ideas from Bill.
Illuminate top/sides with patch sources to check location of gaps in the simulated geometry.
Similar sources could be used to show how well the digitization algorithms are working.
We need these benchmarks in place before serious updates to the digitization code begins.
...