1. IRMIS Technical Details
8/6/2018
IRMIS Technical Details
D. A. Dohan,
SLAC EPICS Collaboration Meeting, Apr.26, 2005
Test

2. Workshop summary (excerpt)
8/6/2018
Workshop summary (excerpt)
Work breakdown – CA client crawlers
adl,alh – Janet Anderson, APS
SDDS – APS
EDL – J. Sinclair
SNC – R. Chestnut
CA archiver – SLAC
Channel Watcher – M. Zelazny
BURT s/r – T. Birke
CDEV – T. Birke
XAL – J.Patton
CA Security – APS
Test

3. (generic) PV_Client Schema
8/6/2018
(generic) PV_Client Schema
Test

4. 8/6/2018
PV Client Crawlers
Janet Anderson at APS has built the following PV client crawlers:
MEDM clients (.adl files)
Alarm Handler (.alh)
The Alarm Handler and MEDM crawlers have been tested at APS
These crawlers are installed in the tarball
Useful as ‘prototype’ crawler code example
Test

5. IOC Table generic IOC attribute table added to IRMIS::Base 8/6/2018
Test

6. PV Crawler Enhancements
8/6/2018
PV Crawler Enhancements
Crawler inserts directly into the RDB
‘Agnostic’ (Oracle sequences vs MySQL Autoincrement)
2 sets of DDL - template for different vendor RDBMS
PV Crawler - minor tweaks
PV schema has remained unchanged
100% ‘reach’ at APS
BESSY results:
Test

7. BESSY results: (email from Thomas Birke)
8/6/2018
BESSY results: ( from Thomas Birke)
Don Dohan wrote:
>> Participants in the IRMIS Collaboration meeting:
>> The IRMIS::Base web-site is now available at the EPICS site:
...
Congratulations to this first roll-out.I immediately downloaded this first version and got it running here at BESSY.
The result is: I successfully crawled all of our machine-group IOCs, adl-files and alh-files.
And the PV-viewer works just fine.
There were just little changes I had to make to get everything working (see attached diff-output). …
I just started writing the crawlers that I volunteered for (burt, cdev,
Are there plans to set up a forum/wiki/mailing-list for irmis-related questions/documentation/...?
Greetings from Berlin,you really did a good job.
Thomas
Test

8. Enhancements (cont’d)
8/6/2018
Enhancements (cont’d)
SNS PV crawler enhancements
save intermediate ‘path’ results of parsing cdCommands
should these be in IRMIS::Base – or are they site specific?
possibility: store this information as part of the ioc attr table?
XAL enhancements
Desktop
PV Client viewer
IOC Attribute viewer
Test

9. xal demo of crawler, and link to ioc_table
8/6/2018
xal demo of crawler, and link to ioc_table
Test

10. Get it Go to EPICS main page, then click on the IRMIS tab
8/6/2018
Get it
Go to EPICS main page, then click on the IRMIS tab
IRMIS ‘primer’
Copies of presentations at kickoff meeting
Tarball (with the above enhancements)
Extensive Readme
Site specific tailoring with site.build.properties file
PV crawler
XAL/CDW framework
Hibernate framework (subset)
PV viewer
IOC viewer
PV Client viewer
Test

11. Work in Progress - tying it all together
8/6/2018
Work in Progress - tying it all together
component type
name description form factor manufacturer feature sheet function
ioc attribute
type value
is a
ioc
name
is cpu
component
name logical number physical descriptor serial number
prop of
loaded in
record client
type file path
record
name type dbd definition
is part of
cable
color label
port
name connector type
client of
is part of
is part of
is part of
field
type value db load line
pin
designator signal name
conductor
pin_a connection pin_b connection
pv name
Test

12. PV <---> Cmpnt relationship
8/6/2018
PV <---> Cmpnt relationship
pv,dbd,st.cmd
dbior
dev support
hueristics
miner
Cmpnt
Editor
App
An additional source for information for the miner are the dbior reports. For example, these are helpful for extracting VXI chassis and MXI connection information.
The ultimate goal is to create and maintain a hierarchy of control cmpnts. A 'miner' process uses the st.cmd/pv/dbd datastore as the primary source of information. The cmpnt database must capture the hierarchy (ie connection) information, and the goal is to make it concurrent/consistent with the PV database
The expansion of the cmpnt table into master/detail port and pin tables is handled with cmpnt-type port/pin tempates
An externally maintained device support table provides rules that relate an IO string format to a particular component type.
To complete the scheme to include non-control cmpnts, and to resolve issues that the miner cannot determine strictly from the pv and ds tables, a user application is required to manually create and update a cmpnt-instance rules table. This user application replaces the cmpnt_table editor in vcct2.0, which adjusts the cmpnt table directly.
cmpnt; port; pin
The cmpnt;port;pin tables not only contain the component hierarchical information: - the pin <-> PV relationship is also established, relating EPICS records to hardware components
Test

13. If the miner is run at boot time:
8/6/2018
If the miner is run at boot time:
alert user if new records detected without corresponding entries in the component database.
increase the ‘exhaustive’ coverage of the hardware database as well as the PV-to-HW connections/links
Test

14. Future User/Reference Manual Tracked to the IRMIS release
8/6/2018
Future
User/Reference Manual
Tracked to the IRMIS release
Birke: Are there plans to set up a forum/wiki/mailing-list for irmis-related questions/documentation/...?
IRMIS Developers Session – ICALEPCS 2005?
Test