You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Agenda:

 

  1. News, Quick Updates                                  — All
  2. Adding Pulser data to MC, take 2                — Kyle
  3. Noise in the Ecal simulation (appendix of presentation)  — Kyle
  4. Questions, Comments, Announcements      — All

Notes:

We had some excellent discussions on the limitations of each of the methods for folding pulser data into MC tridents. The proposed method of merging after the readout has a weakness in that it does not allow for an accurate simulation of the trigger. The trigger code would run over the MC data before it has the noise added. It would be very difficult to avoid this. A perfect system for folder in pulser data would require a continuous readout of the the hardware with very low readout thresholds on all channels, giving us completely unbiassed noise. Our hard ware is not capable of acquiring such data.

Jeremy told us that he could help provide the driver that would read a pulser file and then select random events from this file. He thinks this can only be done by reading the entire file into memory. This is probably possible since the files are not expected to be to huge. Jeremy promised to help create this code.

Sebouh was willing to help with creating a clean pulser data file. It would probably be sufficient to start with one setting, so from 2015 the 0.5mm pulser data at a nominal luminosity, and the same for 2016 data. He will write out a file that contains only good pulser events. The files need to have about a million events in them. We can then use this to see how well the proposed scheme works.

 

  • No labels