Status of the HYDRA Oracle interface

by Ilse Koenig, GSI Oct 02, 2002

The following report gives an actual overview of the Oracle interface for all parameter containers in the analysis, which are initialized from an external source.

Almost all parameter containers have a working interface!

Categories of parameter containers

There exist five different categories of parameter containers, which differ by the version management, the table design and the interface.

1. Containers, which need no version management
The data for these containers are stored in one or several tables, which are filled once via SQL and then are not changed anymore.
Examples: Geometry information as number of wires in MDC layers or RICH pad geometry
 
2. Lookup tables, ideal geometry
The data are stored in a couple of tables and the analysis reads only a subset of the information.
The filling is done via sql or separate programs and not possible via the analysis. But once filled, only a few data change and not very often.
 
3. Containers with a small amount of data stored in data elements, which might change in future code releases
For such parameter containers exists a complete environment including a WebDB GUI for filling and public queries.
By deriving them from HParCond and implementing two additional functions in the parameter container, one gets the Oracle read and write interface for free (and also the ROOT and ASCII interface).
see Folder Params & Conds for WebDB GUI and documentation
 
4. Containers with data element, which will most propably not change in the future (stable code), with often a large amount of data and/or a tree-like strucure
By using a standard layout for these parameter containers in Oracle, it was possible to develop a read and write interface with cut-and-paste and to write a generic WebDB GUI for filling and public queries.
Typical examples: Calibration parameters
see Folder Tree-Organized Params for WebDB GUI and documentation
 
5. Containers used by Run Control
These containers have a slightly different version management.

Description of the table columns:

Container Class Class in the corresponding library holding the parameters
Code Status Shows, if the code of the parameter container is stable, if it will change within the next weeks or if it is still used by the actual HYDRA version.
Tables and Read Interface Shows, if already Oracle tables for the data and a read interface to the analysis exist
Write Interface Shows the kind of write interface for existing tables
Oracle Development By Person responsible for the Oracle development (server and client side applications)
Filling By Person responsible for the filling of the Oracle tables (green-colored:Preliminary)

Parameter containers in libBase

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HSpecGeomPar stable exist, including target versions and alignment separate program (ideal geometry) and sql (target setup)
target alignment stored via analysis macro + WebDB GUI		 I. Koenig I. Koenig (on request)

 

Parameter containers in libRich

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HRichAnalysisPar may change exist via analysis macro + WebDB GUI I. Koenig T. Christ
HRichCalPar stable exist via analysis macro + WebDB GUI T. Christ T. Christ
HRichCorrelatorPar may change exist via analysis macro + WebDB GUI I. Koenig T. Christ
HRichDigitisationPar may change exist via analysis macro + WebDB GUI I. Koenig T. Christ
HRichGeometryPar stable exist filled once via perl script T. Eberl T. Christ
HRichMappingPar stable exist filled once via perl script T. Eberl T. Christ
HRichThresholdPar stable exist filled via WebDB GUI for Run Control T. Christ T. Christ

 

Parameter containers in libTof

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HTofCalPar stable exist via analysis macro + WebDB GUI I. Koenig D. Zovinec
HTofDigiPar stable exist via analysis macro + WebDB GUI I. Koenig D. Zovinec
HTofGeomPar stable exist separate program(ideal geometry)
alignment stored via analysis macro + WebDB GUI		 I. Koenig I. Koenig (on request)
HTofLookup stable exist sql I. Koenig (I. Koenig)
HTofClusterFPar may change exist via analysis macro + WebDB GUI I. Koenig Dusan Zovinec

 

Parameter containers in libStart

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HStartCalPar stable exist via analysis macro + WebDB GUI I. Koenig Dusan Zovinec
HStartGeomPar stable exist separate program I. Koenig I. Koenig (on request)
HStartLookup stable exist sql I. Koenig (I. Koenig)
HStartSelfCoPar stable exist via analysis macro + WebDB GUI I. Koenig Dusan Zovinec

 

