Package org.epics.pvmanager.data

Support for control system types.

See:
          Description

Interface Summary
Alarm Alarm information.
Array<T> Multi dimensional array, which can be used for waveforms or more rich data.
Display Limit and unit information needed for display and control.
Enum Metadata for enumerations.
MultiScalar<T extends Scalar> Multi channel array.
Scalar<T> Basic type definition for all scalar types.
Statistics Basic type for statistical information of numeric types.
Time Time information.
VDouble Scalar double with alarm, timestamp, display and control information.
VDoubleArray  
VEnum Scalar enum with alarm and timestamp.
VEnumArray  
VInt Scalar integer with alarm, timestamp, display and control information.
VIntArray  
VMultiDouble Multi channel array of VDouble.
VMultiEnum  
VMultiInt  
VMultiString  
VStatistics Statistics for double with alarm, timestamp and display information.
VString Scalar string with alarm and timestamp.
VStringArray  
VTable A table.
 

Class Summary
ExpressionLanguage PVManager expression language support for EPICS types.
ValueFactory Factory class for all concrete implementation of the types.
 

Enum Summary
AlarmSeverity Enumeration for severity of alarm.
 

Annotation Types Summary
Metadata Annotation to flag which fields are considered part of the metadata.
 

Package org.epics.pvmanager.data Description

Support for control system types.

This package contains the data definitions for all the EPICS types. These are in terms of Java interfaces so that each data source can map directly to their own structure.

The interfaces starting with Dbr represent actual types that can be taken by a data source. The other interfaces represent atomic elements that can be treated separately so that generic support can be written against them (i.e. one can write support for alarms regardless of the actual type).

TODO: alarm acknowledgment? Not in this package... TODO: histograms for statistics on enums? TODO: what about toString? Java default? Only value? Full information? TODO: equals and hashcodes? Each object different? Compare on the data only? if we do, what about compare?



Copyright © 2010. All Rights Reserved.