Introduction
LATC as a system doesn't provide an interface for manipulating the LATC xml as a system. Also, due to some features of the LATC compiler (LATC_parser), there are subtleties in attempting to simply "chain" different sets of XML together to create a correct description of the detector
Interface
The <foo> package contains a simple interface to an in-memory model of the LATC register space. A top level object, LATC_LAT, is provided which constitutes the top level interface to the LATC register hierarchy. This package contains several base classes: LATCComponent, LATCComponentDict, LATCRegister. The top level object is instantiated with a simple:
lat = LATC_LAT()
LATCComponent
The base class of all LATC component objects (such as LATC_LAT, LATC_TEM, LATC_AFE). LATCComponent objects contain sets of LATCComponents and sets of LATCRegisters. These sets may be empty.
All LATCComponent objects define the following methods:
name() Returns the component's name (a string)
components() Returns a dict of LATCComponent objects (may be empty).
Example: lat.components().keys() returns:
['AEM', 'TEM', 'GEM']
nComponents() Returns the length of the components() dict
registers() Returns a dict of LATCRegister objects (may be empty).
Example: lat.components()['AEM'].registers().keys() returns:
['trgseq', 'aem_configuration']
addComponent(name, component) Adds a component to the object.
+Not normally used by the user.+
addRegister(name, register) Adds a register to the object.
+Not normally used by the user.+
There also exists a more intuitive interface for LATCComponents. The user can reference the components and registers of a component by name. For example, the following two code snippets are equivalent:
aem1 = lat.components()['AEM'] aem2 = lat.AEM
trgseq1 = lat.AEM.registers()['trgseq'] trgseq2 = lat.AEM.trgseq
LATCComponentDict
LATCRegister