<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Dear FTers,<br>
we'll have next FT meeting on <b>Tuesday Oct 24 at 10:30AM(JLab
time)</b>.<br>
Here below the BJ coordinates:<br>
<a class="moz-txt-link-freetext" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__bluejeans.com_971952783&d=DwMDaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=cVGcBoL0aH8k8TAWsF2OUQLRME6Fr2Q-yDWM-WA_5zY&m=gFBfQf1hrfV9HbtN1Eebo8KmaLCMDU8EuiZQVFWbFIw&s=puj98aRCEKVGy1fLuirA62RHBaFv1ItQDSDghUu-nbU&e=">https://bluejeans.com/971952783</a><br>
The agenda is reported on the FT wiki<br>
<a class="moz-txt-link-freetext" href="https://clasweb.jlab.org/wiki/index.php/10/24/2017_Meeting">https://clasweb.jlab.org/wiki/index.php/10/24/2017_Meeting</a><br>
Feel free to add any other items you want to be discussed<br>
Cheers<br>
Marco<br>
<br>
<br>
<br>
<br>
<i>MINUTES and HOMEWORKS</i><i><br>
</i><i> - 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) </i><i><br>
</i><i> - 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. </i><i><br>
</i><i> - at the next meeting we'll present a draft of a detailed
FT commissioning plan completing what already in CalCom hands</i><i><br>
</i><i> - based on the message below, we'll prepare a detailed
list of duties and tasks for the commissioning and production
runs</i><i><br>
</i><i> - provide a repository with all the relevant documents and
documentations to make easy to get used with the FT systems</i><i><br>
</i><i> - we'll use the engineering run as a good test for
documentations implementing the feedback in the
manual/procedures for the first run</i><i><br>
</i><i> - prepare a list of histos (same as CLAS6 MONB) to check
FT vitals</i><i><br>
</i><i> </i><i><br>
</i><i> </i><i><br>
</i><i> Mar</i>co Battaglieri wrote:<br>
</div>
<blockquote cite="mid:59D3D9A5.9010608@ge.infn.it" type="cite">
Dear FT enthusiasts,<br>
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.<br>
<br>
Over the next month we should provide:<br>
- a detailed commisioning plane<br>
- a detailed schedule for the commisining compliant with the
general CLAS12 commisioning plan<br>
- a list of 'detector experts' and other collaborators (students?
postdocs?) that will be trained during the commissioning to gain
enough confidence with the detector<br>
- a detailed shift list for commisioning and RG-A run time to be
sure we have enough <br>
- a list of analysis/calibrators working off-line during
commisioning/run time<br>
It would be also very useful to check the status of:<br>
- tools necessary to operate, monitor, and calibrate the FT<br>
and define a common set to be tested and used.<br>
<br>
In parallel we should check the status of FT GEMC/REC sw to be
sure that all tools are in place.<br>
<br>
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.<br>
<br>
Here is a (preliminary) list of sub-task experts/coordinators:<br>
<br>
FT-Cal<br>
- 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<br>
- sim/rec expert: she/he knows how the Sim/Rec code works, take
care of standard and exceptional (such as develop patches) code
maintenance <br>
- calibration coordinator: she/he coordinate the calibration
effort, check results of calibration team <br>
<br>
FT-Hodo <br>
- hardware expert<br>
- sim/rec expert<br>
- calibration coordinator<br>
<br>
FT-Trck <br>
- hardware expert<br>
- sim/rec expert<br>
- calibration coordinator<br>
<br>
- 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<br>
- 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<br>
<br>
- 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<br>
- VeryStrange analysis coordinator<br>
- LMD analysis coordinator<br>
- HybridBaryon analysis coordinator<br>
- Pentaquark analysis coordinator<br>
<br>
+ list of students/postdocs or any seniors interested to
FT-involved analyses<br>
<br>
We should appoint a responsible for each activity in order to have
a well organized structure ready for data taking day-0.<br>
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.<br>
Please, identify among your groups, people that may lead the
effort and resources to accomplish the listed tasks and send it to
me by <b>Tue Oct 10 </b><br>
<br>
I propose to resume the Wednesday FT meeting to define, prepare
and discuss this plan in details.<br>
Let's start next week (<b>Oct 11 at 9:00 EST</b>) with the old
timetable (and discuss if we want to keep it!).<br>
I'll send a reminder shortly before<br>
Cheers<br>
Marco<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</body>
</html>