Parameter containers in libTofino

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HTofinoCalPar stable exist via analysis macro + WebDB GUI T. Wojcik (T. Wojcik)
HTofinoGeomPar stable exist separate program(ideal geometry)
alignment stored via analysis macro + WebDB GUI		 I. Koenig I. Koenig (on request)
HTofinoLookup stable exist sql I. Koenig (I. Koenig)
HTofinoShowerMap stable exist via analysis macro + WebDB GUI T. Wojcik (T. Wojcik)

 

Parameter containers in libShower

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HShowerCalPar stable exist via analysis macro + WebDB GUI T. Wojcik T. Wojcik
HShowerDigiDetPar stable exist via analysis macro + WebDB GUI T. Wojcik T. Wojcik
HShowerGeomPar stable exist separate program(ideal geometry)
alignment stored via analysis macro + WebDB GUI		 I. Koenig, T. Wojcik I. Koenig (on request)
HShowerHitFPar stable exist via analysis macro + WebDB GUI T. Wojcik T. Wojcik
HShowerUnpackParam stable exist via analysis macro + WebDB GUI T. Wojcik T. Wojcik
The parameter container HShowerGeometry does not need an Oracle interface, but will be filled in the future from parameter container HShowerGeomPar.

 

Parameter containers in libMdc

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HMdcCalParRaw stable exist via analysis macro + WebDB GUI I. Koenig J. Markert
HMdcCal2ParSim stable exist via analysis macro + WebDB GUI I. Koenig J. Markert
HMdcCellEff stable exist via analysis macro + WebDB GUI I. Koenig J. Markert
HMdcClosePairCut will change - via analysis macro + WebDB GUI I. Koenig J. Markert
HMdcDigitPar may change exist via analysis macro + WebDB GUI I. Koenig J. Markert
HMdcGeomPar stable exist separate program(ideal geometry)
alignment stored via analysis macro + WebDB GUI		 I. Koenig I. Koenig (on request)
HMdcGeomStruct stable exist sql I. Koenig J. Stroth
HMdcLayerGeomPar stable exist sql I. Koenig J. Markert
HMdcLookupGeom stable exist sql I. Koenig J. Stroth
HMdcLookupSubEvtId obsolete exist via analysis macro + WebDB GUI I. Koenig J. Markert
HMdcMboReadout stable exist sql I. Koenig J. Stroth
HMdcRawStruct stable exist sql I. Koenig J. Stroth
HMdcSetup may change exist via analysis macro + WebDB GUI I. Koenig J. Markert
HMdcTdcThreshold may change exist partially via analysis macro (+ later Run Control WebDB GUI) I. Koenig ?
HMdcTimeCut stable exist via analysis macro + WebDB GUI I. Koenig J. Markert

 

Parameter containers in libMdcTrackD

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HMdcTrackFitPar may change exist via analysis macro + WebDB GUI I. Koenig J. Markert

 

Parameter containers in libMdcTrackS

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HMdcHitFPar ? May use interface for conditions (read, write + GUI exist) ?
HMdcSegmentFPar ? May use interface for conditions (read, write + GUI exist) ?
The parameter containers MdcLeverArmGeometry, MdcModuleGeometry and MdcTargetGeometry can be filled in the analysis from the containers SpecGeomPar and MdcGeomPar and do not need an Oracle interface.

 

Parameter containers in libKick

Container Class Code Status Tables and Read Interface Write Interface Oracle Development By Filling By
HKickMatchPar stable ? exist via analysis macro + WebDB GUI I. Koenig M. Sanchez
HKickPlane obsolete exist via analysis macro + WebDB GUI I. Koenig M. Sanchez
HKickPlane2 stable exist via analysis macro + WebDB GUI I. Koenig M. Sanchez
HKickTrackFPar may change exist via analysis macro + WebDB GUI I. Koenig M. Sanchez
HRtTrackingPar ? May use interface for conditions (read, write + GUI exist) ?