1. CLAS12 CalCom Activity CLAS Collaboration Meeting, March 6 th 2014

2. Outline Summary of 2013 activity: – Commissioning Meeting on subsystem commissioning Update of subsystem commissioning plans – Calibrations First meetings with detector subsystems Combined calibration of forward detectors – CalCom Workshop 2014 Workplan: – Calibrations Meetings with detector groups to discuss calibration algorithms and software development Development of common software tools Development of calibration software template – Commissioning Revision and update of commissioning plan

3. 2013 Commissioning Activity Meetings with CLAS12 subsystems Participants: CalCom members and subsystem representatives Purpose: discuss and review subsystem commissioning plans Outcomes: recommendation to subsystem groups Meetings with EC/Pcal, DC, FTOF, CTOF, CND, MM, SVT, FT, HTCC, Beamline in 2012/2013 Meeting minutes and committee recommendations available on CalCom Wiki

4. 2013 Commissioning Activity Revision and update of commissioning plan Report submitted from all CLAS12 subsystem groups via standard template: Status, Achievements and Issues since last report Highlights Work plan, resources involved and timeline CLAS12 Subsystems Reports available at: https://userweb.jlab.org/~devita/clas12_commissioning/meetings/ calcom_20131120/20131120_commissioning_v1.pptx

5. 2013 Calibration Activity Calibration of Forward Detectors: Forward detector installation is close to completion First calibration with cosmic rays in progress Work will continue during 2014 Possibility of performing simultaneous calibration of EC-PCal- FTOF combining information from different detectors Issue studied by FTOF and EC-PCal groups and discussed at CalCom meetings Now getting underway! Presentations available at: https://clasweb.jlab.org/wiki/index.php/EC-PCAL- FTOF_Calibration_11/07/2013

6. CalCom Workshop Workshop at the November CLAS Collaboration meeting Overview of activity based on CLAS12 subsystem reports Detailed presentations from most advanced detector systems: – FTOF – EC-Pcal Open discussion https://clasweb.jlab.org/wiki/index.php/CalCom_Sess ion_11/20/2013

7. CalCom Workshop Open discussion: Calibration: Framework: – Definition of requirements and goals – Standalone vs integrated/standardized codes Online vs. offline – Online can be necessary to optimize EC-PCal based triggers – Online calibration/High-level monitoring can identify problems to be fixed – Offline allow for higher precision and should be used for final optimization Commissioning: Combined detector calibrations with cosmic rays Dependencies from other systems Checkout with final front-end electronics Outcomes: Better coordination in the development of calibration software More strict collaboration between detector group and software group Supervision of calibration software development and test of “new releases” Documentation and tutorials for “calibrators” Calibration readiness review before start of massive data cooking

8. Calibration WorkPlan Plan based on last year’s work and open discussion: Periodic meetings with detector groups to discuss algorithms, discuss software development and monitor progress Production of Detector Subsystems Geometry and Calibration Constant documents New representatives of the software group (M. Ungaro and G. Gavalian) in the CalCom committee to supervise and guide software development Development/Use of common tools whenever possible to reduce workload for developers Development of calibration software template

9. CalCom Role Provide oversight to the development of calibration tools Provide feedback from the detector groups to the software group and vice versa In collaboration with the software group, provide software template for detector groups and common I/O tools Enforce basic rules about documentation, tutorials for calibrators, calibration tool usability, test, maintenance, …

10. Detector Groups and CalCom In the current year, detector groups will be asked to meet with CalCom to present and discuss the detector calibration plan: – Present strategy – Discuss algorithms – Discuss software development – Resources – Time scale submit Information on resources and time scale to define the timeline of the CLAS12 calibration development provide input for the design of the database structure by submitting documents describing detector geometry and calibration constants

11. Detector Group Responsibilities 1)A geometry document – coordinate system defined, – names and values for key parameters, – clear, easy-to-understand pictures. – DC geometry document as an example. https://clasweb.jlab.org/wiki/index.php/ CLAS12_Detector_Subsystem_Geometry 2)A calibration database document – Describes and names the parameters which are used to go from detector signal to "hit value”. 3)A monitoring document – names and describes histograms, graphs, tables and/or other data summaries which will be used online to discover changing behavior, and in particular, malfunctioning equipment. – Also, names and describes plots to be used by the offline "chef" to make sure that the relevant reconstruction code (e.g. tracking, shower-finding, etc.) is working right; e.g. number of tracks per event, etc. 4)For Reconstruction software developers – a reconstruction methods document that describes the mathematical methods and formulae used in the reconstruction From Veronique’s talk

12. Detector Group Responsibilities SLOW CONTROL: Each detector group is asked to identify a person who will be responsible of slow control development. Role: a.Work together with slow control group to define the slow control needs of the system. Identify things that will already be taken care of as standard (eg HV, Low Voltage, Disc/Scaler) b.Identify any non-standard hardware and ensure that drivers / device support are available. NOTE. The development of drivers / device support will be done by specialists. Mostly already done. c.Create any specialist GUIs required for that system. This will be done using a drag and drop GUI builder tool. Templates and examples will be provided. d.Develop and specialized slow controls scripts / tools for that subsystem. E.g initialization, monitoring, alarming. Required Effort: 3 months FTE for each system. That would include developing GUIs, scripts, testing and documentation.

13. Common Tools for Calibration Software DATA I/O: Calibration database access tools: Histogramming tools From Gagik’s talk at the sofwtare workshop

14. Calibration Software Template Develop examples of calibration software within the CLAS software framework – Define scheme of calibration software within framework – Use common tools for input/output: EVIO I/O CCDB access Graphics and fitting – Implement calibration algorithms – Test software on simulated data (GEMC) – Use newly built package as template for other detectors – Candidates for the first trials: FT and CND

15. Calibration meetings: FTOF (1) First meeting on FTOF calibration: – Software being developed by Haiyun Lu (Iowa U.) – Calibration approach defined based on CLAS experience and new FTOF cosmic ray calibrations – Code designed to work in CLARA – Initial tests with cosmic ray data

16. Calibration meetings: FTOF (2)

17. Calibration meetings: FTOF (3)

18. Commissioning WorkPlan Complete commissioning plan for new detectors (RICH) Review/Update commissioning plan for all CLAS12 subsystems Update Commissioning Timeline Release new version of commissioning document

19. Summary and Outlook 2013 activity: – Completion of first round of meetings on subsystem commissioning and update of commissioning plans – First meetings on detector calibration with focus on forward detectors – CalCom Workshop 2014 activity: – Focus on development of calibration tools with the goal of having calibration running by the end of the year – Implement recommendations discussed at CalCom Workshop – Provide oversight of the calibration tools development – Provide support to detector groups in collaboration with the software group (use of common tools, use of calibration templates)