To understand next...

500 files of each MC flavor are now done.  Next items of business are:

1. get raw and accepted vertices to Megan.  She will begin with the raw 1.0 files, import as a pandas dataframe.  Then she'll combine the "raw 2.0" vertices (raw, but with primary [and secondary] vertices corrected).  THEN, she'll correlate raw vertices with accepted vertices.

2. Would be good to find a way for DSelector to output ONLY the TRUTH track permutation so that we can check vertexing.  Not sure if this would be a good approach for training NNs, too.

UPDATE: There is a Get_IsTrueCombo() member of ParticleCombo, but it doesn't work for displaced vertices (see google group).  Instead, it looks like I can check each charged particle hypothesis' thrown particle index.  What I should do is add another branch to the output tree that is a boolean of whether the thrown topo is matched.

3. Need to understand how vertexing works.  Does the kinematic fitter try to match the p mu- vertex with the Lambda flight path from the primary vertex?  If so, this might NOT be helpful, as it could make fastpi events look too much like sl_mu events.  So, can we access the pre-KF Lambda vertex in DSelector?  Vertexing happens at hd_root time, right?  Call Simon?

4.  Would be good to include detector information (timing, dEdx, etc) in the data stream that goes into NNs.  Find out how to do this in DSelector.

5. Look for conferences next year, and get Megan and Kripa on track for a poster presentation.