Paper | Title | Page |
---|---|---|
TUPPC031 | Proteus: FRIB Configuration Database | 623 |
|
||
Distributed Information Services for Control Systems (DISCS) is a framework for developing high-level information systems for a Experimental Physics Facility. It comprises of a set of cooperating components. Each component of the system has a database, an API, and several applications. One of DISCS' core components is the Configuration Module. It is responsible for the management of devices, their layout, measurements, alignment, calibration, signals, and inventory. In this paper we describe FRIB's implementation of the Configuration Module - Proteus. We describe its architecture, database schema, web-based GUI, EPICS V4 and REST services, and Java/Python APIs. It has been developed as a product that other labs can download and use. It can be integrated with other independent systems. We describe the challenges to implementing such a system, our technology choices, and the lessons learnt. | ||
![]() |
Poster TUPPC031 [1.248 MB] | |
TUCOCB04 | EPICS Version 4 Progress Report | 956 |
|
||
EPICS Version 4 is the next major revision of the Experimental Physics and Industrial Control System, a widely used software framework for controls in large facilities, accelerators and telescopes. The primary goal of Version 4 is to improve support for scientific applications by augmenting the control-centered EPICS Version 3 with an architecture that allows building scientific services on top of it. Version 4 provides a new standardized wire protocol, support of structured types, and parametrized queries. The long-term plans also include a revision of the IOC core layer. The first set of services like directory, archive retrieval, and save set services aim to improve the current EPICS architecture and enable interoperability. The first services and applications are now being deployed in running facilities. We present the current status of EPICS V4, the interoperation of EPICS V3 and V4, and how to create services such as accelerator modelling, large database access, etc. These enable operators and physicists to write thin and powerful clients to support commissioning, beam studies and operations, and opens up the possibility of sharing applications between different facilities. | ||
![]() |
Slides TUCOCB04 [1.937 MB] | |
TUCOCB05 |
Device Definition and Composite Device Views on Top of the Flat EPICS Namespace | |
|
||
The EPICS (Experimental Physics and Industrial Control System) IOC (Input Output Controller) Core database represents a process on signal level, presenting a flat view of possibly complex devices. This signal level interface is an easily agreed upon common denominator, allowing drivers, signal records, and processes on these signals to be standardized across EPICS installations. However, it is also necessary to represent a device in its different aspects. Currently this requires a-priori knowledge of all individual channels that are included in a device by each client. This paper discusses device orientation based on the new EPICS Version 4 database and middle layer services along with the ecosystem to manage these views. | ||
![]() |
Slides TUCOCB05 [1.144 MB] | |
WECOBA02 | Distributed Information Services for Control Systems | 1000 |
|
||
During the design and construction of an experimental physics facility (EPF), a heterogeneous set of engineering disciplines, methods, and tools is used, making subsequent exploitation of data difficult. In this paper, we describe a framework (DISCS) for building high-level applications for commissioning, operation, and maintenance of an EPF that provides programmatic as well as graphical interfaces to its data and services. DISCS is a collaborative effort of BNL, FRIB, Cosylab, IHEP, and ESS. It is comprised of a set of cooperating services and applications, and manages data such as machine configuration, lattice, measurements, alignment, cables, machine state, inventory, operations, calibration, and design parameters. The services/applications include Channel Finder, Logbook, Traveler, Unit Conversion, Online Model, and Save-Restore. Each component of the system has a database, an API, and a set of applications. The services are accessed through REST and EPICS V4. We also discuss the challenges to developing database services in an environment where requirements continue to evolve and developers are distributed among different laboratories with different technology platforms. | ||
THCOAAB09 | Olog and Control System Studio: A Rich Logging Environment | 1074 |
|
||
Leveraging the features provided by Olog and Control System Studio, we have developed a logging environment which allows for the creation of rich log entries. These entries in addition to text and snapshots images store context which can comprise of information either from the control system (process variables) or other services (directory, ticketing, archiver). The client tools using this context provide the user the ability to launch various applications with their state initialized to match those while the entry was created. | ||
![]() |
Slides THCOAAB09 [1.673 MB] | |