Transcript Tools for Trigger

А.Чеплаков – ЛФВЭ ОИЯИ
OTS ATLAS Strategy @ JINR
Персональный (упрощенный?) взгляд
ATLAS Workshop at JINR 12/05/2009
Содержание
Эволюция АТЛАСа
Первоисточники и основные понятия
Простые вычисления
Проблемы и предложения
12/05/2009
OTS ATLAS Strategy @ JINR
2
Эволюция АТЛАСа
От строительно-монтажных работ через наладочные
работы – к рутинной эксплуатации детектора
От разрозненных активностей в подсистемах и физических
группах - к централизованному, скоординированному
управлению
Безусловно, со временем команда ОИЯИ также будет
меняться и обретет иную, стабильную структуру
На переходном этапе – акцент на «доводку» и изучение
детектора, калибровки, на отработку алгоритмов
.................blah-blah-blah
12/05/2009
OTS ATLAS Strategy @ JINR
3
Первоисточники
ATLAS MoU for M&O CERN-RRB-2002-035: “Memorandum of Understanding for
Maintenance and Operation of the Detector” (from 1 May 2002 to 31 Dec 2011)
- reaching agreement on a maintenance and operation procedure and monitoring its
functioning
- endorsing the annual maintenance and operation budgets of the detector
... It is also a fundamental principle that an Institute, which has contributed a component of
equipment, will also contribute to the necessary scientific and technical manpower support
to operate that component and maintain it in good working order.
... For Category A, the costs are to be shared amongst the ... Institutes in proportion to the
number of ... authors of scientific publications of the Collaboration. - in cash!
[Only Italy, USA, CERN & JINR – contribute to all sub-systems]
ATLAS Home Page - ATLAS Organization=>Authorship Committee=> Authorship
Policy document
- document sets out the policy for ATLAS Authorship during data-taking (2008 and beyond).
- in particular, definitions of terms: ATLAS member & ATLAS author
12/05/2009
OTS ATLAS Strategy @ JINR
4
Первоисточники
Действующие списки см. http://atlas-authdb.web.cern.ch/atlas-authdb/
The individual entries for each Institute in the ATLAS directory, showing the list of people
currently associated to the institute, including those appearing on the author’s list (A),
contributing to the M & O assessment (M) and the operations tasks (O).
JINR: ATLAS members - 178: 43 on authorlist (A), 38 counted for M&O (M) and 46.25 for OT (O, o)
AM
Last name
First name Institute phone Mobile
Ahmadov
Azad
AMO
Aleksandrov
Igor
Alexeev
Guennadi
-10240.57
MO
Artemenkov
Denis
+74962165059
Artikov
Akram
Astabatyan
Razmik
-10269.1
Ao
Barashkou
Andrei
AMO
Bardin
Dmitri
..........................................................
Email address
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
CERN (201) :
A=152 MO=128 OT=134.8
Brookhaven (91) : A= 46 MO= 47 OT= 50
ATLAS total (3691) = 2361 OT
12/05/2009
OTS ATLAS Strategy @ JINR
5
Основные понятия - Авторство
“To become an ATLAS author, a person must:
Have been an ATLAS member for at least one year.
Not be an author of another major LHC collaboration at the time of
application (this rule applies to all physicists, but an exception may be
made for engineers).
Have spent at least 80 working days and at least 50% of their available
research time during the year doing ATLAS technical work (defined in
Appendix). The total of 80 days technical work may be accumulated over
more than one year in exceptional circumstances.”
12/05/2009
OTS ATLAS Strategy @ JINR
6
Основные понятия - Авторство
Technical work includes:
Working on the design, construction, installation or commissioning of ATLAS,
including upgrades.
Running, servicing and maintaining the detector, including work during shutdowns and work on detector calibration
Participating in ATLAS Test-beam work, either in the preparation, running or data
analysis.
Working on the On-line or Off-line ATLAS Software: developing code of general
use, as opposed to code intended purely for physics analysis by a few individuals.
Running and overseeing ATLAS software: running Monte Carlo production or
running/overseeing data processing.
Taking shifts or work resulting from being on-call for a subsystem.
Working on managerial and administrative tasks for ATLAS, including serving on
ATLAS committees or acting as a Physics Convener.
Managing an ATLAS group in an Institution (university or lab).
12/05/2009
OTS ATLAS Strategy @ JINR
7
Основные понятия - Авторство
“Technical work does not include:
Doing physics analysis.
Contributing to physics papers or participating in physics meetings.
Supervising others doing physics analysis, other than as the convener of an ATLAS
physics group.
These definitions are intended to include the case of a theorist with a strong
involvement in ATLAS. To qualify as an author, a theorist would have to have
done some technical work, such as implementing Monte Carlo code in the
ATLAS environment.”
2.4.2 Additional authors for a particular paper
“…a visitor to ATLAS or … non-ATLAS theorist who has made a significant contribution
to a particular paper may request to the AC Chairperson to be included in the paper’s
author list, although it would be more normal to acknowledge the person in the paper’s
Acknowledgements”
“… it may be very appropriate to recognize key Engineers…”
12/05/2009
OTS ATLAS Strategy @ JINR
8
Основные понятия - OTSMOU
Extract from Authorship Policy document
“Operation tasks, needed to operate/maintain the ATLAS detector, including triggering,
off-line processing and data preparation, will be allocated to an Institution according to
the number of ATLAS authors in that Institution, including members in the process of
qualifying as authors. All operation tasks are technical work but not vice versa.
The Collaboration Board approved in its meeting on 23Feb 2007, the so‐called
OTSMOU Report (Operation Task Sharing and M&O Update), as well as the
mandate and composition of POTS (Panel for Operation Task Sharing) to
oversee the OT process and monitor the fair Sharing of operation tasks across
the ATLAS institutions.
POTS proposals (3 Feb 2009):
1) Use a well trained pool of shifters year by year;
2) Also use people other than the experts for shifts, ensuring annual rotation;
3) All ATLAS members are expected to participate (not every year but over some years).
4) Allow allocation of tasks per institution (head) in blocks which institution then ensures are
executed;
5) If necessary, apply loads on tasks to ensure a fair balance across different service tasks.
12/05/2009
OTS ATLAS Strategy @ JINR
9
Основные понятия - OTSMOU
The Collaboration Board meeting 20 Feb 2009:
The Operation Tasks are now subdivided into two categories:
1.
2.
Category 1 is composed of shift tasks and on-call tasks crucial for the daily running of the experiment,
during critical periods such as LHC operation and pre-beam cosmic/test runs organized by Run
Coordination. (10%-15% of total OT)
Category 2 is all other operation tasks.
The practical implications of the new rules are the following.
- Each Institution must contribute to control room shifts and/or on-calls .
- The number of shifts or on-calls required from each Institution is calculated based on the
estimated number of shifts / on-calls for 2009 and each Institution's OT share.
- An Institution cannot avoid doing shifts or on-calls (Category 1) by contributing to another
type of Operation Task (i.e. Category 2).
The total number of working hours required for Category 1, to cover the run periods of 2009, has
been estimated to the best of our current knowledge, after consultation with the Project
Leaders and Activity Coordinators. This number of working hours is equivalent to 21000
eight-hour shifts. (i.e. 10 shifts/member, also 21000 shifts = 80FTE => 800FTE in total)
12/05/2009
OTS ATLAS Strategy @ JINR
10
Простые вычисления
JINR OTS (Category 1) – 363 смены на 2009 = 20 чел-месяцев пребывания в
ЦЕРНе – не страшно!? Но это лишь ~10% квоты ОТ => 14 FTE JINR total !!!
По результатам бесед с координаторами групп, «причастных» к ОТ работам:
TILE PL: 58 FTE-> JINR квота (3.6%) = 2.1 FTE ( 1 FTE = 260 дней )
33 смены + 18 “on-call” = 52 смены = 0.2 FTE
2.1 - 0.2 = 1.9 FTE [technical work, category 2]
x-check: в списке Ю.К. 6 чел = 5.5OT => 363/40.75x5.5 = 49 смен
Предварительно:
MUONs: 13 чел (Г.Ш.) => 8.25 OT => 73 смены + 2.5 FTE (cat 2)
TRT: 4 чел (?В.П.)=>1 OT => 9 смен + 0.3 FTE (cat 2)
LArg: 11 чел (А.Ч.)=> 5 OT => 45 смен + 1.5 FTE (cat 2)
TDAQ - ? чел (В.К.) ?
Проблема: 40 человек –> 20 OTS –> 200 смен + 7 FTE
7 FTE – справимся? А в 2010?
12/05/2009
OTS ATLAS Strategy @ JINR
11
Проблемы и предложения
Привести в порядок авторский список от ОИЯИ
Минимизировать участие сотрудников в работах, не
попавших в «OTS-перечень», сконцентрировав усилия на
«правильных» направлениях
Координаторам подсистем согласовать с Project Leader
график участия сотрудников в «Перечне»
Распределение ресурсов МНТС среди подсистем в ОИЯИ
проводить с учетом вклада группы в выполнение OTS
Физика ??!!!
12/05/2009
OTS ATLAS Strategy @ JINR
12