BCAL Reconstruction Meeting 2014-09-18
Video Conferencing Information
Meeting Time: 12:00 p.m. EDT
- To join via a Web Browser, go to the page  https://bluejeans.com/907185247.
- To join via Polycom room system go to the IP Address: 220.127.116.11 (bjn.vc) and enter the meeting ID: 907185247.
- To join via phone, use one of the following numbers and the Conference ID: 907185247.
- US or Canada: +1 408 740 7256 or
- US or Canada: +1 888 240 2560
- Upon connection all microphones are automatically muted. To unmute your mike on a Polycom or equivalent unit, enter *4. Unmuting on a computer is trivial as there is a microphone button than can be clicked.
- More information on connecting to bluejeans is available.
Participant Direct Lines
- JLab Phone: in CC F326 is 757-269-6460 (usual room)
- JLab Phone in CC L207 is 757-269-7084
- Phone in the Regina Video-conference Suite is 306-585-4204
- Reconstruction code
- Timing: extracted from F1TDC and compared to fADC; check need for time-walk (fits, iterations, etc)
- Tegan: BDT presentation and timing plots at next meeting
- Sampling fraction tables
- Shower curvature tables: compare KLOE to IU codes: check gap in cluster handling between codes.
- z-coordinate determination from up/down amplitude ratio
- set variable “failures” to a number other than zero (e.g. -9999 or similar)
- comb code for constants to be pulled out into a database
- measure data pedestals using LV=0 setting (Mark)
- Action Items
- BDT Update: Presentation:File:BDT 2014-09-18.pdf (Tegan)
- fADC time-walk code: see emails from Aug 21 and Sep 17; (Will and Tegan)
- Any other business
Attendees: David, Elton, Will M., Irina, Andrei (JLab), Will L. (CMU), Justin (MIT), Tegan, Zisis
- Announcements: Zisis is planning to come to JLab for shifts, Oct 1-11, subject to the accelerator schedule.
- Action Items: Items 1 and 2 are being worked on; see Tegan's reports below.
- Update on BDT: Tegan gave a report (see link above) on what he and Justin have been working on. The objective is to implement the BDT in the BCAL Reconstruction to see if it can improve over Will's cuts analysis (Looking for similar efficiency with higher background rejection and signal purity); also to import the BDT knowledge to Regina.
- Overview: The events are generated by bggen (full hadronic photoproduction spectrum) requiring at least 2 showers/clusters in the BCAL. The FCAL is not involved at this stage but will be in the future. The BDT was trained on a single cluster (gamma).
- (ES) pi0 peak is at 130 MeV resolution is 30 MeV (slide 5) and has a tail. This should be looked at more carefully. Red curves are signal, blue background.
- (WL) Observation on Slide 8. Will had communication with Richard Jones on a similar issue, namely that the truth info from HDGEANT is not behaving as it should. Secondaries are being reordered. Some showers start right outside the BCAL. Zisis will follow up.
- (DL) primary flag =1 comes from generator.
- (JS) It is good to have detector-level matching in the BDT.
- (DL) DBCALIncidentParticle factory was written to capture Andrei/Irina's Sampling Fraction tables.
- (ES) Why the theta ranges? JS: Theta is binned in ranges (instead of letting the BDT handle it) because it allows the extraction of finer dependencies over limited angular range, instead of a global dependency.
- (WL) Is there a hard cut to eliminate noise? TB: No.
- (WL) Why Point>1 cut? JS: It is a global cut, which is done in BDT to simplify life ahead of time, by removing obviously unnecessary sorting of such a variable in BDT. Nevertheless, even after the cut the Point variable is still used in the BDT classifier.
- (ZP) What is z-coordinate cut? TB: it is almost the full length of the BCAL, in the global coordinate frame, where the BCAL goes from 17-407cm.
- (ZP) The ranking of the variables changes in the last few slides. TB: The top 4 variables are always the same, and there is no significant difference in their ranking.
- (DL) tproj looks narrow. TB: this is an artifact of the plotting. Promised to circulate expanded scale plot after the meeting (and he did).
- (AS) Can you train the BDT in pairs of photons? JS: Training it on di-photon sample may occur in the future. It is more complicated.
- (ES) What are the horizontal lines in slide 5? TB: Those represent the hard cuts from Will, ie if we match the efficiency we get a better purity.
- Conclusion: Will's hard cuts did a pretty good job. More BDT work is needed as mentioned above.
- Update on Timing code: Will said that it looks good. Tegan took the time-walk out, but it needs to be replaced with new code, following the flash ADC timing. Tegan will look at time vs ADC to study the t-w.
- Any other business: Zisis suggested that Tegan/Justin present their work at the Collaboration Meeting, and everyone agreed. Zisis will email Mark Ito to schedule this.