February 24, 2016 Calibration

GlueX Calibration Meeting
Wednesday, February 24, 2016
11:00 am, EST
JLab: CEBAF Center, F326

Communication Information

Remote Connection

You can connect using BlueJeans using the meeting number 630 804 895 .       (Click "Expand" to the right for more details -->):

1. Make sure you have created a BlueJeans account via your JLab CUE account using this link:
   • http://jlab.bluejeans.com (You should only need to do this once)

   
   

2. Meeting ID: 630804895
   • (you may need to type this in, depending how you connect)

   
   

3. If connecting via Web Browser: click this link (no passcode is needed):
   • https://bluejeans.com/630804895

   
   

4. If connecting via iOS or Android App:
   • Use your JLab e-mail address to log in and then enter the meeting ID given above to join the meeting

   
   

5. If connecting via Phone: Dial one of the following numbers and then enter the meeting ID above and hit "#" or "##"
   • Dial: 1 888 240 2560 (US or Canada only)
   • or, List of International Numbers

   
   

6. If connecting via Polycom unit:
   • Dial 199.48.152.152 or bjn.vc
   • Enter meeting ID above
   • Use *4 to unmute

Slides

Talks can be deposited in the directory /group/halld/www/halldweb/html/talks/2016 on the JLab CUE. This directory is accessible from the web at https://halldweb.jlab.org/talks/2016/ .

Agenda

1. Announcements
   • Offline monitoring running on incoming data
2. Calibration Tasks
   • Spring 2016 Recon Checklist
   • Mcsmear updates
   • Calibration Train
     • Running at 5PM today (if farm is back up)
     • RCDB production runs
3. Current Run
   • Identifying "production" runs
   • Data Validation
4. Subdetector Reports
5. Sim1 progress
   • sim1 jobs
6. AOB

Minutes

1. Announcements
   • Offline monitoring has been running on incoming data and had mostly caught up with the data on tape before lustre filesystems were taken offline.
   • The next offline monitoring run will be scheduled for about a week after the calibration train launch, depending on the progress of the jobs.
2. Calibration Tasks
   • We discussed a few new reconstruction tasks to tackle for this spring
   • Simon is coordinating geometry updates. Some changes will be made to the XML geometry files, some parameters may be stored in CCDB when convenient.
   • For physics analyses, samples of simulated data are needed that correspond to the conditions of the data that was taken. We therefore need to update mcsmear to reflect the resolutions in current data and to look at adding run-dependent MC constants. Sean will coordinate the effort of updating the software, detector experts will be in charge of adding the CCDB constants that best reflect the conditions of their detector.
     • The primary tasks are to add dead/noisy channel support in sim-recon for detectors that do not already support this, and to update the parameters used by mcsmear. These values are listed in the wiki page linked in the agenda.
     • Sean and Dmitry will also explore loading run-dependent thresholds and other values from RCDB, and detector noise modeling will be revisited once random triggers are implemented.
     • The hardest part will likely be to devise analyses that can obtain these new CCDB constants, therefore this will be an on-going agenda item.
   • David L. pointed out that there are some lingering problems with how low-level configuration parameters are applied when reading in EVIO files. This mostly affects fADC250's. Mike S. is working on this, but it requires extensive refactoring, so he is planning to have it ready to test the new fADC250 firmware that is planned for this summer. This is expected to mainly affect the analysis of mode 8 data in the BCAL and FCAL, as it is likely the cause of differences between results with data taken in modes 7 & 8 (short & long). We are taking some data in mode 8 to check the algorithms, so we will keep an eye if this project needs to be higher priority.
   • The additional of photon polarization data into the
   • Calibration Train running
     • Currently this is planned to run at 5PM Thursday, to allow for refinements to the procedure and stable farm conditions..
     • Some tweaks to the RCDB search conditions for production runs, since most of the diamond runs were made with the daq type of "EXPERT" instead of "PHYSICS". Justin also pointed out some inconsistencies.
3. Current Run
   • Identifying "production" runs
   • Data Validation
4. Subdetector Reports
5. Sim1 progress
   • sim1 jobs
6. AOB