SLAC National Accelerator Laboratory


MEME Basic Architecture

Draft, November 12, 2014

Authors:
Greg White, SLAC IDEA

Abstract

This document gives the most basic block diagram and network elements of the MAD EPICS Matlab Environment (MEME).

MEME is a system of accelerator physics applications and data servers for online beam optimization and data mining LCLS and LCLS-II, plus associated Matlab APIs. MEME is built on top of EPICS Version 4.

Table of Contents


Introduction to MEME

MAD EPICS Matlab Environment, MEME, is a collection of Matlab applications and data services built on top of EPICS, for control and optimization of the LCLS system of accelerators.

Figure 1: Schematic of the technology stack of the MAD EPICS Matlab Environment.

MEME is built on top of EPICS, specifically EPICS v4, and as such uses both the classic CA communications protocol, and the new "PV Access" protocol introduced in v4. So, the first releases related to MEME are of EPICS V4. MEME services are hosted at the DMZ level, so EPICS v4 must be installed both on production, and on AFS.

A small set of data services help physicists get non-control data required for high level applications.

The initial set of MEME data services

Optics
The Optics Service makes available Twiss and R-matrix from the database, as uploaded from the model application (not described here). For instance, a user can get the 6x6 transfer matrix from a quadrupole to a wire scanner. /dd>
Relational Database (RDB)
The Relational Database Service can get any general data from SLAC's Oracle system. For example it can get data on how a given magnet is powered, and whether it's in BCS, MPS or PPS subsystems.

In the future, not part of this release phase, shall be these services in development by ICD:

Directory Service
The Directory Service serves data on the controls process variable (PV) names, element names, and their hierarchy within the accelerator. Importantly, its source data for the hierarchy is the MAD Deck itself. Consequently, it is a simple matter for a user to get all of the values of some system of devices, like BPM offsets, or data from another of the MEME services - for whole sections of the machine, as defined in the deck
Archive
The Archive service serves past PV data, given a time interval start and end time.
Model
In future, it's envisaged that a second modelling related service will run, offering continuously updated optics of the extant accelerator.

Network Diagram

The following network diagram shows the location of the production and development servers. The production services will be hosted on a single computer (lcls-prod01) on the DMZ network. Those production services will be used by control room applications and physics users in their offices. Additionally a mirror set of development instances will be hosted, always on, on lcls-dev2. Those are used only for software development.

Figure 1: Computers and networks of initial MEME services, showing that there wil be a single system of production services serving both control room and office data requirements, plus a second system for software development.

Greg White, SLAC
Last modified: Wed Mar 11 17:39:32 CET 2015