|   | - Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Plans for the US-CMS
- Remote Operations Center
- LHC@FNAL
- Erik Gottschalk
- Fermilab
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Overview
- Overview
- Remote operations for CMS & LHC
- What is LHC@FNAL?
- Planning
- Status
- Needs
- Summary
- LHC@FNAL website:
- http:
- //cd-amr
- gov/remop/remop
- .html
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- support both CMS and
- Goals for
- Joint CMS & LHC Remote Operations
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Remote Operations for US-CMS
- Remote Operations for US-CMS
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Remote operations for LHC
- Remote operations for LHC
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- What is LHC@FNAL?
- What is LHC@FNAL?
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- LHC@FNAL Location & Layout
-
- Operations
- Center
- (Phase 1)
- Office Space
- (Phase 2)
- Conference
- (Phase 1)
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- LHC@FNAL Construction
- LHC@FNAL Construction
- Status
- Status
- Construction is almost complete (photo taken Nov. 30, 2006).
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Planning for LHC@FNAL
- Planning for LHC@FNAL
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Current Status of LHC@FNAL
- Current Status of LHC@FNAL
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- An approach to restrict system access to authorized users
- What is a
- What is being
- What type of
- Requirements have been written
- Status:
- Code development in progress
- This is a
- CERN/Fermilab
- collaboration working on RBA for the LHC control system.
- Role Based Access (RBA)
-
- The software infrastructure for RBA is
- crucial for
- remote operations. Permissions can be setup to
- allow experts outside the control room to
- read or
- monitor a device safely
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- An approach to provide a snapshot of a graphical interface to remote users.
- What is a snapshot?
- What is the role of the service
- How will this work?
- Status:
- SSS is being developed at
- Fermilab
- for CMS, and
- may be applicable to the LHC.
- Screen Snapshot Service (SSS)
- Screen Snapshot Service (SSS)
- snapshots
- snapshots
- requests
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Future Capabilities for HEP
- Future Capabilities for HEP
- Presentation to OHEP, OFES, OASCR: Nov 7, 2006
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Summary
- Summary
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Additional Slides
- Additional Slides
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Site Visits
- Site Visits
- (TRECC)
- – West Chicago, Illinois
- – Hilo, Hawaii
- http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=425
-
- http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=505
- – Baltimore, Maryland
- – Livermore, California
- http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=532
- – San Diego, California
- – Oak Ridge, Tennessee
- http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=570
- – Argonne, Illinois
- – Darmstadt, Germany
- http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=622
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- LHC Sequencer
- LHC Sequencer
- Automates the very complex sequence of operations required to operate the LHC.
- Typical commands
- Set, get, check devices
- Wait for conditions
- Execute more complex operations
- Start regular programs
- Start plots
- Send data to shot log
- Step through commands
- Stops on error
- Allow restart at failed command
- Sequencer is used for:
- Normal operations
- Studies or special cases
- Working with CERN on requirements
- Explore existing implementations:
- FNAL, LEP, RHIC, NIF, HERA, SMI++
- http://cd-amr.fnal.gov/remop/Sequencer.htm
- This is a
- CERN/Fermilab
- collaboration working on the LHC Sequencer.
- LHC State Diagram
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- SDA is a software system for collecting, storing and analyzing data in terms
- of the stages of a complex process.
- SDA 1
- SDA 2
- SDA 2 for LHC
- This is a
- CERN/Fermilab
- collaboration.
- Sequenced Data Acquisition (SDA)
- Sequenced Data Acquisition (SDA)
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Identity Database (IDDB)
- Identity Database (IDDB)
- A lightweight user authentication framework.
- Motivation
- Identity Database
- Features
- IDDB is being developed at
- Fermilab
- for an electronic logbook for ILC.
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- LHC
- Beam Instrumentation Software
- Beam Instrumentation Software
- Dedicated applications for LHC beam instrumentation need to be written.
-
- application software for the LHC tune measurement system by providing
- panels for device configuration/setup and measurement displays:
- This is a
- CERN/Fermilab
- collaboration working on LHC beam instrumentation software.
- Shaping Collaboration 2006: Dec. 11 - 13, 2006
- Some assumptions (CMS
- Some assumptions (CMS
- operations)
- operations)
- For CMS
- For both CMS & LHC
|
Shaping Collaboration 2006: Dec. 11 - 13, 2006
1
Plans for the US-CMS
Back to top
Remote Operations Center
Back to top
LHC@FNAL
Back to top
Erik Gottschalk
Back to top
Fermilab
LHC at CERN - Geneva, Switzerland
Fermilab
- Batavia, Illinois
Shaping Collaboration 2006: Dec. 11 - 13, 2006
2
Overview
Back to top
Overview
•
Back to top
Remote operations for CMS & LHC
•
Back to top
What is LHC@FNAL?
•
Back to top
Planning
•
Back to top
Status
•
Back to top
Needs
•
Back to top
Summary
Back to top
LHC@FNAL website:
Back to top
http:
Back to top
//cd-amr
.
fnal
.
Back to top
gov/remop/remop
Back to top
.html
Shaping Collaboration 2006: Dec. 11 - 13, 2006
3
1.
Build a dedicated remote operations center to
support both CMS and
LHC
commissioning and operations.
Remote shifts for CMS
Enable CMS and LHC experts to access information in real time
Participate remotely in studies, commissioning, and operations
Training
for CMS & LARP (LHC Accelerator Research Program)
2.
Facilitate communication with CMS and LHC control rooms.
Call center
in the US - to help contact experts, answer questions.
T
est collaboration tools to improve communication
3.
Take advantage of a unique opportunity to have detector and accelerator
experts working together to solve problems.
4.
The
principal goal
is to enable people to participate in commissioning &
operations when they are unable to
travel (cost, family, visa issues, etc.).
Back to top
Goals for
Back to top
Joint CMS & LHC Remote Operations
Shaping Collaboration 2006: Dec. 11 - 13, 2006
4
Remote Operations for US-CMS
Back to top
Remote Operations for US-CMS
The remote operations center will serve the US-CMS community.
There are nearly 50 US institutions
in CMS and approximately 600 signing
physicists/engineers/guest scientists in
the US.
The LHC Physics Center (LPC) will provide
a place in the US for physics/analysis
discussions and meetings.
The
LHC@FNAL remote operations center
will provide a US hub for operations
activities.
The goal is to provide a facility
that will
enable CMS collaborators to take remote
shifts (for example, data-quality monitoring)
C
M
S
H
e
a
d
C
o
u
n
t
,
P
h
.
D
P
h
y
s
i
c
i
s
t
s
,
4
3
8
T
o
t
a
l
Boston Univ., Boston
Brown Univ., Providence
UC Davis, Davis
UCLA, Los Angeles
UC Riverside, Riverside
UC San Diego, La Jolla
UC Santa Barbara, Santa Barbara
California Inst. of Tech., Pasadena
Carnegie Mellon Univ., Pittsburgh
University of Colorado at Boulder, Boulder
Cornell University, Ithaca
Fairfield Univ., Fairfield
Fermi National Accelerator Lab., Batavia
Univ. of Florida, Gainesville
Florida International University, Miami
Florida State Univ., Tallahassee
Florida Inst. of Tech., Melbourne
Univ. of Illinois at Chicago, Chicago
The Univ. of Iowa, Iowa City
Iowa State Univ., Ames
Johns Hopkins Univ., Baltimore
The Univ. Of Kansas, Lawrence
Kansas State Univ., Manhattan
LLNL, Livermore
Univ. of Maryland, College Park
Mayaguez, Puerto Rico
Massachusetts Inst. of Tech., Cambridge
Univ. of Minnesota, Minneapolis
U
Fermilab
Shaping Collaboration 2006: Dec. 11 - 13, 2006
5
Remote operations for LHC
Back to top
Remote operations for LHC
CCC
Remote operations center for LHC:
•
provide
training before going to CERN
•
support LHC components built in US
•
participate remotely in LHC studies
•
access monitoring information
•
develop
software for LHC
CCC at CERN
LARP:
The US LHC Accelerator Research
Program (LARP) consists of four US
laboratories, BNL, FNAL, LBNL and SLAC, who
collaborate with CERN on the Large Hadron
Collider (LHC).
The LARP program enables U.S. accelerator
specialists to take an active role in the LHC
accelerator during its commissioning and
operations, and to be a major collaborator in
LHC performance upgrades.
Shaping Collaboration 2006: Dec. 11 - 13, 2006
6
What is LHC@FNAL?
Back to top
What is LHC@FNAL?
•
A Place
•
That provides access to information in a manner that is similar to
what is available in control rooms at CERN
•
Where members of the LHC community can participate remotely in
LHC and CMS activities
•
A Communications Conduit
•
Between CERN and members of the LHC community located in
North America
•
An Outreach tool
•
Visitors will be able to see current LHC activities
•
Visitors will be able to see how future international projects in particle
physics (such as the ILC) can benefit from active participation in
projects at remote locations.
Shaping Collaboration 2006: Dec. 11 - 13, 2006
7
LHC@FNAL Location & Layout
LHC@FNAL Location & Layout
Back to top
Back to top
Operations
Back to top
Center
Back to top
(Phase 1)
Back to top
Office Space
Back to top
(Phase 2)
Back to top
Conference
Room
Back to top
(Phase 1)
LHC@FNAL is located in
Fermilab
’
s
Wilson Hall (1
st
floor)
Shaping Collaboration 2006: Dec. 11 - 13, 2006
8
LHC@FNAL Construction
Back to top
LHC@FNAL Construction
Back to top
Status
Back to top
Status
Back to top
Construction is almost complete (photo taken Nov. 30, 2006).
Shaping Collaboration 2006: Dec. 11 - 13, 2006
9
•
We formed a task force with members from all
F
ermilab
divisions, university groups,
CMS, LARP, and LHC. The advisory board had an even broader base.
•
The LHC@FNAL task force developed a plan with input from many sources including
CMS, LHC, CDF, D0, MINOS, MiniBoone and Fusion Energy Sciences (FES).
•
We worked with CMS and US-CMS management, as well as members of LARP and the
LHC machine group at all steps in the process.
•
A detailed requirements document for LHC@FNAL was prepared and reviewed in 2005.
•
We visited 9 sites (e.g. Hubble, NIF, ESOC) to find out how other projects build control
rooms and do remote operations.
•
We have
a Collaboration Agreement between CERN and FNAL to work on LHC software
development.
•
We are engaged in construction, integration, software development and outreach activities.
The CMS Remote Operations Center (ROC) is already in operation.
•
The goal is to have LHC@FNAL ready for detector commissioning and startup of beam in
2007.
•
We plan to work with the ILC controls group to develop plans for ILC remote operations.
•
We
hope to collaborate with
the
Fusion
community (FES) to develop collaborative tools.
Together we are exploring connections to OSG
and other GRID projects.
Planning for LHC@FNAL
Back to top
Planning for LHC@FNAL
Shaping Collaboration 2006: Dec. 11 - 13, 2006
10
Current Status of LHC@FNAL
Back to top
Current Status of LHC@FNAL
•
Construction of a joint CMS and LHC remote operations center
(LHC@FNAL) is nearing completion - Spring 2007
•
LHC@FNAL Software (LAFS) development effort for LHC
accelerator software has been successfully launched. This
is a collaboration between CERN and
Fermilab
.
•
Software development for LHC, CMS, ILC:
1.
Role Based Access for LHC (RBA)
2.
LHC Sequencer
3.
Sequenced Data Acquisition (SDA)
4.
Screen Snapshot Service (SSS)
5.
Identity Database (IDDB)
6.
LHC Beam Instrumentation Software
7.
Electronic Logbook for ILC
Shaping Collaboration 2006: Dec. 11 - 13, 2006
11
An approach to restrict system access to authorized users
.
Back to top
What is a
ROLE
?
•
A role is a job function within an organization.
•
Examples: LHC Operator, SPS Operator, RF Expert, PC Expert, Developer,
…
•
A role is a set of access permissions for a device class/property group
•
Roles are defined by the security policy
•
A user may assume several roles
Back to top
What is being
ACCESSED
?
•
Physical devices (power converters, collimators, quadrupoles, etc.)
•
Logical devices (emittance, state variable)
Back to top
What type of
ACCESS
?
•
Read: the value of a device once
•
Monitor: the device continuously
•
Write/set: the value of a device
Back to top
Requirements have been written
•
Authentication
•
Authorization
Back to top
Status:
Back to top
Code development in progress
Back to top
This is a
Back to top
CERN/Fermilab
Back to top
collaboration working on RBA for the LHC control system.
Back to top
Role Based Access (RBA)
Role Based Access (RBA)
Back to top
Back to top
The software infrastructure for RBA is
Back to top
crucial
for
Back to top
remote operations. Permissions can be setup to
Back to top
allow experts outside the control room to
Back to top
read or
Back to top
monitor a device safely
.
Shaping Collaboration 2006: Dec. 11 - 13, 2006
12
An approach to provide a snapshot of a graphical interface to remote users.
Back to top
What is a snapshot?
•
An image copy of a graphical user interface at a particular instance in time.
•
Examples: DAQ system buffer display, operator control program,
…
•
A view-only image, so there is no danger of accidental user input.
•
Initially envisioned for application GUIs but could be expanded to desktops.
Back to top
What is the role of the service
?
•
Receives and tracks the snapshots from the monitored applications.
•
Caches the snapshots for short periods of time.
•
Serves the snapshots to requesting applications/users.
•
Prevents access from unauthorized applications/users.
•
Acts as a gateway to private network applications for public network users.
Back to top
How will this work?
•
Applications capture and send snapshots to the service provider in the background.
•
Users would access snapshots using a web browser.
Back to top
Status:
•
The capturing of snapshots from Java applications has been demonstrated.
•
The transfer of snapshots
is
being investigated.
Back to top
SSS is being developed at
Back to top
Fermilab
Back to top
for CMS, and
Back to top
may be applicable to the LHC.
Back to top
Screen Snapshot Service (SSS)
Back to top
Screen Snapshot Service (SSS)
Monitored
Application(s)
Snapshot
Service
Web
Browser(s)
snapshots
snapshots
requests
Shaping Collaboration 2006: Dec. 11 - 13, 2006
13
Future Capabilities for HEP
Back to top
Future Capabilities for HEP
Although we are making good progress on the development of remote operations
capabilities for high-energy physics (HEP), there is
room for improvement
.
Better
collaborative tools
will contribute significantly to our ability to participate in LHC,
and plan for
the International Linear
Collider
(ILC).
We can benefit from improved
communications tools
by
•
exploiting convergence of
telecom and internet technologies (e.g. SIP),
•
deploying integrated communications (voice, video, messaging, email, data)
•
and advanced directory services for identification, location and scheduling.
We can benefit from a
true
collaborative control room
by
•
deploying distributed, shared
display walls for remote collaborative visualization.
We can benefit from security enhancements (role-aware & easier-to-use security).
Some of these needs are already being addressed by Fusion (FES) community.
Presentation to OHEP, OFES, OASCR: Nov 7, 2006
14
Approaches to OASCR
Fusion Energy Sciences
High Energy Physics
New
FusionGrid
Computational
Services
MDSplus
Collaborative Displays
Federated Security
Role Based Access
Sequenced Data Acquisition (SDA)
SIP Communication Tools
LHC Sequencer
LHC Beam
Instrumentation
Identity Database (IDDB)
Electronic
Logbook
Screen Snapshot Service (SSS)
FusionGrid
Parallel
Computational
Services
Substantial Overlap Between FES and HEP Needs
Shaping Collaboration 2006: Dec. 11 - 13, 2006
15
Summary
Back to top
Summary
•
The goals of LHC@FNAL are to support both CMS and LHC
commissioning and operations, and to take advantage of an
opportunity to have detector and accelerator experts work together.
•
The LHC@FNAL remote operations center is under construction,
and will be completed by
Spring 2007.
•
A collaborative effort between CERN and
Fermilab
to develop LHC
accelerator software has been successfully launched.
•
There is an urgent need for better collaborative tools to improve our
ability to work on the LHC.
•
There is substantial overlap between the needs for High Energy
Physics (HEP) and Fusion Energy Sciences (FES) for collaborative
tools.
Shaping Collaboration 2006: Dec. 11 - 13, 2006
16
Additional Slides
Back to top
Additional Slides
Shaping Collaboration 2006: Dec. 11 - 13, 2006
17
Site Visits
Back to top
Site Visits
•
Technology Research, Education, and Commercialization Center
Back to top
(TRECC)
Back to top
–
West Chicago, Illinois
(Aug. 25, 2005)
•
Gemini Project remote control room
Back to top
–
Hilo, Hawaii
(Sept. 20, 2005)
•
Back to top
http://docdb.fnal.gov/C