IRMIS Status

1
IRMIS Status EPICS 2009 Vancouver D. A. Dohan
2
Outline

• IRMIS hardware model
• cable/cable run
• channel list
• Equipment Inventory System
• RDB Domain separation
• High Level Application support
• lattice
• TRACY3/Elegant deck generator
• Process Variable Introspection
• pv groups
• pv aliases
• pv to channel
• IRMIS Code-a-thon
• PHP integration/support
• PHP work at APS
• PHP work at MSU/NSCL
• Architecture
• Future Plans

3
General observations

• RDB services are now considered a basic
  requirement for machine commissioning and
  operation support for High Level Applications
• proven availability of RDB services (hardware
  redundancy, load balancing, )
• shift in emphasis in IRMIS from descriptive to
  prescriptive
• the RDB schema and application suite continues to
  evolve as each application is rolled out
• requires an agile programming environment, where
  enhancements to the relational database can be
  made to an operational production system

4
IRMIS Overview
Lattice
Software (Global EPICS/PV Logic)
Hardware (component model)
Cables (Signals)
5
IRMIS Hardware Model Enhancements - separation
of the Component Installation from the Equipment
Inventory System - allows the installation
of infrastructure items that are not typical EIS
inventory items (rooms, racks, etc). - allows
multiple configurations (e.g. ion source, RF,
beamlines, etc) - the EIS contains items that
are not installed (spares, stock) - completely
separate applications (domain separation between
the installer and the EIS). - The
installation schema has strict validation
requirements the data can be independently
verified by inspection, whereas the EIS will
generally be unverifiable. (domain specific
validation requirements)
6
Parts Assembly Instructions
7
Equipment Inventory (History)
8
IRMIS Loose Coupling and Domain Separation

• The Equipment Inventory System is a separate RDB
  sub-domain, (it contains the foreign key to the
  main install table)
• The EIS has a separate schema and application
  development prototyping cycle. Each site has
  different EIS requirements (maintenance cycles,
  certification, calibration, )
• The install schema has stringent data integrity
  requirements database constraints, application
  business rules, test routines, external
  validation.
• The install schema provides the basis for a
  number of domains/applications that are dependent
  on the install data consistency.
• Additional sub-domains loosely coupled to the
  install domain
• lattice
• cable
• pvchannel

9
IRMIS Domain Separation Separate schema and
application development cycles
10
IRMIS Lattice Schema

• The IRMIS lattice schema provides a 4th hierarchy
  the accelerator hierarchy
• a hierarchy of nested sequences, ultimately
  containing the target beam delivery components
  (magnets, bpms, )
• IRMIS Data Service Layer support

11
IRMIS lattice schema
12
IRMIS Overview
Lattice
Software (Global EPICS/PV Logic)
Hardware (component model)
Cables (Signals)
I/O Channels
13
(No Transcript)
14
(No Transcript)
15

• IRMIS codeathon, Apr. 21-23
• Participants Debby Quock (ANL), Eric Berryman
  (National Superconducting Cyclotron Lab), Guobao
  Shen, Don Dohan, Bob Dalesio and Gabriele
  Carcassi (BNL).
• Highlights
• Using WebStart to support GUIs on Macs
• Import/export lattice information in Tracy-3
  format
• Fixed a couple of problems in the UI (including
  a concurrency bug that caused applications to
  fail with large datasets)
• Improvements in the Java API (findByFieldName
  for components and saving the XML of a
  transaction)

16
IRMIS codeathon, Apr. 21-23, (contd) We had a
number of planning/design discussions, especially
to coordinate future developments at ANL and at
NSCL. NSCL has already built PHP-based
inventory tools on top of IRMIS3. Given the
interest in PHP support, we are going to
investigate how to take some of the work done at
NSCL and turn it into a PHP library bundled in
the IRMIS3 distribution. We also need some kind
of issue tracker to manage the todo
list. (G.C.)
17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
IRMIS Overview New Developments
Lattice
Software (Global EPICS/PV Logic)
Hardware (component model)
Cables (Signals)
I/O Channels
PV Introspection
Prescriptive PV
21
IRMIS Plans

• PV introspection
• centralized location of EPICS and physics name
  aliases
• central management of pv service applications
  (archiver, alarm handler, SCORE, machine
  snapshot, etc)

22
PV introspection (development)
23
Accelerator RDB editors/applications - Loose
Coupling
HLA
crawler
lattice, snapshot
pv
IRMIS Data Services
presc-pv
EIS
Cosylab VDCT? tdct?
NSCL/ NSLS/ CIDB
24
(No Transcript)
25
IRMIS Wish List

• Link expander
• expand link component network topology (network
  virtual circuit, etc)

ioc
ethernet link
network attached device
network attached device
26
IRMIS plans/wishlist

• PV introspection
• centralized location of EPICS and physics name
  aliases
• central management of pv service applications
  (archiver, alarm handler, SCORE, machine
  snapshot, etc)
• capture cable signal information Petri-net
  analysis
• end-to-end signal tracing (e.g. timing signal)
• drill down for cable database application

27
Accelerator RDB editors/applications Technology
Selection
HLA
crawler
lattice, snapshot
pv
IRMIS Data Services
presc-pv
EIS
Cosylab VDCT
NSCL/ NSLS/ CIDB