1. This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC0000661. Michigan State University designs and establishes FRIB as a DOE Office of Science National User Facility in support of the mission of the Office of Nuclear Physics. Paul Chu Save/Compare/Restore (SCORE)

2.  Originally developed by J. Galambos at SNS  Technologies Used: Java »Client application »Database configuration tool (JERI) Relational database Java Channel Access XAL framework (GUI and menu utilities)  Main functions Save machine settings and their associated readbacks Compare saved settings to the live machine values Restore the machine to a set of saved values  SLAC/LCLS also uses a modified SCORE Background P. Chu, Controls Database Collaboration, 18 Nov 2011, Slide 2

3.  Needs a database to store data captured. (XML) files will work with some work around but not recommended  SNS SCORE database schema 3 main tables How Does It Work? P. Chu, Controls Database Collaboration, 18 Nov 2011, Slide 3

4.  SNS JERI -- A GUI configuration tool for changing the PV list – run as Java Web Start. Can select PVs from signal table with filtering To get full functional JERI, need additional tables  LCLS Oracle APEX Web interface Load a formatted Excel file SCORE Database Configuration P. Chu, Controls Database Collaboration, 18 Nov 2011, Slide 4

5.  XAL based GUI SNS LCLS SCORE GUI P. Chu, Controls Database Collaboration, 18 Nov 2011, Slide 5

6. LCLS SCORE Schema P. Chu, Controls Database Collaboration, 18 Nov 2011, Slide 6

7.  Tables (5 for SCORE data, 3 for PV list configuration file upload) SCORE_SNAPSHOT_GRP_SGNL SCORE_SNAPSHOT_SGNL SCORE_SNAPSHOT_GRP SCORE_SUBSYSTEMS (new) SYST (new) SCORE_UPLOAD_LOG (new) SCORE_UPLOAD (new) CHECK_FLE_LOG (new)  5 joined tables for faster query, 2 tables for QA purpose  The 3 tables for file upload are not needed for SNS – SNS uses JERI tool LCLS SCORE Schema Details [1] P. Chu, Controls Database Collaboration, 18 Nov 2011, Slide 7

8. Table Name# Cols# IndexesSizeTablespace CHECK_FILE_LOG5364KSCORE_DATA CHECK_FILE_ROW20186MSCORE_DATA LATEST_BSA_REGION_SIGNALS7164KSCORE_DATA SCORE_SNAPSHOT_GRP733MSCORE_DATA SCORE_SNAPSHOT_GRP_JN2117MSCORE_DATA SCORE_SNAPSHOT_GRP_SGNL14132MSCORE_DATA SCORE_SNAPSHOT_GRP_SGNL_JN34110MSCORE_DATA SCORE_SNAPSHOT_SGNL78904MSCORE_DATA SCORE_SNAPSHOT_SGNL_JN191584MSCORE_DATA SCORE_SUBSYSTEMS8264KSCORE_DATA SCORE_SUBSYSTEMS_JN24164KSCORE_DATA SCORE_UPLOAD882MSCORE_DATA SCORE_UPLOAD_JN2414MSCORE_DATA SCORE_UPLOAD_LOG7564KSCORE_DATA SYST4164KSCORE_DATA LCLS SCORE Schema Details [2] P. Chu, Controls Database Collaboration, 18 Nov 2011, Slide 8

9.  PV validation check with IRMIS signals  At application level Restore with LEM (Linac Energy Manager) energy scaled GUI modification »Table columns rearranged »better color coded LCLS SCORE Additional Feature P. Chu, Controls Database Collaboration, 18 Nov 2011, Slide 9

10.  IRMIS Save/Restore database schema should be relatively straightforward based on SCORE Links to Component, Lattice and other sub-schemas should be considered »Lattice need not have its own snapshot of the machine for model replay  Service and GUI are next A new GUI application similar to JERI and APEX for PV list configuration »Should be an IRMIS package Data access API for clients Energy scaling should be in a different service provider with input from Model Server Other features in Save/Restore Service »Periodic snapshot Path Forward P. Chu, Controls Database Collaboration, 18 Nov 2011, Slide 10