discs - distributed information services for control systems eric berryman frib-nscl, east lansing,...
TRANSCRIPT
DISCS - Distributed Information Services for Control Systems
Eric Berryman
FRIB-NSCL,East Lansing, Michigan, USA.
Overview
2
Problem Vision Collaborators Architecture Development Methodology
Domains & Modules Current Status Conclusion
The Problem
Problem Statement
4
Disparate and Heterogeneous Systems Used During The Design, Construction, Commissioning, Operation, and Maintenance of an Experimental Physics Facility (EPF)
No Way to Share Data
Problem Illustration
5
DISCS
DISCS Vision
7
To Develop Collaborating Services That Any Experimental Physics Facility Can Easily Configure, Use, And Extend For Its Design, Commissioning, Operation, And Maintenance
DISCS – Scope I
8
DISCS – Scope II
9
DISCS Collaborators
10
Brookhaven National Lab, USA Cosylab, Slovenia European Spallation Source, Sweden Facility for Rare Isotope Beam, USA Institute for High Energy Physics,
China
DISCS Challenges
11
Integration Of Myriad Databases Multiple Teams From Different Labs Geographically Dispersed Collaboration Labs Have Different Priorities Labs Have Different Schedules Labs Have Different Technology Platforms Differing Software-engineering Processes
DISCS – Architecture
DISCS Architecture
13
Application layer• Operator interfaces• High-level applications• Libraries
Service layer• Access to data• Programming Interface
Data layer• Managed data• Instrument data• No direct access
EPICS V4 - DISCS
14
Development Methodology
15
I – Divide Entire System Is Broken Down Into Smaller Loosely-
coupled Parts Or Domains II – Develop
Each Domain Is Implemented Independently III – Frame
Application Programming Interfaces Are Developed IV – Integrate
Domains Are Integrated
Check Paper For Details
DISCS Modules
16
Module: An Implementation Of A Domain
DISCS - Status
DISCS Status
18
Domain Team Status
Configuration FRIB,ESS,Cosylab
In Production At FRIB
Cables FRIB Under Development
eTraveler FRIB In Production At FRIB
Lattice-Model BNL, FRIB, ESS Prototypes At FRIB and BNL
Logbook BNL, FRIB In Production At FRIB & BNL.
Inventory FRIB Under Development
Naming System
FRIB In Production at FRIB
Operations FRIB Under Development
Save/Restore BNL In Production at BNL
Security ESS, Cosylab, FRIB
Under Development
Signals (PV) BNL In Production at BNL, FRIB (ChannelFinder)
Unit Conversion
BNL Under Development
DISCS - Screenshots
20
Logbook: Web Client
21
Logbook: CSS Client
22
Logbook: pyOlog
23
eTraveler – List of Travelers
24
eTraveler – DevicesIntegration with Configuration Module
25
Configuration: Component Tree
26
Configuration: Magnet Measurement
27
Configuration: Live Signals (PV)
28
Screenshots – Configuration Module
29
Configuration: Component Relationships
30
Configuration: Component Relationships
31
Configuration: Lattice
32
Lattice-Model: Beamlines
33
Naming Convention – Name Elements
Name Elements Are Parts of A Name: System, Subsystem, Device Type etc
34
Naming Convention – Submit Requests
Submit Requests to Add, Modify, or Delete Name Elements
35
Naming Convention – Process Requests
36
Naming Convention - Reports
37
Screenshots – Unit Conversion
38
Screenshots – Save/Restore
39
Cables – Normal View
40
Cables – Manager View
41
Cables - Types
Conclusion
42
Described An Information Services Framework For Accelerator Design, Commissioning, Operation, And Maintenance
Discussed Challenges To Collaborative Development
Acknowledgements: IRMIS, Control System Studio, EPICS V4, ChannelFinder,
and PVManager Teams
DISCS Website: http://discs.openepics.org
43
“Nine people can’t make a baby in a month.”
– Fred Brooks, The Mythical Man-Month
“Computer science is no more about computers than astronomy is about telescopes”
– Edsger W Dijkstra
Thank you!