[Nicolò]

• Data reprocessing: code almost ready to recover a fraction of missing FERS events, using dT based on tracker hardware (see inefficiency plot, slide 6)
  • Looking for spills in FERS and XDCs leaves with empty FERS events in the last 3/4 fills
  • Such inefficiency accounts for up to ~25% in (not many, and typically short) runs
  • Using time interval between consecutive events may work, but system clock used to tag XDC events has very poor resolution
  • Hardware 2.5 MHz clock from tracker can be used instead .. and it seems to work well