...
Archiver PV query APEX application
Lists of archived PVs by IOC application, IOC.
https://seal.slac.stanford.edu/apex/mccqa/f?p=259:8
Discontinued: IOC Info query application
This is a jsp web application containing data about IOCs and applications, and their configurations. It is no longer maintained.
https://seal.slac.stanford.edu/IRMISQueries/
IOC list report (run nightly)
This html report is created nightly by the LCLS PV Crawler
http://mccas0.slac.stanford.edu/crawler/ioc_report.html
...
- CURR_PVS view has all currently loaded PVs
Discontinued: IOC Info query application
This is a jsp web application containing data about IOCs and applications, and their configurations. It is no longer maintained.
https://seal.slac.stanford.edu/IRMISQueries/
...
OPERATIONAL and SUPPORT DETAILS
...
| Note | ||
|---|---|---|
| ||
The IRMIS GUI and the JSP application still use uses hardcoded passwords. These This must be changed “manually” at every password change cycle. |
...
The PV crawler is run once for each IOC boot directory structure. The LCLS PV crawler (runLCLSPVCrawlerLx.bash) runs the crawler only once. It is and FACET PV crawlers are separate to enable it them to be run on a different schedule and different host which can see the LCLS production IOC directories for these systems. Also, the LCLS crawler code has been modified to be LCLS-specific; it is a different version than the SLAC PV crawler.
...
- LCLS side: laci on lcls-daemon2: runLCLSPVcrawlerLx.bash: crawls LCLS PVs and creates lcls-specific tables (bsa_root_names, devices_and_attributes), copies LCLS client config files to dir where CD client crawlers can see them.
- LCLS side: laci on lcls-daemon2: caget4curr_ioc_device.bash: does cagets to populate curr_ioc_devices for the IOC Info APEX app. Run separately from the crawlers because cagets can hang unexpectedly – they are best done in an isolated script!
- CD side: laci on lcls-prod01: runAllCDCrawlers.csh: runs CD PV crawler and all client crawlers, data validation, and sync to MCCO.
- FACET side: flaci on facet-daemon2daemon1: runFACETPVcrawlerLx.bash: crawls FACET PVs, copies FACET client config files to dir where CD client crawlers can see them.
...
description | cvs root | production directory tree root | details |
|---|---|---|---|
IRMIS software | SLAC code has diverged from the original collaboration version, and LCLS IRMIS code has diverged from the main SLAC code (i.e. we have 2 different version of the IRMIS PV crawler.) | CD: |
|
CD scripts | For ease and clarity, the CD scripts are also in the LCLS CVS repository under | /afs/slac/g/cd/tools/irmis |
|
LCLS scripts | /afs/slac/g/lcls/cvs | /usr/local/lcls/tools/irmis |
|
FACET scripts | These scripts share the LCLS repository (different names so they don’t collide with LCLS scripts) | /usr/local/facet/tools/irmis |
|
...
- 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
- 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:
- 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 crawlers causes the sync to MCCO not to run, you may want to simply remove the PV Client crawler check from the data validation step.
- 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)
- 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:
...