<html>
<head>
</head>
<body text="#000000" bgcolor="#FFFFFF">
Dear All,<br>
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.<br>
Best regards,<br>
Raffaella<br>
<br>
<div class="moz-cite-prefix">Marco Battaglieri wrote:<br>
</div>
<blockquote type="cite" cite="mid:59DE5229.10606@ge.infn.it">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">Dear FTers,<br>
here are the minutes of toda'ys meeting with homeworks for the
next meeting.<br>
Feel free to add or point out what missed.<br>
As discussed I created a doodle<br>
<a class="moz-txt-link-freetext" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__beta.doodle.com_poll_tsyaq9kz7ck34npb&d=DwMDaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=cVGcBoL0aH8k8TAWsF2OUQLRME6Fr2Q-yDWM-WA_5zY&m=5uJDlBsq1f6kJ-Ezsl_LfXO3q_52NLAiodu3ULv1Hiw&s=r07rzuS97Qbe6PCA99OmUmLUzcJ8AKIbCkKhyVWqmvU&e=" moz-do-not-send="true">https://beta.doodle.com/poll/tsyaq9kz7ck34npb</a><br>
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.<br>
Please express your preference<b> by Sunday night </b>so that
on Monday I can call the meeting.<br>
Thanks again for attending<br>
Marco<br>
<br>
MINUTES and HOMEWORKS<br>
- 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) <br>
- 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. <br>
- at the next meeting we'll present a draft of a detailed FT
commissioning plan completing what already in CalCom hands<br>
- based on the message below, we'll prepare a detailed list of
duties and tasks for the commissioning and production runs<br>
- provide a repository with all the relevant documents and
documentations to make easy to get used with the FT systems<br>
- we'll use the engineering run as a good test for
documentations implementing the feedback in the
manual/procedures for the first run<br>
- prepare a list of histos (same as CLAS6 MONB) to check FT
vitals<br>
<br>
<br>
<br>
Marco 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>
</blockquote>
<br>
</body>
</html>