Page History

...

1. Topics for Collaboration Meeting                                               – All
2. Update on Integration Tests                                                      — Norman
3. Quick project checking/update (time permitting)                        — All
4. Questions?                                                                                 — All

Notes:

Collaboration Meeting. - Software Talks:

1. Overview                                                        – Maurik
2. Machine Learning & HPS                               – Kyle
3. Summary of changes to the Tracking Code   – Miriam and/or Norman

...

2. Data Processing Update    (10 - 15 min)       –  Rafo
3. Relevant changes in MC                                – Bradley
4. Simulation:                      – Jeremy
   1. Infrastructure tools.   (15)
   2. A SLIC replacement. (25)

Norman - Integration tests - good progress, pull request forthcoming.

Miriam – Track states

• Track states only have a few entries for storing information. Missing:
  • Track position at the sensor. 
  • This could go into the reference points, but then ref. point is not origin.
• So what to do?
  • We can store the track position in the reference point, but then all the other objects of the track state need to be made self consistent. This would require a set of transformation if you then want to use say, d0. etc.
    • GBL already has all the info, we just need to decide which one to store.
  • We cannot extend the object, so we can do LCrelations and add the info in another object. Doesn't seem so great.

Miriam - 3D hits from Hole+Slot strip hit combinations – Issue 57 -Pull request: 219

• Switch to turn this on/off.
• This is in the HelicalTrackHit driver.
• HSMap contains list of slot - hole combinations.
• Small increase in the number of hits identified with this new method, order 1%of all hits in data. 
• Should discuss if this should be part of production – Discuss in Tracking Meeting.

Pull Requests:

Norman will review:

• Iss146  – Seems ready for merge.
• Issue 126  – Miriam's rabbit hole. 
• Issue 135 – Miriam - currently produces same results as current Master, but allows for more flexibility to later introduce new 

Comment: There is some overlap with the tests done here and those we want for DQM, but the overlap is not perfect. It would make sense to have some plots in common.

Comment: The tests should run with the Jenkins build, so they will actually run regularly. To do this, the tests cannot take too long, but we still need enough events to make sure the output is useful. The time that the test takes is part of the useful output, but this needs to be normalized to the speed of the system.