Page History

Agenda

Software priorities, slide 2

Tracking:
- Omar points out that the MC picks up conditions for the timing from run 5772, SVT does not have the timing shifts that data has, which may throw off distributions of timing.
- Bradley says there is a separate steering file to analyze the MC data, which sets the offsets to zero, so it is consistent with MC data.
- SVT has noise taken from the baseline runs, so it is close to the noise in data. Signal/Noise is very good, so this is not likely an issue anyway.
Ecal:
- Holly: Ecal hit timing is more discreet than the data, at 2 ns interval, so timing looks too nice.
- Energy has random fluctuations added, which add to the energy spread. Nathan says the electronic noise is not included but not important.
MC Geometry:
- There is a support structure for the cooling that that sticks into the active region and is not in the MC geometry. It could affect low momentum tracks.
- Ani has put a lot of effort into improving the ECal geometry so every crystal is in its surveyed position. We are NOT (yet) using this geometry. We should.
  - The parameters will need to have some global offsets added so that the ECal position overall corresponds to where the tracker thinks it is, rather than the surveys.
  - Doing this will improve the track - cluster matching across the detector.
  - This will be a new JIRA item.

Trigger Documentation:

John mentions that the trigger documentation needs to contain an up to date description of the hardware, and what it does.
Kyle will contact Ben Radyo to get this into the document.
The Trigger Sim parameters, (and the parameters that go into the simulation that feed into the trigger sim) should be better documented.

DST:

We ran out of time to properly discuss the DST. Main points:

Omar continues to oversee the DST code, any changes will first go into a branch, and if found OK, will be merged by him through a pull request.