1 / 10

RDB and EPICS

Explore SLAC's history and implementations of EPICS and RDB systems, including the challenges faced and the plans for future development. Learn about the importance of secondary data management and the tools used for data analysis and generation. Discover SLAC's vision for a user-friendly, web-based UI with advanced features such as mass import, field-by-field editing, and customizable reports.

calvinc
Download Presentation

RDB and EPICS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RDB and EPICS The World According to SLAC Ideas and Implementations by: J. Rock, D. Rogind, S. Allison Ron Chestnut SLAC

  2. History of attempts • Old SLC system • Controls database is a collection of flat files • Cabling and maintenance databases not complete • PEP-II (mid ’90s) • Started late • Some EPICS (first at SLAC) • Odd collection with duct tape and wire • SPEAR • Small project; limited goals • LCLS • The chance to do it right; mostly EPICS Ron Chestnut SLAC

  3. SPEAR’s Way • DEC RDB (not ORACLE or MySQL) • IOCs report PV information on boot • PV information includes INP/OUT • Used to resolve mix ups Ron Chestnut SLAC

  4. LCLS Future • Looking for an RDB person • Naming convention meeting as we speak • Steve Lewis has joined from LLNL • Looking to do as much as possible • Central PV help just a beginning • Interested in our outcome Ron Chestnut SLAC

  5. ESD Software (our part) • Need good up-to-date list of PVs • Needs to include “other” system • Management of secondary data important • Archiver data • Channel Watcher data (save/restore) • Alarm Handler data Ron Chestnut SLAC

  6. Other System • Has EPICS version of name • Code to generate list worked once • Fairly static now Ron Chestnut SLAC

  7. Secondary Systems • Not just record names, but fields • Save/Restore might want .LOPR, for example • Ease of choosing names • Singly • In groups by pattern • Ease of setting parameters • Singly • In groups by pattern Ron Chestnut SLAC

  8. Notes from Judy • The UI we need: • Is convenient, easy to use, intuitive. • Is probably web-based. • Allows mass import of data • Allows field-by-field editing • Allows update of groups of things, with as many cut/paste/filldown/automatic options as possible • Has plenty of reports so we can easily see and communicate what we have in the db structure. • Maps easily into our normal view of the data (i.e. we need to easily identify and manipulate an epics .db or template, an alarm tree, a channel list.) • Has security (one or more levels) Ron Chestnut SLAC

  9. ESD RDB Use • Startup file crawling to produce • Old method for old system data • Tools to get secondary data right • Generation of secondary data files • LCLS may want .db generation too • We also have cable databases and, in principle, power drawings Ron Chestnut SLAC

  10. Tools • I like to talk about • Functionality • Tables • Reports • Generating configuration files • Task groups end up talking about • Which web tools? • Formal Oracle or ad-hoc generation Ron Chestnut SLAC

More Related