h1. PC19082015

Wednesday 19th August 2015 at 15:00 BST

Room CR09 RAL

{{>toc}}

h2. Summary of Actions

* *ACTION*: Look into TRefArray limits (*A. Dobbs*)

* *ACTION*: Optimize residuals for final tracks (*C. Hunt*) - _Done for straights_

* *ACTION*: Get detector output in global coordinate system (*C. Heidt, C. Hunt*)

* *ACTION*: Fix close to paraxial tracks producing nan output (*C. Hunt*)

* *ACTION*: Update tracker online plots (*M. Uchida*)

* *ACTION*: Update tracker schedule (*P. Kyberd*)

* *ACTION*: Update ConfigurationDefaults with tracker optimum parameters (*P. Kyberd*)

* *ACTION*: Set HelicalPR on or off depending on CDB value of magnetic field (*C. Hunt*)

* *ACTION*: Restructure TOF Digitisation and incorporate MapCppTrigger (*D. Rajaram*)

* *ACTION*: Make current beamline geometry available in CDB (*R. Bayes*)

* *ACTION*: Implement dE/dx in Runge-Kutta (*M. Uchida*)

* *ACTION*: Need C++ Reducer example (*A. Dobbs*)

h2. Agenda

h3. Release status

* Current release = 1.0.0

* Targets for release 1.0.1:

** execute_against_data.py should be always make a tarball

** Support for gcc 4.9

* Targets for future release:

** Trigger MC

** Fix memory leaks

** Tracker -- Kalman updates

h3. Schedule

* attachment:2015-08-19_MAUS-Schedule.ods

h3. Detectors

* Detector integration (D. Rajaram)

** Reconstruction quality flags (*A. Dobbs* to make requests to detector groups) #1585

* Tracker (P. Kyberd)

** *PRIORITY INTERRUPT* C. Hunt email 18-08-2015:

_"After a lot of playing around, and seeing how the tracker reconstruction correlates to the TOF reconstruction, it seems that the output from the track reconstruction is incorrect and requires a rotation of 120 degrees and a sign flip to correct it.  If you sit and think for a while you can justify this as being the result of the planes being in the wrong order. However as the data is not specifically sensitive to the plane ordering it could be one of 3 things:

- Construction differs to design

- Recon geometry differs to construction

- Mapping differs to construction and recon geometry"_

K. Long keen we pursue as matter of urgency

** Space-point, track-finding efficiency studies partly blocked by lack of trigger #1182

** *ACTION*: Optimize residuals for final tracks (*C. Hunt*)

** *ACTION*: Fix close to paraxial tracks producing nan output (*C. Hunt*)

** *ACTION*: Update tracker online plots (*P. Kyberd*)

** *ACTION*: Update tracker schedule (*P. Kyberd*)

** *ACTION*: Update ConfigurationDefaults with tracker optimum parameters

** *ACTION*: Set HelicalPR on or off depending on CDB value of magnetic field (C. Hunt)

** Flag low pt for downstream tracker reconstruction? (*A. Dobbs*) 

* TOF (D. Rajaram)

** Restructure TOF MC Digitizer - part of trigger MC (*D. Rajaram*)

* EMR (F. Drielsma)

** MC #1033

* KL (M. Bogomilov)

** *STANDING*: MC validation, optimization, tuning, #1411

* CKOV (Drews, Winter, D. Rajaram)

* Monte Carlo trigger (D. Rajaram) #1182

** *ACTION*: Restructure TOF Digitisation and incorporate MapCppTrigger (*D. Rajaram*)

h3. Global Reconstruction

* Tracking (J. Greis)

* PID (C. Pidcott)

* Detector output

** *ACTION*: Get detector output in global coordinate system (*C. Heidt, C. Hunt*)

*** See #1631

** *ACTION*: Need uncertainties from detector reconstructions: on positions, momenta, tof time (*A. Dobbs*)

* *ACTION*: Implement dE/dx in Runge-Kutta (*M. Uchida*)

* Need uncertainties from detector reconstructions: on positions, momenta, tof time (*A. Dobbs*)

h3. Unpacking

* Need to roll out SL6 to Jenkins nodes (*P. Franchini*)

* DAQ channel maps to DB (*D. Rajaram*) #1375, blocked by #994

h3. Infrastructure

* Geometry/MC (S. Ricciardi, R. Bayes)

** *ACTION*: Make current beamline geometry available in CDB (*R. Bayes*)

* GRID and Batch Production (C. Rogers, J. Martyniak)

** Running 1.0.0

** Fix memory leaks

** execute_against_data.py

* Need C++ Reducer example (*A. Dobbs*)

* Code deployment

* Documentation

h3. Online

* Online reconstruction (A. Dobbs)

* Have prototype GUI and prototype ROOT-based document DB to replace maus-web-app and django #1312 (C. Rogers)

* Software On Call (A. Dobbs)

** http://micewww.pp.rl.ac.uk/projects/maus/wiki/Software_on-call (SOC wiki)

h3. Performance

* Speed improvements

** Fix memory leaks - preventing GRID runnning (A. Dobbs, D. Rajaram, C. Rogers)

** YK proposes parallelising MAUS with C++11 multi-threading, at the mapper level, see #1638 (A. Dobbs, D. Rajaram, C. Rogers, Y. Karadzhov)

*** Extensive refactor work

* Beam generation excessive resource usage

** Query analysis group requirements (in particular how many G4BL beams we need)

** Consider alternative upstream beam generation code

h3. Documentation

* Finish MAUS workbook (A. Dobbs)

h3. AOB

* MAUS paper draft - developers please review and supply input where required "launchpad":https://code.launchpad.net/maus-pub

h2. International Toll-Free Dial-in numbers

* Switzerland:	0800705351

* UK:	08004960576

* US:	1-866-740-1260

* "Other numbers":http://www.readytalk.com/an.php?tfnum=8667401260

* Access Code: 5673390

h2. Notes

h3. Attendance

A. Dobbs, J. Greis, P. Kyberd, A. Lui, C. Pidcott

h3. Detectors

* Detector Integration

* KL

* Ckov 

* EMR

* Tracker

* TOF

h3. Global Reconstruction

h3. Unpacking

h3. Infrastructure

* Geometry

* MC

* G4BL

* GRID

h3. Online

h3. Performance

h3. Miscellaneous