Page History

...

• First part: EVIO to LCIO is done and merged.
• Second part: 
  • Decided to use generic collections, because the data is different from Ecal. 
  • Hodoscope Hits: Several arrays: x-index, y-index, layer and energy, and .
  • Hodoscope Clusters: Combines the hit that are in the same tile, that have dual readout.
  • Used the detector with only hodoscope and ecal and it worked. With other detector, there seems to be an issue with the conditions?
    • Needs to dig into what is happening, is this the detector file or is this the conditions?  
    • Tongtong  will run the code through the debugger, Norman will also look at this problem.
    • Issue was resolved. See SLACK: https://heavyphotonsearch.slack.com/archives/C449ZNYAV/p1560307810072900

The Readout, Tracking and L0 issue (Norman):

...

• Q: How much data is needed to do a reasonable DQM?  
  • A single data file for 2016 V0 skim. 12k events in the file, 38k clusters, 27k tracks, ~ 5k tridents. From a single 2GB data file.
  • Occupancies, etc are also available in online monitoring.
  • How many tridents do we need? Not clear.
  • We should try to do at least 1% of data for DQM, perhaps 2-5%?
    
    

Questions: 

• Norman to Rafo: What driver for the hodoscope?   
  • Rafo will post the reconstruction driver info. It needs to be added to the standard steering file.
• Kyle: For the trigger studies, needs the correct method for extending a track to the ECAL face. There isn't a cluster-track matching for the GTP clusters.
  • Norman will show Kyle where the files are and how to get going.