Title: IRMIS: A Descriptive Approach
1IRMIS A Descriptive Approach
- Ned Arnold, APS
- April 27, 2005
The submitted manuscript has been created by the
University of Chicago as Operator of Argonne
National Laboratory (Argonne) under Contract
No. W-31-109-ENG-38 with the U.S. Department of
Energy. The U.S. Government retains for itself,
and others acting on its behalf, a paid-up,
nonexclusive, irrevocable worldwide license in
said article to reproduce, prepare derivative
works, distribute copies to the public, and
perform publicly and display publicly, by or on
behalf of the Government.
2RDB Workshop March 9-11, 2005
- Institutions Represented
- APS, SNS, SLAC, LCLS, FERMI (D0), TRIUMF, BESSY,
DESY - New Terminology
- Grand Unified Relational Database
- GURD
- System for Tabulating Engineering Installation
Nomenclature - STEIN
- dialect agnosticity
- Descriptive vs. Prescriptive Relational Databases
3What We Want to
- Track
- Process Variables
- Devices
- Engineering Device Properties (scale,
calibrations data, serial , base addr) - Physics Device Properties
- Signals
- Components
- Cables
- Configuration Files
- Control Software
- Software Versions
- Impact of PV changes on clients
- and all the relationships between them!
4What We Want to
- Generate
- Templates
- Databases
- Faceplate Displays
- Configuration Files for other tools (alh,
save/restore, MPS, etc) - Web-based reports
- Fault Analysis
- Cause/Effect Analysis
5RDB Workshop March 9-11, 2005
- Aggregate Requirements
- Basically, we want ltthe databasegt to do
everything thought of in the past and anything to
be thought of in the future (LCLS) - Implementation seems to be quite a challenge
- impossible to get IOC engineers to import the
data - History of attempts
- not maintainable (after a few years)
- but we still need it!
- ltholygt grail the object of an extended or
difficult quest
6IRMIS (APS)
Data Mining Scripts
As Built Control System
Heuristic Rules
Manual Input
7What we require a new system to support (BESSY)
- Generation of
- .db, .substitution, .template
- All other kinds of configuration dataALH,
Archiver, Save/Restore, Orbit-Correction,other
yet unknown applications - Different views to the same dataset
RDB
8Relational Database (TRIUMF)
Web Application
RDB devices
Perl Tools
EPICS configuration files
9dbd files ? epicsOra ? db file (DESY)
10Database System (D0)
Template Definitions
Template Generators
Record Field Definitions
Instance Creation
DB Creation
Oracle Hardware Database
Record Extract
Template Extract
List of Records For IOC
Template Generators For IOC
IOC Id
11Is there any room for collaboration?
- Start with EPICS specific information
- Things every EPICS site has to deal with
- Partition tables between common and extended
(site-specific items) - Provide exhaustive descriptive tables and
crawlers to populate the data allowing sites to
continue with their own prescriptive schemes
while benefiting from an as built repository - Co-existence
- Take whats best from each
- Ensure SQL dialect agnosticity
12Co-existence
Partition the problem
Common Descriptive Tables
Site-specific Tables for everything else
Site-specific Descriptive Tables
13IRMISBase 1.0
IRMISBase 1.0 Release Date April 27, 2005
PV Crawler
PV Crawler
PV Table
IOC Table
IOC Table Editor
adl Crawler
alh Crawler
IOC Attribute Table
PV-Usage-by-Client Table
edl Crawler
archiver Crawler
CA Security Crawler
Save/Restore Crawler
Sequencer Crawler
rdbBase 1.1
Component/Device Table
XAL Crawler
StripTool Config Crawler
Cable Table
sdds Crawler
14Summary
- Two approaches
- Descriptive (describes what is installed)
- Prescriptive (defines what is to be installed)
- The ultimate solution is probably a combination
of approaches - An exhaustive descriptive solution is easier
- Having an exhaustive descriptive solution may
alleviate some difficult requirements on a
prescriptive solution (e.g. history) - We feel that everyone can benefit from common
exhaustive descriptive approach and that it is
complementary to the prescriptive efforts being
undertaken. - IRMISBase 1.0 is available
15An Opportunity