ICALEPCS2015 - List of Authors (Veseli, S.)

Paper	Title	Page
WEA3O02	Recent Advancements and Deployments of EPICS Version 4	589
	G.R. White, M.V. Shankar SLAC, Menlo Park, California, USA A. Arkilic, L.R. Dalesio, M.A. Davidsaver, M.R. Kraimer, N. Malitsky, B.S. Martins BNL, Upton, Long Island, New York, USA S.M. Hartman, K.-U. Kasemir ORNL, Oak Ridge, Tennessee, USA D.G. Hickin DLS, Oxfordshire, United Kingdom A.N. Johnson, S. Veseli ANL, Argonne, Ilinois, USA T. Korhonen ESS, Lund, Sweden R. Lange ITER Organization, St. Paul lez Durance, France M. Sekoranja Cosylab, Ljubljana, Slovenia G. Shen FRIB, East Lansing, Michigan, USA
	EPICS version 4 is a set of software modules that add to the base of the EPICS toolkit for advanced control systems. Version 4 adds the possibility of process variable values of structured data, an introspection interface for dynamic typing plus some standard types, high-performance streaming, and a new front-end processing database for managing complex data I/O. A synchronous RPC-style facility has also been added so that the EPICS environment supports service-oriented architecture. We introduce EPICS and the new features of version 4. Then we describe selected deployments, particularly for high-throughput experiment data transport, experiment data management, beam dynamics and infrastructure data.
	Slides WEA3O02 [2.413 MB]
Export •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

WEPGF116	PvaPy: Python API for EPICS PV Access	970
	S. Veseli ANL, Argonne, Ilinois, USA
	As the number of sites deploying and adopting EPICS Version 4 grows, so does the need to support PV Access from multiple languages. Especially important are the widely used scripting languages that tend to reduce both software development time and the learning curve for new users. In this paper we describe PvaPy, a Python API for the EPICS PV Access protocol and its accompanying structured data API. Rather than implementing the protocol itself in Python, PvaPy wraps the existing EPICS Version 4 C++ libraries using the Boost. Python framework. This approach allows us to benefit from the existing code base and functionality, and to significantly reduce the Python API development effort. PvaPy objects are based on Python dictionaries and provide users with the ability to access even the most complex of PV Data structures in a relatively straightforward way. Its interfaces are easy to use, and include support for advanced EPICS Version 4 features such as implementation of client and server Remote Procedure Calls (RPC).
	Poster WEPGF116 [0.742 MB]
Export •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

THHC2O02	Component Database for APS Upgrade	1127
	S. Veseli, N.D. Arnold, J. Carwardine, G. Decker, D.P. Jarosz, N. Schwarz ANL, Argonne, Ilinois, USA
	The Advanced Photon Source Upgrade (APS-U) project will replace the existing APS storage ring with a multi-bend achromat (MBA) lattice to provide extreme transverse coherence and extreme brightness x-rays to its users. As the time to replace the existing storage ring accelerator is of critical concern, an aggressive one-year removal/installation/testing period is being planned. To aid in the management of the thousands of components to be installed in such a short time, the Component Database (CDB) application is being developed with the purpose to identify, document, track, locate, and organize components in a central database. Three major domains are being addressed: Component definitions (which together make up an exhaustive "Component Catalog"), Designs (groupings of components to create subsystems), and Component Instances ('Inventory'). Relationships between the major domains offer additional "system knowledge" to be captured that will be leveraged with future tools and applications. It is imperative to provide sub-system engineers with a functional application early in the machine design cycle. Topics discussed in this paper include the initial design and deployment of CDB, as well as future development plans.
	Slides THHC2O02 [1.957 MB]
Export •	reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

Paper

Title

Page

Recent Advancements and Deployments of EPICS Version 4

589

G.R. White, M.V. Shankar
SLAC, Menlo Park, California, USA
A. Arkilic, L.R. Dalesio, M.A. Davidsaver, M.R. Kraimer, N. Malitsky, B.S. Martins
BNL, Upton, Long Island, New York, USA
S.M. Hartman, K.-U. Kasemir
ORNL, Oak Ridge, Tennessee, USA
D.G. Hickin
DLS, Oxfordshire, United Kingdom
A.N. Johnson, S. Veseli
ANL, Argonne, Ilinois, USA
T. Korhonen
ESS, Lund, Sweden
R. Lange
ITER Organization, St. Paul lez Durance, France
M. Sekoranja
Cosylab, Ljubljana, Slovenia
G. Shen
FRIB, East Lansing, Michigan, USA

EPICS version 4 is a set of software modules that add to the base of the EPICS toolkit for advanced control systems. Version 4 adds the possibility of process variable values of structured data, an introspection interface for dynamic typing plus some standard types, high-performance streaming, and a new front-end processing database for managing complex data I/O. A synchronous RPC-style facility has also been added so that the EPICS environment supports service-oriented architecture. We introduce EPICS and the new features of version 4. Then we describe selected deployments, particularly for high-throughput experiment data transport, experiment data management, beam dynamics and infrastructure data.

Slides WEA3O02 [2.413 MB]

Export •

reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

WEPGF116

PvaPy: Python API for EPICS PV Access

970

S. Veseli
ANL, Argonne, Ilinois, USA

As the number of sites deploying and adopting EPICS Version 4 grows, so does the need to support PV Access from multiple languages. Especially important are the widely used scripting languages that tend to reduce both software development time and the learning curve for new users. In this paper we describe PvaPy, a Python API for the EPICS PV Access protocol and its accompanying structured data API. Rather than implementing the protocol itself in Python, PvaPy wraps the existing EPICS Version 4 C++ libraries using the Boost. Python framework. This approach allows us to benefit from the existing code base and functionality, and to significantly reduce the Python API development effort. PvaPy objects are based on Python dictionaries and provide users with the ability to access even the most complex of PV Data structures in a relatively straightforward way. Its interfaces are easy to use, and include support for advanced EPICS Version 4 features such as implementation of client and server Remote Procedure Calls (RPC).

Poster WEPGF116 [0.742 MB]

Export •

reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)

THHC2O02

Component Database for APS Upgrade

1127

S. Veseli, N.D. Arnold, J. Carwardine, G. Decker, D.P. Jarosz, N. Schwarz
ANL, Argonne, Ilinois, USA

The Advanced Photon Source Upgrade (APS-U) project will replace the existing APS storage ring with a multi-bend achromat (MBA) lattice to provide extreme transverse coherence and extreme brightness x-rays to its users. As the time to replace the existing storage ring accelerator is of critical concern, an aggressive one-year removal/installation/testing period is being planned. To aid in the management of the thousands of components to be installed in such a short time, the Component Database (CDB) application is being developed with the purpose to identify, document, track, locate, and organize components in a central database. Three major domains are being addressed: Component definitions (which together make up an exhaustive "Component Catalog"), Designs (groupings of components to create subsystems), and Component Instances ('Inventory'). Relationships between the major domains offer additional "system knowledge" to be captured that will be leveraged with future tools and applications. It is imperative to provide sub-system engineers with a functional application early in the machine design cycle. Topics discussed in this paper include the initial design and deployment of CDB, as well as future development plans.

Slides THHC2O02 [1.957 MB]

Export •

reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)