Difference between revisions of "Slow Controls Shift"

Revision as of 22:46, 29 June 2014

Operator Interface Overview

The operator interface for Hall D control systems is based on Control System Studio or CSS. It allows the operator to use different important tools for EPICS from a single application. CSS is based on Eclipse RCP, and many features of CSS to the operator in the control room who already used Eclipse IDE will look and feel like Eclipse. For instance, there are Perspectives in CSS for running EPICS controls GUI, for defining and running strip charts for EPICS variables, for running an alarm handler. Most of the time the proper perspectives will already be open when a shift operator arrives at the shift or when an operator starts the EPICS controls or alarm screens.

Multiple control screens can be combined into a single CSS window as different tabs. Clicking on the tab in a view will activate the corresponding control screen. The tabs can be moved within a window or to a different window by clicking and dragging it into the desired location. One can also open a new empty window by selecting WindowNew Window menu item from the menu-bar of any of the CSS windows and drag the tab of one of the control screens into that new window.

To exit the current CSS session one needs to select FileExit from the menu-bar of any of the CSS windows. That will close all windows that belong to the same CSS session. When starting a new CSS instance all the window that were open just before exiting the CSS session will open. If one chooses to exit CSS by closing all CSS windows one-by-one using the window manager then only the window that was closed last will open when restarting CSS.

EPICS Control Screens

The EPICS display management system is based on Controls System Studio (CSS), namely on BOY package. To start the main control screen one needs to be logged into the gluon01 console machines in the Hall D control room and at the Linux prompt type:

|HDOPS> gluex_css 

This will bring up the controls screen configuration as it was just before the last control screen was closed from the previous CSS session.

Figure1. CSS BOY controls GUI for Hall D show the action bar on the left side and the Hall D tagger magnet power supply control screen on the right side.

The Hall D controls screens are organized in a hierarchy of subsystems and components. The examples of subsystems are FDC,CDC, FDC etc. And each subsytem can have components such us Voltages, Gas etc. If the GUI you are looking for is not displayed you can open it using the main action toolbar by clicking on the Top GUI->MainActionBar button on the toolbar of any of the CSS window. This should open a list of action buttons on the left side of the CSS GUI. Clicking on any of the button on the main action bar will pop up a new window with the corresponding control screen. You can open other control screens using the widgets on the newly open window for the selected component.

Data Browser / Striptooling

CSS has an integrated feature called Data Browser that allows users to display stripcharts within the same program where the controls screens are. As with the old EPICS StripTool, the CSS Data Browser allows one to create a file describing which EPICS variables need to be plotted in a give stripchart. Then one can open the desired file by a clicking a previously configured Data Browser file.

In addition, CSS Data Browser allows the user to create stripchart on the fly for the EPICS variable that one currently is monitoring on the CSS BOY screen. To start a stripchart, one needs to bring the mouse pointer to the desired EPICS variable and using righ-click select Process Variable Data Browser, This will open a stripchart in a separate tab in BOY and the time evolution of the EPICS variable will start being plotted. At this point there should be a visible toolbar on top of the strip chart that will allow the user to configure the properties of the stripchart, such as the axis limits, autoscrolling enable/disable, colors etc.

MYA Archiver

The archiving of Hall D EPICS variables is done using MYA archiver developed and maintained by the controls group of the JLAB accelerator divisions. At present time CSS and MYA are not integrated and the archived data from MYA cannot be displayed on CSS screens. In order to view the history of an EPICS variables one needs to:

1. Determine the name(s) of the EPICS variables that one wants to view,
2. Open the graphical viewer for MYA archiver called MyaViewer by typing at Linux prompt

   |HDOPS> MyaViewer

3. Setup the axes and traces on MyaViewer to view the history of desired EPICS variables. For instructions how to use MyaViewer please refer to the MyaViwer User's Guide.

One can also have the history of a given EPICS variable or time slice tables be printed on the screen using command line tools like myget, myData, mySampler. There is also a command line tool called myStats that allows to compute and printout the statistics on EPICS channel history stored in the MYA archiver.

Alarm Handler

The EPICS alarm system is based on Controls System Studio (CSS), namely BEAST. To start the main alarm screen one needs to be login to the gluon02 console machines in the Hall D control room and at the Linux prompt type:

|HDOPS> gluex_css 

This will bring up the screen configuration as it with was just before the last control screen was closed from the previous session. The program for the alarm handling is the same as for the display management, therefore one can use the buttons on the alarm browser to open the control GUIs appropriate for a alarm condition.

Figure 2. CSS screen in Alarm Perspective showing the Area Panel, Alarm Tree and Alarm Table.

The alarm perspective of CSS consists of three important views: Area Panel, Alarm Tree and Alarm Table. Area Panel shows which subsystem of GlueX detector is in a normal condition and which areas contain alarming EPICS variables. Alarm Tree view allows one to browse the alarm hierarchy three to find the variables that is in alarming state. Each node on the Alarm Tree has a menu that can be accessed by right-clicking on the node on the tree. The menu may have a selection options for acknowledging the alarm, for information and guidance, and for opening related displays. The shift personnel needs to read all information items marked by i on the left side to get more information about the event and to get guidance on the possible actions require to solve the problem.

Shift personnel should take actions suggested by the information buttons and after that acknowledge the alarm. That should move the corresponding line in the Alarm Table from the Unacknowledged Alarms panel to Acknowledged Alarms panel. The line will disappear from the Acknowledged Alarms panel in the i>Alarm Table</i> once the alarming condition goes away. If the same EPICS variable alarms again, the corresponding line in the Acknowledged Alarms will move to back to the Unacknowledged Alarms panel, in which case the shift personnel should repeat the actions suggested by the guidance unless the information screen suggest different set of action for repeated alarms.

Expert personnel

The individuals responsible for the Slow Controls are shown in following table. Problems with normal operation of the Slow Controls System should be referred to those individuals and any changes to their settings must be approved by them. Additional experts may be trained by the system owner and their name and date added to this table.