-
Notifications
You must be signed in to change notification settings - Fork 2
Glossary
Access Control File. A file used by the Gateway which contains rules for access.
A messaging system that is used in a number of places throughout IBEX. Specifically, The Alarm Server and The IOC Log Server. See ActiveMQ Homepage for more information on the technology.
A CSS component that archives PV values. Implemented in IBEX in the Block Archive and Instrument Archive
A system to record PV values and reinstate them on startup of an IOC.
A method of changing the internal parameters of an emulator to mimic the behaviour of the actual device.
Slits used on each of the Muon instruments to control the neutron flux to the sample. Each "jaw" pivots on one edge, much like a door on a hinge.
Archives block values using the CSS Archive Engine and restarts whenever block definitions and/or the configuration changes.
Channel Access Laboratory. A library which enables EPICS and LabVIEW to communicate with each other.
Files which contain information about how pieces of sample environment equipment translate their readings into useful data. e.g. temperature sensor calibration files which enable translation from electrical measurements to temperature values.
A Protocol that defines how PV data is transferred between a server and client in an EPICS control system.
A device, usually a spinning disc of thick metal with a narrow slot, which allows selection of a particular energy range of neutrons by varying its speed.
Central Laser Facility. A department at RAL that also uses the EPICS control system.
Short meetings and presentations held within the group to discuss various aspects of the control system, or other related technologies.
A method for detecting collisions between moving beamline components by simulating the requested move beforehand. See Collision Detection Project for more information.
A Python script to highlight potential issues with current configurations when a new version of IBEX is installed.
A Python script to upgrade current configurations to be compatible with new versions of IBEX.
"Control System Studio is an Eclipse-based collection of tools to monitor and operate large scale control systems, such as the ones in the accelerator community. It's a product of the collaboration between different laboratories and universities."
A file containing the definition of PVs for a specific IOC using records.
An IDE and collection of tools for development of GUIs. CSS and the IBEX client are based on it.
A software implementation of hardware. Usually used to help write and test an IOC and OPI. See Emulating-Devices for more information.
Experimental Physics and Industrial Control System. A client/server control system using Channel Access as its communication protocol, forming a distributed real-time database of machine values (PVs). It is a collection of software tools collaboratively developed which can be integrated to provide a comprehensive and scalable control system.
A service that controls access between two or more networks.
An implementation of the OpenGenie scripting language in Python, or at least its commands specific to instrument control. Documentation here.
The new ISIS instrument control system. Primarily based on EPICS as the underlying technology.
Archives PV values using the CSS Archive Engine which have the ARCHIVE Field set in their Record.
InputOutputController. A process which reads and writes PVs. Often interfaces with hardware (e.g. sample environment equipment) to enable it to be controlled remotely.
LaboratoryVirtualInstrumentEngineeringWorkbench. A graphical programming language in which the device drivers for SECI are written.
Let's Write Intricate Simulators. A Python framework for producing and running emulators. See Emulating-Devices for more information.
A term used to describe an instrument which uses components from both the SECI and IBEX control systems. For example, an IOC wrapped with a VI on a SECI instrument (using CALab).
Slits used on the Muon front-end to control the neutron momentum to the three instruments.
A network-based control system. Some elements of it are used in the script server.
Operator Interface. A file used in CSS to enable a user to interact with an IOC graphically.
Process Variable. A named piece of data and the primary object of the Channel Access Protocol, often associated with a piece of equipment (e.g. status, readback, setpoint, parameter).
A file used by the Gateway which specifies which rules to follow that are defined in the ACF.
Used to define a PV in a DB File.
The version of IBEX to be deployed.
Sample Environment Control Interface. The current instrument control system, currently being replaced by IBEX. Written in C# and incorporating LabVIEW drivers for the sample environment equipment. User manual here.
An EPICS module to provide support for SNL files.
State Notation Language. A "C-like" language to enable State Machines to be written which can then be integrated into IOCs.
An software implementation of a motor axis to enable conversion between two coordinate systems.
A software design in which a program executes only its well-defined states with strict rules governing the changes between them. Written in SNL in this case.
A template for creating DB files using macros.
A tool for building and managing virtual machine environments. See homepage for more information.
A tool for running virtual machines.
Virtual Instrument. A LabVIEW program, usually a device driver for interacting with sample environment equipment.
An entire computer system running, without its own dedicated hardware, as software on a host computer. Each of the ISIS control machines (NDX...) is a virtual machine, as well as many other servers used as part of the development process.
Another messaging broker that is used in NICOS