Page History

...

• 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 list 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)
• CURRENTLY OBSOLETE 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 APEX guis
• New PV Client viewer addition to the IRMIS Desktop New guis- THERE BUT NO LONGER FUNCTIONAL, AND DATA OUT OF DATE

#top

...

UI and DATABASE QUERYING

...

The gui paradigm is a set of “document types”; click the File/New Document menu for the list. Right now there are only 2 available for use at SLAC:

• idt::pv – Search for lists of PVs and IOCs. This is the most useful interface, and it comes up upon application startup.

...

Query results can be saved to an ascii file for further processing.

...

At SLAC, in a nutshell the PV and PV client crawlers update:

• all IRMIS tables in MCCQA. All IRMIS UIs query data on MCCQA: PV and IOC data, and PV Client data.
• 3 production tables on MCCO, which are used by other system – AIDA, BSA applications

...

FACET PV Crawler start
FACET PV Crawler finish
ALL_DATA_UPDATE start
LCLS PV Crawler start
LCLS PV Crawler finish
CD PV Crawler start
CD PV Crawler finish
PV Client Crawlers start
PV Client Crawlers finish
PV Client Cleanup start
PV Client Cleanup finish
DATA_VALIDATION start
DATA_VALIDATION finish
FACET DATA_VALIDATION start
FACET DATA_VALIDATION finish
ALL_DATA_UPDATE finish

...

some specific error checks:

...

1. Synchronization to MCCO that bypasses error checking
   • If you need to run the synchronization to MCCO even though IRMISDataValidation.pl failed (i.e. the LCLS crawler ran fine, but others failed), you can run a special version that bypasses the error checking, and runs the sync no matter what. It’s:
     /afs/slac/u/cd/jrock/jrock2/DBTEST/tools/irmis/cd_script/runSync-no-check.csh
2. Comment out code in IRMISDataValidation.pl
   • If the data validation needs to bypass a step, you can edit IRMISDataValidation.pl (see above tables for location) to remove or change a data validation step and enable the crawler jobs to complete. For example, if a problem with the PV client FACET crawlers causes the sync to MCCO not to run, you may want to simply remove the PV Client FACET crawler check from the data validation step.
3. Really worst case! Edit the MCCO tables manually
   • If the PV crawlers will not complete with a sync of good data to MCCO, and you decide to wait til November for me to fix it (this is fine – the PV crawler parser is a complicated piece of code that needs tender loving care and testing!), AND accelerator operations are affected by missing PVs in one of these tables, the tables can be updated manually with names that are needed to operate the machine:
     • aida_names (see Bob and Greg)
     • bsa_root_names (see Elie)
     • devices_and_attributes (see Elie)

...