IRMIS Workshop Report
D. A. Dohan,
SLAC EPICS Collaboration Meeting, Apr.26, 2005
Argonne National Laboratory
Office of Science
U.S. Department of Energy
A U.S. Department of Energy
Office of Science Laboratory
Operated by The University of Chicago
IRMIS - Introduction
•
Integrated Relational Model of Installed Systems
- ‘connection-based’ approach to modeling the accelerator and its
control system
- integrated ‘system’ coverage of software, hardware and
cabling
2
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Collaborative approach
• Goal is to provide re-useable relational database and
•
•
•
•
application frameworks
Inter-laboratory effort strengthens the underlying database and
application structures
The ‘EPICS’ model is used throughout – sophisticated high
level tools are developed, but the user always maintains the
ability to look ‘under the hood’
Site-neutral (and RDBMS agnostic)
Minimalist approach, locally extensible
3
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Collaborative approach
• A different programming paradigm (ask Bob and Marty)
•
•
- Programming for general audience
- More difficult short-term, but offset by leveraging group
resources
Initially, APS/SNS collaboration
Expression of interest from SLAC/LCLS ->
- Kickoff (extended) collaboration meeting at APS, Mar. 2005
4
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
IRMIS Collaboration Meeting
March 9-11, 2005
Advanced Photon Source, Argonne National Laboratory
Agenda and Presentations
Session A: Laboratory Perspectives
Presentations of each laboratory's requirements and understanding of the relational database
project. This discussion will provide a high level requirements/wish list.
1. N. Arnold, APS
2. D. Gurd, SNS
3. C. Sibley, SNS
4. R. Chestnut, SLAC
5. J. Stein, LCLS
6. T. Birke, BESSY
7. R. Keitel, TRIUMF
8. (D. Dohan for) DIAMOND
9. F.Bartlett FERMILAB
10. (D. Gurd for) SLS
11. C. Gerke, DESY
5
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Workshop Report (Cont’d)
Session B: IRMIS Overview
An overview of the present status of the IRMIS project at APS.
1. IRMIS-APS, outline, boundary conditions, issues - D. Dohan
2. RDBCore Schema for process variables, components (devices), and cables D. Dohan
3. IRMIS demonstration. N. Arnold
4. Discussion
6
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
IRMIS Components
PV Crawler
Data Miner
GUI
PHP/
XAL
RDB
•
•
•
Agreement on RDB schema
User interface technology(s)
Business rules
7
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Process Variable Entity Relation Diagram (ERD)
ioc
name
loaded in
record
name
type
dbd definition
is part of
field
type
value
db load line
8
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
PV Schema
9
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Component (hardware) schema
• Component:
- “ a constituent element, as of a system”… (Google)
- unit replaceable physical entity associated with the accelerator
- IO card, chassis, serial link, ..
- more primitive granularity than a ‘device’
- do not assign a high level physics ‘role’ to a component
- less subjective – no naming convention issue
- more on this later
- more geared to how the facility is assembled, rather than how it
functions.
10
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Component ERD
component type
name
description
form factor
manufacturer
feature sheet
function
is a
component
is controlled by
is housed by
name
logical number
physicaldescriptor
serial number
location
is powered by
///////
11
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Component types
• ‘Universal’ component type table
•
- core set, derived from the supported EPICS device types
Generalization to other hierarchies
- (e.g. accelerator, vacuum, ..)
12
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Component Schema (prototype)
13
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Cable ERD
component type
name
description
form factor
manufacturer
feature sheet
function
is a
component
name
logical number
physical descriptor
serial number
is part of
cable
port
name
connector type
is part of
pin
designator
signal name
pv name
color
label
is part of
conductor
pin_a connection
pin_b connection
14
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Cable database
•
•
•
•
•
Straightforward, once the component database is in place
Builds on theme of ‘connectivity’
End-to-end signal tracing
Cable does not need a name, color or other id
- the cable is a ‘connection’ between 2 pins
Completeness/consistency – examine installed system using
housing view
15
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Workshop Report (Cont’d)
Session C: Results, Progress & Plans
1. PV Crawler (with time stamp) - C. Saunders
2. Crawler extensions (proposed) - Andrew Johnson
3. EPICS databases using JERI - J. Patton, C. Foulkes, C. Sibley
4. Device Data and EpicsOra - DESY results - J. Rock, C. Gerke
16
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Workshop Report (Cont’d)
Session D: User Interface and Applications
1. PV Viewer and the CFW. - C. Saunders
2. Java RDB API and Object-Relational Modeling - C. Saunders
3. JERI directions in XAL. J. Patton
4. CFW Internal Multiple Documents - C. Saunders
5. XAL/CFW discussion - T. Pelaia, C. Saunders, C. Foulkes, etc.
6. What's next? - Ned Arnold
7. Epics V4 functional requirements report - Marty Kraimer
17
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
IRMIS PV Viewer
• Started out as PHP version of Oracle app-server viewer
• Decided that thin-clients not sufficient
• PV Viewer Foundation
- Java Swing
- Subset of XAL (later topic)
- Java database access layer (later topic)
18
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
IRMIS Java API
• Object-Relational Mapping (ORM)
•
- Bridges gap between relational data model and object-oriented
data model of applications
- This “gap” responsible for a significant amount of development
and maintenance hours
- ORM allows focus on application and data, not transforming
between the two models
Java ORM <==> Hibernate (Gavin King)
- LGPL license
- Development began in 2001
- Joined jboss.org in 2003, so commercial support and training
available
- Very popular, mature, with active support forums
- Excellent book “Hibernate in Action” (2005 - Bauer, King)
19
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
IRMIS Extensions
• Jeff Patton – work on ‘mining’ the pv database to integrate into
•
the detailed physics RDB at SNS
Coles Sibley
- use of JERI as a global DCT for managing distributed databases
20
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy
Session E: Open Workshop, Discussion
1. Extending RDBCore - SNS experience J. Patton
2. ORM and extending RDBCore - C. Saunders
3. PV Crawler How to - C. Saunders
4. PV Usage-by-Client how-to - C. Saunders
5. Capfast Device Instantiation from RDB - R. Keitel
6. Workshop summary
21
Pioneering
Science and
Technology
Office of Science
U.S. Department
of Energy