Actions
PC16092015¶
Wednesday 16th September 2015 at 15:00 BST
Room CR09 RAL
Summary of Actions¶
- ACTION: Fix tracker geometry plane ordering bug (C. Hunt)
- 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 (J. Greis)
- ACTION: Need C++ Reducer example (A. Dobbs) C. Rogers will provide one
- ACTION: Need MAUS Schedule for Alan Grant by next time (CKOV: A.Liu, TOF: D. Rajaram, MC: D. Rajaram, Global: J. Greis)
- ACTION: Fix geometry test which randomly produces large SOAP error (R. Bayes)
- Notes: these don't appear to be geometry-related. jobs pass ok on heplnm070 jenkins master. issue with helplnv157 seems configuration related.
Agenda¶
Release status¶
- Current release = 1.0.0
- Targets for release 1.1:
- execute_against_data.py should be always make a tarball
- Support for gcc 4.9
- Updates to Geometry handling
- EMR reducer
- SciFi CDB interface
- SciFi mapping and calibration update
- Future release
- Updated tracker noise
- Workbook added
- Targets for future release:
- Trigger MC
- Fix memory leaks
- Tracker -- Kalman updates
Schedule¶
Detectors¶
- Detector integration (D. Rajaram)
- Reconstruction quality flags (A. Dobbs to make requests to detector groups) #1585
- Tracker (P. Kyberd)
- Tracker plane ordering bug Fixed in trunk, mapping error corrected
- Observe that tracks when visualised do not appear to line up between trackers, in both position and slope
- 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, #1411Done, ref. PID paper
- CKOV (A. Liu, Drews, Winter, D. Rajaram)
MC Digitizer updateCkov MC now in trunk. Needs to be validated against data.
- Monte Carlo trigger (D. Rajaram) #1182
- ACTION: Restructure TOF Digitisation and incorporate MapCppTrigger (D. Rajaram)
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: Get detector output in global coordinate system (C. Heidt, C. Hunt)
- ACTION: Implement dE/dx in Runge-Kutta (M. Uchida)
- Need uncertainties from detector reconstructions: on positions, momenta, tof time (A. Dobbs)
Unpacking¶
- Need to roll out SL6 to Jenkins nodes (P. Franchini)
DAQ channel maps to DB (D. Rajaram) #1375, blocked by #994Done
Batch Reconstruction¶
- GRID running 1.0.0
- Enable MC GRID running again #1739
- execute_against_data.py to always produce tarball
- Fix memory leaks
Infrastructure¶
- Geometry/MC (S. Ricciardi, R. Bayes)
- ACTION: Make current beamline geometry available in CDB (R. Bayes)
- Need C++ Reducer example (A. Dobbs)
- Documentation
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)
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- Current MAUS speedup is satisfactory. Can revisit, if any speed issues with MC.
- Beam generation excessive resource usage
- Query analysis group requirements (in particular how many G4BL beams we need)
- Consider alternative upstream beam generation code
Tools¶
- Add V. Blackmore event visualiser to MAUS
Documentation¶
AOB¶
International Toll-Free Dial-in numbers¶
- Switzerland: 0800705351
- UK: 08004960576
- US: 1-866-740-1260
- Other numbers
- Access Code: 5673390
Notes¶
Attendance¶
T. Mohayai, J. Nugent, A. Liu, C. Pidcott, J. Greis, R. Bayes, P. Kyberd, D. Rajaram
Apologies: A. Dobbs
Release¶
Detectors¶
- Detector Integration
- DR asks that detectors provide a simple yes/no flag to denote 'analyzability' of a run.
- DR will produce one for TOFs.
- PK agrees that a high-level yes no should be easy to get from trackers based on #spacepoints/digits [ or something of that sort ]
- Need to get this done so that Janusz can implement table in CDB & test on preprod before rolling out
- KL
- Ckov
- EMR
- Tracker
- PK: has generated plots [ Tracker efficiencies based on slab hits in TOF1/TOF2 --> ~98-99% for t1, ~85% for T2 up to 98 after Ed's calibration ] which Ed thinks are useful.
- ACTION: need to get the plots into MAUS. PK has asked MU about getting them into MAUS. [ ]
- PK: Tracker efficiency map may need to be folded into MC if there are reasons to believe the fiducial-dependent (in)efficiencies may affect emittance measurements
- Ed & CH have updated calibration & maps. In the trunk.
- CH has added a calibration/mapping uploader/downloader to MAUS. The track reconstruction code does not automatically download the calibrations from CDB. But this can be done [ similar to what's done for TOF/KL/DAQ ]
- ACTION: Config cards: Finalize tracker reco cards & move them to ConfigurationDefaults
- Currently track reconstruction is not set to handle case where one magnet is on and other is off. Since we'll likely have more than one data-set with this configuration, can we modify code to handle it natively? [ instead of having to process twice, once with Helical on and once with Helical off ]
- TOF
Global Reconstruction¶
- JG: de/dX implementation in RK is done. Currently testing.
- CP & JG report issues with running Global reducers
- CP: issue when setting header_and_footer_mode to "dont_append". CR will chase this. Could be a SWIG issue. CP to remove swig .i file and see if that sorts it out.
- JG: cannot run reducer in conjunction with mappers. DR has been running mappers + tof calib an plot reducers. JG to check if this is also a swig issue. If not, raise issue.
Unpacking¶
Batch Reconstruction¶
- MC processing almost there. Code-side is OK. CDB-side: RB to upload cooling channel tags to production DB [ has been tested on preprod. ]. Plan is to wait for new MAUS release and try running batch MC and grid next week.
Infrastructure¶
- Geometry
- June & July geometries are in CDB: 69, 70
- RB to verify that "current" geometry points to ID 70
- MC
- G4BL
- Other
Online¶
Performance¶
Tools¶
Miscellaneous¶
- PK to check tracker schedule and update by end of the week
- JG to update Global schedule this week.
Updated by Rajaram, Durga about 8 years ago · 3 revisions