TupleEnv Migration
Overview
GenBuildEnv has been modified so that the tuple manager is no longer set in it. GenEnv still holds the tuple manager so that users do not need to change their access method to get the global tuple manager. The change has been made so that future tuple
managers can be added to the BaBar environment without modification of GenBuildEnv. All tuple managers will have their own environment
Tuple Environments
There are presently two tuple environments available: HbkTupleEnv (hbook) and DhpTupleEnv (distributed histogramming). These environments are available in the HbkTupleEnv and DhpTupleEnv packages, respectively. It is possible to have more
than one environment linked into an executable, but only one may be used at a time. The tuple manager is selected through tcl.
Linking Tuple Environments
Tuple environments should be linked in AppUserBuild. It should be placed before any module that uses the tuple manager.
Selecting Linked Tuple Environments
A particular tuple environment is selected by setting the 'ntupleFile' field in the talk-to to true. The following code selects an hbook tuple manager.
module talk HbkTupleEnv
ntupleFile set true
exit
FAQ
1. Should I remove the line
ntupleFile set false
from my GenBuildEnv talk-to?
Yes. ntupleFile is no longer a valid tcl parameter of GenBuildEnv.
Scott Metzler
metzler@caltech.edu
Last updated January 28, 1999
|
