RICH EB DST Integration

The event builder (EB) performs four main tasks:

1. Read and organize all the detector information from upstream services
2. Associate tracks and detector responses into particle objects
3. Perform a particle identification scheme on those particle objects
4. Write those particles and their associated detector responses to DST banks

Integrating the RICH requires passing specific information between software packages, and identifying that data is key.

Inputs

• EB particles
  • as org.jlab.clas.detector.DetectorParticle objects from common-tools/clas-reco/detector
  • these contain tracks and associated hits from all detectors (except RICH currently)
  • RICH software currently reads bank EB outputs as inputs, like REC::Particle
• The RICH::tdc bank
• Event vertex and start time?

Outputs

• RICH detector responses associations for the relevant particles
  • as org.jlab.clas.detector.CherenkovResponse objects
  • for the REC::Cherenkov bank, or its future upgrade
• PID metric for the relevant particles
  • multiple hypotheses?

Potential Interfaces

• List<CherenkovResponse> getHits(DetectorParticle p, DataBank RICH::hits);
  • List<List<CherenkovResponse>> getHits(List<DetectorParticle> p, DataBank RICH::hits);
• Matrix getLikelihood(DetectorParticle p);

Notes

• RICH is in only 1 or 2 sectors of CLAS, depending on the year
• So, simple data analysis may warrant some kind of PID (masking) option