Project

General

Profile

Actions

Meeting 6-1-2017

Minutes:
Ed looked at chi squared fit for sz and circle cuts, using all tracks that passed and no cuts. The results look funky. See talk attached.
He looked through Adams failed event file and examined a few events by eye. Several look as though they ought to have passed (see attached). Need to understand.
Paul looked at the same events by eye and agrees.

Need to compare trim on and off data as well as 4 T data.

There is some concern that the tracker local to global coordinates are handled correctly. Melissa and Paul to investigate.

Chris R has calculated a 10mrad error will exist through MAUS reconstruction meaning that scattering may be hidden. This is just a result of the physics of the system we have and hence is the best that MAUS can get. US Some checks of his calculations are necessary.

Need to explore tracker to TOF backtracking.

11th January Meeting
Ed has added an error to his previous data and we need to understand what it should be and set appropriate value.

Adam has a version of the code that makes plots before cuts are made in MAUS and Ken would like this implemented in the next MAUS release and to have it available for now by some method.

Need to include offsets in local coordinates

Actions:

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

Ed:
1. Trims vs no trims at 3T
2. 4 tesla data

Adam:
1. Can we make plots before cuts in MAUS and implement. YES Adam has a version of the code that can do this, make this available
2. Add in offsets to local coordinates from CMM
3. Regenerate bad events once offsets have been added.
4. Make a data set of only good tracks.

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

Paul and Melissa:
1. check local and global coordinates

Chris R:
1. BDL for record - work going well but more to do
2. Check positions

Chris H:
1. Momentum study

NEXT MEETING: weds 11th at 10.30am

MON 16th Jan Meeting
Actions:

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

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

Adam:
1. Can we make plots before cuts in MAUS and implement. YES Adam has a version of the code that can do this, make this available - DONE available and sent.
2. Add in offsets to local coordinates from CMM - TBD
3. Regenerate bad events once offsets have been added. -TBD
4. Make a data set of only good tracks. - DONE http://www.hep.ph.ic.ac.uk/~adobbs/Files/maus_output_5pt_tracks_08681.root

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

Paul and Melissa:
1. check local and global coordinates

Chris R:
1. BDL for record
2. Check positions

Hall probe positions were corrected according to the new positions provided by Melissa now agress with MAUS to a systematic offset. Field map obtained from Holger and will be included.

Chris H:
1. Momentum study
Work going well. Two corrections to tackle: PR seed correction and fitted track correction.
The PR seed correction has been addressed with a reducer, and a script to use it, to generate a set of linear corrections for the PR seeds.
The PR mapper has been edited to account for the corrections and apply them to the PR tracks.
Documentation is still required but a branch is ready to merge this week.

Actions:

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

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

Adam:
1. Add in offsets to local coordinates from CMM
2. Regenerate bad events once offsets have been added.

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

Paul and Melissa:
1. check local and global coordinates

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

Chris H:
1. Momentum study

Updated by Hunt, Christopher over 6 years ago ยท 10 revisions