Paper | Title | Page |
---|---|---|
MOPPC155 | NSLS II Middlelayer Services | 467 |
|
||
Funding: Work supported under auspices of the U.S. Department of Energy under Contract No. DE-AC02-98CH10886 with Brookhaven Science Associates, LLC, and in part by the DOE Contract DE-AC02-76SF00515 A service oriented architecture has been designed for NSLS II project for its beam commissioning and daily operation. Middle layer services have been actively developing, and some of them have been deployed into NSLS II control network to support our beam commissioning. The services are majorly based on 2 technologies, which are web-service/RESTful and EPICS V4 respectively. The services provides functions to take machine status snapshot, convert magnet setting between different unit system, or serve lattice information and simulation results. This paper presents the latest status of services development at NSLS II project, and our future development plan. |
||
![]() |
Poster MOPPC155 [2.079 MB] | |
TUPPC133 | Graphene: A Java Library for Real-Time Scientific Graphs | 901 |
|
||
While there are a number of open source charting library available in Java, none of them seem to be suitable for real time scientific data, such as the one coming from control systems. Common shortcomings include: inadequate performance, too entangled with other scientific packages, concrete data object (which require copy operations), designed for small datasets, required running UI to produce any graph. Graphene is our effort to produce graphs that are suitable for scientific publishing, can be created without UI (e.g. in a web server), work on data defined through interfaces that allow no copy processing in a real time pipeline and are produced with adequate performance. The graphs are then integrated using pvmanager within Control System Studio. | ||
![]() |
Poster TUPPC133 [0.502 MB] | |
TUPPC134 | Pvmanager: A Java Library for Real-Time Data Processing | 903 |
|
||
Increasingly becoming the standard connection layer in Control System Studio, pvmanager is a Java library that allows to create well behaved applications that process real time data, such as the one coming from a control system. It takes care of the caching, queuing, rate decoupling and throttling, connection sharing, data aggregation and all the other details needed to make an application robust. Its fluent API allows to specify the detail for each pipeline declaratively in a compact way. | ||
![]() |
Poster TUPPC134 [0.518 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] | |