[Clas12_photon] FT commissioning and run plan

Wed Oct 11 19:30:57 EDT 2017

Dear All,
as mentioned today, one of the things we have to do is to define simple 
histograms to be included in the online monitoring gui (aka mon12) that 
shifts takers will use to monitor the detector status. In attachment you 
can find snapshots of the plots available during kpp.
Best regards,
     Raffaella

Marco Battaglieri wrote:
> Dear FTers,
> here are the minutes of toda'ys meeting with homeworks for the next 
> meeting.
> Feel free to add or point out what missed.
> As discussed I created a doodle
> https://urldefense.proofpoint.com/v2/url?u=https-3A__beta.doodle.com_poll_tsyaq9kz7ck34npb&d=DwICaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=cVGcBoL0aH8k8TAWsF2OUQLRME6Fr2Q-yDWM-WA_5zY&m=5uJDlBsq1f6kJ-Ezsl_LfXO3q_52NLAiodu3ULv1Hiw&s=r07rzuS97Qbe6PCA99OmUmLUzcJ8AKIbCkKhyVWqmvU&e= 
> for next Tuesday (as a template for next weeks). I started at 10:00AM 
> EDT (hope it shows up right in your time zone) ending at 1:00PM.
> Please express your preference*by Sunday night *so that on Monday I 
> can call the meeting.
> Thanks again for attending
> Marco
>
> MINUTES and HOMEWORKS
> - after discussing the plan circulated last week we all agree on the 
> need of a organized run plan for all activities related to the FT 
> (from the HW to the shifts, tfrom the calibrations to thehigh level 
> analysis)
> - all sub-groups (MesonEx, LDM, VeryStrange and Hybrid Baryons) are 
> requested to contribute to set up a full  working detector and a 
> complete framework to monitor, calibrate it before to focus on high 
> level-specific analyses.
> - at the next meeting we'll present a draft of a detailed FT 
> commissioning plan completing what already in CalCom hands
> - based on the message below, we'll prepare a detailed list of duties 
> and tasks for the commissioning and production runs
> - provide a repository with all the relevant documents and 
> documentations to make easy to get used with the FT systems
> - we'll use the engineering run as a good test for documentations 
> implementing the feedback in the manual/procedures for the first run
> - prepare a list of histos (same as CLAS6 MONB) to check FT vitals
>
>
>
> Marco Battaglieri wrote:
>> Dear FT enthusiasts,
>> as you know the commissioning of CLAS12 will happen shortly 
>> (beginning of December) and after the 30 days allocated,  we'll run 
>> for several months the RG-A run.
>>
>> Over the next month we should provide:
>> - a detailed commisioning plane
>> - a detailed schedule for the commisining compliant with the general 
>> CLAS12 commisioning plan
>> - a list of 'detector experts' and other collaborators (students? 
>> postdocs?) that will be trained during the commissioning to gain 
>> enough confidence with the detector
>> - a detailed shift list for commisioning and RG-A run time to be sure 
>> we have enough
>> - a list of analysis/calibrators working off-line during 
>> commisioning/run time
>> It would be also very useful to check the status of:
>> - tools necessary to operate, monitor, and calibrate the FT
>> and define a common set to be  tested and used.
>>
>> In parallel we should check the status of FT GEMC/REC sw to be sure 
>> that all tools are in place.
>>
>> We already discussed that, during regular data taking, there will be 
>> only one FT expert-on-call serving the 3 subsystems and this requires 
>> that experts of each sub systems will share information and details.
>>
>> Here is a (preliminary) list of sub-task experts/coordinators:
>>
>> FT-Cal
>> - hardware expert: she/he knows how the detector works, how to 
>> monitor and judge if it is healthy it and names of (off-site) 
>> specialists that may take care of hw issues or help on the phone
>> - sim/rec expert: she/he knows how the Sim/Rec code works, take care 
>> of standard and exceptional (such as develop patches)  code maintenance
>> - calibration coordinator: she/he coordinate the calibration effort, 
>> check results of calibration team
>>
>> FT-Hodo
>> - hardware expert
>> - sim/rec expert
>> - calibration coordinator
>>
>> FT-Trck
>> - hardware expert
>> - sim/rec expert
>> - calibration coordinator
>>
>> - FT trigger expert: she/he has knowledge of the hw and sw behind the 
>> trigger, collect requirements based on physics and acts as a link 
>> with the trigger/daq group
>> - FT data cooking expert: she/he knows the machinery requested to 
>> cook a file on the farm, keep trace of the current cooking status, 
>> collect the monitoring histos (or equivalent) verifying and checking  
>> that the FT information are always present in the data stream
>>
>> - MesonEx analysis coordinator: she/he coordinates analysis efforts 
>> providing all the necessary information about the history of 
>> collected data, correction/tools to be used, warnings, ... to any new 
>> data analyzer
>> - VeryStrange analysis coordinator
>> - LMD analysis coordinator
>> - HybridBaryon analysis coordinator
>> - Pentaquark analysis coordinator
>>
>> + list of students/postdocs or any seniors interested to FT-involved 
>> analyses
>>
>> We should appoint a responsible for each activity in order to have a 
>> well organized structure ready for data taking day-0.
>> Each expert will act as link to other detector/group/experiments 
>> subtasks  and should come with an estimate of resources needed to 
>> manage the task.
>> Please, identify among your groups, people that may lead the effort 
>> and resources to accomplish the listed tasks and send it to me by 
>> *Tue Oct 10 *
>>
>> I propose to resume the Wednesday FT meeting to define, prepare and 
>> discuss  this plan in details.
>> Let's start next week (*Oct 11 at 9:00 EST*) with the old timetable 
>> (and discuss if we want to keep it!).
>> I'll send a reminder shortly before
>> Cheers
>> Marco
>>
>>
>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/clas12_photon/attachments/20171011/68100d3c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mon12_02-03-2017_04.15.04_PM.zip
Type: application/zip
Size: 249766 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/clas12_photon/attachments/20171011/68100d3c/attachment-0001.zip>