...
- Data source for PV names for AIDA (nightly cron jobs)
- Data source for element EPICS device names for LCLS_INFRASTRUCTURE (nightly cron jobs)
- PV and PV Client lists and data (IRMIS gui)
- IOC configuration and parameters (IOC Info APEX: https://seal.slac.stanford.edu/apex/mccqa/f?p=104:8)
- IOC and application configuration data (IOC Info jsp app: https://seal.slac.stanford.edu/IRMISQueries )
- EPICS camdmp application (APEX app: https://seal.slac.stanford.edu/apex/mccqa/f?p=103:4)
- NO LONGER VALID DUE TO THE NEW ARCHIVER ENGINE Archiver PV search application (APEX app: https://seal.slac.stanford.edu/apex/mccqa/f?p=259:8 )
- Lists of IOCs and their PV populations (web page: http://mccas0.slac.stanford.edu/crawler/ioc_report.html)
- ad hoc queries using TOAD, sqlplus, pl/sql, perl scripts, or other db query tool.
- IRMIS crawler logs, with duplicate PV reports: http://www.slac.stanford.edu/grp/lcls/controls/sysGroup/report
...
- IOC boot syntax adaptations in the PV crawler and IOC Info crawler (adopted from SNS) and schema
- Special application-oriented tables in the IRMIS schema, and their population scripts (for example for EPICS camdmp and the archiver PV viewer app)
- Crawl of IOC.dbDumpRecord, which will slowly supercede crawling of st.cmd files.
- Addition of config file tree structure crawling in the ALH crawler
- New crawlers for Channel Watcher and Channel Archiver
- New PV Client viewer addition to the IRMIS Desktop
- New guis
...
EPICS camdmp APEX application
Various reports listing PVs and their module and channel connections.
https://seal.slac.stanford.edu/apex/mccqa/f?p=103:4Archiver PV query APEX application
Lists of archived PVs by IOC application, IOC.
https://seal.slac.stanford.edu/apex/mccqa/f?p=259:8
IOC list report (run nightly)
...
- MCCQA IRMISDB schema: Production for all gui’s and applications. Contains data populated nightly by perl crawler scripts from production IOC configuration files. Data validation is done following each load.
- MCCO IRMISDB schema: contains production data, currently for 3 tables only: bsa_root_names, devices_and_attributes, curr_pvs. MCCQA data is copied to MCCO once it has been validated. So MCCO is as close as possible to pristine data at all times.
- SLACDEVcontains the 3 schemas which are used for developing, IRMISDB schema: sandbox testing and staging new features before release to production on MCCQA (see accounts below)
- IRMISDB – sandbox for all kinds of development, data sifting, etc. Not refreshed from prod, or not very often.
- IRMISDB_TEST – testing for application implementation. Refreshed from prod at the start of a development project. IRMISDB_STAGE – staging for testing completed applications against recently-refreshed production dataMCCODEV IRMISDB schema: can be used for staging a release. Currently, the schema and data are out of date. Refresh from prod, then apply SLACDEV changes to use for staging.
- SLACPROD IRMISDB schema: this is obsolete, but will ; however, it is referenced in some scripts or other and has to be kept around for awhile (6 months?) as a starting point in case the DB migration goes awry somehowuntil the scripts are pointed elsewhere. See Poonam, Elie, Mike Z. for details.
Other Oracle accounts
- IRMIS_RO – read-only account (not used much yet – but available)
- IOC_MGMT – created for earlier IOC info project with a member of the EPICS group which is not active at the moment- new ioc info work is being done using IRMISDB
For passwords see Judy Rock or Poonam Pandey or Elie Grunhaus .(or use getPwd)
As of September 15, all crawler-related shell scripts and perl scripts use Oracle Wallet to get the latest Oracle password. Oracle passwords must be changed every 6 months, and is coordinated and implemented by Poonam Pandey.
| Note | ||
|---|---|---|
| ||
The IRMIS GUI uses hardcoded passwords. This must be changed “manually” at every password change cycle. See below for detailed procedure. |
Database structure
see schema diagram below. (this diagram excludes the EPICS camdmp structure, which is documented separately here: <url will be supplied>)
...
The PV crawler is run once for each IOC boot directory structure. The LCLS and FACET PV crawlers are separate to enable them to be run on a different schedule and different host which can see the production IOC directories for these systems. Also, the the same code, that in the LCLS directory structure. The LCLS crawler code has been modified to be LCLSproduction-specific; it is a different version than the SLAC PV crawler.
...