Efficiency Meetings From 20-1-2017¶

Actions:

Ken:
1.Estimate what errors should be for each part of tracker recon - TBC

Ed: - No progress due to readying data taking - TBC
1. Trims vs no trims at 3T
2. 4 tesla data

Adam:
1. Add in offsets to local coordinates from CMM - Pretty sure already done
2. Regenerate bad events once offsets have been added. - So this step is by definition also done.

Melissa:
1. Straight track efficiency begin by looking by eye at failed events. -done

Paul and Melissa:
1. check local and global coordinates -Ongoing

Chris R:
1. Pat rec errors - ongoing but good progress
2. Add PRY field map from Holger into MAUS and compare with hall probes. - model obtained not sure how far along analysis and MAUS inclusion is.

Chris H:
1. Momentum study - going slowly, as working on descope. Has made a variable seed to Kalman fit, which should improve track fit.

25th Feb¶

Summary:
Straight tracks understood, DS ~1% less efficient than US due to dead channels. 2% apparent decrease is due to scattering a 1% fail the road cut (which may or may not be wise to improve).
Error analysis and propagation considered discussed and planned but not yet implemented.
Efficiency code needs to be standardized and new methods checked.
Sz and helical fits need to be looked at agian by eye and their code considered in detail.
geometry considerations are nearly complete, and we suspect that everything will be validated okay but only the end of the study will tell

Actions From 25th Jan:

Ken:
1.Estimate what errors should be for each part of tracker recon - TBC

Ed: - No progress due to readying data taking - TBC
1. Trims vs no trims at 3T
2. 4 tesla data

Paul and Adam:
1. Add in offsets to local coordinates from CMM - Pretty sure already done
2. Regenerate bad events once offsets have been added. - So this step is by definition also done.
3. Review pat rec code particularly sz.
4. return correct error propagation on pat rec.
5. add chris R correctly normalised Chi squared
6. Check number df for straights and helices
7. Check chi sq plots look right
8. Check by eye
9. Add full 3D helix fit (using external code)
10.Finalise Efficiency analysis code
11. Add an efficiency test to integration tests

Melissa:
1. Improve efficiency algorithm using original method and varify results.
2. Compare efficiency calculations for consistency
3. Consider how to implement scattering in the code
4. Analyse fully the effect of road cut.
5. Redo efficiency for all runs based on the above

Paul and Melissa:
1. check local and global coordinates - Monday

Chris R:
1. Pat rec errors
2. Add PRY field map from Holger into MAUS and compare with hall probes.

Chris H:
1. Momentum study
(2. MC - data comp)

Next Meeting January 31st at 2pm.

January 31st at 2pm.¶

Actions From 25th Feb:

Ken:
1.Estimate what errors should be for each part of tracker recon - Done

Ed: - No progress due to readying data taking - TBC
1. Trims vs no trims at 3T
2. 4 tesla data

Paul and Adam:
3. Review pat rec code particularly sz. - Ongoing
4. return correct error propagation on pat rec. - Ongoing
5. add chris R correctly normalised Chi squared - Ongoing
6. Check number df for straights and helices - TBC
7. Check chi sq plots look right
8. Check by eye
9. Add full 3D helix fit (using external code)
10.Finalise Efficiency analysis code
11. Add an efficiency test to integration tests - Paul - almost complete

Melissa:
1. Improve efficiency algorithm using original method and varify results. - ongoing
2. Compare efficiency calculations for consistency - ongoing
3. Analyse fully the effect of road cut.
4. Redo efficiency for all runs based on the above
5. Consider how to implement scattering in the code

Paul and Melissa:
1. check local and global coordinates - Monday

Chris R:
1. Pat rec errors - Done By Adam and Ken
2. Add PRY field map from Holger into MAUS and compare with hall probes. -TBC

Chris H:
1. Momentum study
(2. MC - data comp)

Paul:
Has got the efficiency code running as an integration test on data but it is not working on MC atm. He will get it to Adam by tomorrow. Needs somewhere to keep the output numbers from these tests maybe a root file.

Adam: has the error calculations and so will use these for the circle fits, sz fir and hence chisquared. He is working to get this into MAUS

Chris Hunt is looking at including multiple scattering in pat rec. He is using a Kalmanesque method to include this in the form of increased error. This will take account of chiSquared errors but will not give a track vertex track type format.
Chris R has suggested using the average energy loss across the length of tracker and average angle likewise to then pull out the uncertainties. S Hunt will look into it. This will need to be checked from data.

Chris Rogers: rerunning data with 2.7.0 and is looking at US tracks and pushing them to DS and checking. It looks much better now we have the better sz cut but still needs work.

Melissa is looking into the efficiency code differences and improving and also working to revamp her now out of date binomial efficiency code.

Next Meeting Tuesday 7th at 3.30pm. Tomorrows tracker meeting canceled.