1 / 8

IRMIS @ SLAC

Summary of the SLAC PV Crawler project including current status, plans for future development, SLAC-specific configurations, and usage of PV Viewer and batch reporting tools.

armstrongj
Télécharger la présentation

IRMIS @ SLAC

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. IRMIS @ SLAC Judy Rock SLAC 6/12/06

  2. !!! Thanks Claude and Don !!!

  3. IRMIS @ SLAC Summary • PV part of the schema only so far • Running: • PV Crawler since late 2005 • SEQ crawler • ALH crawler • Use PV Viewer and batch reporting • Plans for client config data and UI

  4. PV Crawler operation • Currently run once daily • SLAC-specific: • 3 different boot directory structures: run PV crawler 3 times for distinct sets of PVs • mirror Oracle-inaccessible boot directory to accessible location

  5. PV Crawler operation cont. • SLAC-specific, continued: • a few PV Crawler code tweaks with new env.properties file defining some slac-specific variables

  6. IRMIS Uses so far • PV Viewer for ad hoc database queries • PV Crawler reports EPICS database and template errors (-: • Data source for EPICS PV names for SLAC legacy control system • formerly dbLoadTemplate and dbReport on hardcoded lists of template files

  7. Plans • Run other PV client crawlers • Write/acquire Channel Archiver, Channel Watcher, dm2k and edm crawlers, others? • Install and integrate new component schema and viewer. • Develop viewer for PV client data

  8. Plans cont. • Extend schema to include config info for clients (e.g. flags, masks) • Read/write UI to maintain client configuration data, with generation of client config files (e.g. .alhConfig) • Would like a nice integrated UI. Will work from existing UIs developed by Claude and Co.

More Related