Difference between revisions of "RF Controls and Software Infrastructure Oct 19 2017"
(Created page with " Software Infrastructure Meeting Notes – 18 October 2017 Software Notes This document does not describe the entire architecture, just draws attention to a few points. (Wesle...") |
|||
| Line 1: | Line 1: | ||
Software Infrastructure Meeting Notes – 18 October 2017 | Software Infrastructure Meeting Notes – 18 October 2017 | ||
| + | |||
Software Notes | Software Notes | ||
| + | |||
This document does not describe the entire architecture, just draws attention to a few points. (Wesley is planning a drawing of the entire architecture.) | This document does not describe the entire architecture, just draws attention to a few points. (Wesley is planning a drawing of the entire architecture.) | ||
| + | |||
One goal is to mimic the LCLS-II software environment as closely as possible. LERF will use 64-bit RHEL6 servers that emulate the SLAC file system. | One goal is to mimic the LCLS-II software environment as closely as possible. LERF will use 64-bit RHEL6 servers that emulate the SLAC file system. | ||
| + | |||
The EPICS IOCs will run on RHEL6-64 and LinuxRT operating systems. | The EPICS IOCs will run on RHEL6-64 and LinuxRT operating systems. | ||
| + | |||
EPICS version R3-15 will be used. | EPICS version R3-15 will be used. | ||
| + | |||
The ALH alarm system will be used. The configuration of this might be tricky | The ALH alarm system will be used. The configuration of this might be tricky | ||
| + | |||
The SLAC GitHub site will be the repository for the SLAC application software. | The SLAC GitHub site will be the repository for the SLAC application software. | ||
| + | |||
The JLab archiver will be used. | The JLab archiver will be used. | ||
| + | |||
We will use the LERF electronic logbook for data-taking. SLAC would like the ability to attach screenshots, files, etc. | We will use the LERF electronic logbook for data-taking. SLAC would like the ability to attach screenshots, files, etc. | ||
| − | Responsibilities | + | |
| + | |||
| + | == Responsibilities == | ||
| + | |||
SLAC Provides | SLAC Provides | ||
| + | |||
• Documentation and instructions for installation and configuration of SLAC-like EPICS software architecture, including: | • Documentation and instructions for installation and configuration of SLAC-like EPICS software architecture, including: | ||
| + | |||
o Versions of EPICS base, extensions, modules, etc. | o Versions of EPICS base, extensions, modules, etc. | ||
| + | |||
o Alarm Handler utility configuration | o Alarm Handler utility configuration | ||
| + | |||
o SLAC-specific build instructions for EPICS | o SLAC-specific build instructions for EPICS | ||
o LinuxRT infrastructure | o LinuxRT infrastructure | ||
Revision as of 19:31, 19 October 2017
Software Infrastructure Meeting Notes – 18 October 2017
Software Notes
This document does not describe the entire architecture, just draws attention to a few points. (Wesley is planning a drawing of the entire architecture.)
One goal is to mimic the LCLS-II software environment as closely as possible. LERF will use 64-bit RHEL6 servers that emulate the SLAC file system.
The EPICS IOCs will run on RHEL6-64 and LinuxRT operating systems.
EPICS version R3-15 will be used.
The ALH alarm system will be used. The configuration of this might be tricky
The SLAC GitHub site will be the repository for the SLAC application software.
The JLab archiver will be used.
We will use the LERF electronic logbook for data-taking. SLAC would like the ability to attach screenshots, files, etc.
Responsibilities
SLAC Provides
• Documentation and instructions for installation and configuration of SLAC-like EPICS software architecture, including:
o Versions of EPICS base, extensions, modules, etc.
o Alarm Handler utility configuration
o SLAC-specific build instructions for EPICS o LinuxRT infrastructure o Support to JLab staff as needed o and more… • Rough estimate of number of channels to be archived • Later, list of PVs to archive with deadband parameter • List of users who need remote access JLab Provides • The SLAC-like software infrastructure, including servers and network • Remote access to the LERF VLAN and servers • Access to SLAC GitHub from LERF • Terminal server for console access to the two RF CPUs