SLAC	PEP-II
BABAR
SLAC<->RAL

HEPIC	E,S & H	Databases	PDG	HEP preprints
Organization	Detector	Computing	Physics	Documentation
Personnel	Glossary	Sitemap	Search	Hypernews

Run-time configuration

Table 3: TCL configuration scripts.

TCL script	Description
btaMini.tcl	Deletes ``AllPath'', creates ``Everything'' path, sources the core configuration script BetaMiniSequences/BetaMiniSequence.tcl, and sources a BetaMiniPatches.tcl script.
btaMiniPhysics.tcl	Sources btaMini.tcl.tcl and adds basic physics lists defined in BetaMiniSequences/BetaMiniPhysicsSequence.tcl.

The BetaMiniUser package was designed from the outset to be configured via TCL, rather than environment parameters. As noted earlier, BetaMiniOptions.tcl file sets the configuration parameters to reasonable default values. These defaults may be overridden by issuing

	set tclvar <value>

in a TCL ``snippet'' file containing job-dependent TCL- and module parameters (the job-independent parameters should be specified in the underlying analysis tcl file). The snippet file

• sets the BetaMiniUser configuration TCL parameters described in Table 2
• defines the collections to read and specifies the number of events to process, and
• sets the analysis module parameters.

This snippet file will source something like BetaMiniUser/MyMiniAnalysis.tcl which in turn sources one of the configuration scripts listed in Table 3, adds the analysis module to the Everything path and runs the through the desired number of events. The examples in Section 3 illustrate how this is done. The basic steps for creating a snippet file are listed below.

• set TCL variables: The TCL variables described in Table 2 should be set as desired. Any parameter appearing in Table 2 which is not explicitly set will be assigned a default value as shown.
  
• Specify input collections: There are two ways to specify the input collections. The first way is to talk to the appropriate XxxInputEvent module, where Xxx is Kan or Bdb, e.g.,

          talkto KanEventInput {
             collection add collection1
             collection add collection2
             ...
          }
  

  where the name of the XxxEventInput module must be consistent with the value (Kan or Bdb) of the BetaMiniReadPersistence variable.

  The second way to specify input collections is to issue the TCL command

          lappend inputList collection1 collection2 ...
  

  The advantage of this method is that it is persistence-independent. The type of input persistence is specified solely by the BetaMiniReadPersistence variable.
• Configure analysis module(s) as follows

          path append Everything AModule
          path append Everything BModule
          ...
          module talk AModule
             Avar1 set <value>
             Avar2 set <value>
             ...
          exit
          module talk BModule
             Bvar1 set <value>
             Bvar2 set <value>
             ...
          exit
          ...
  

  Notes:

  • The beginJob methods of all modules instantiated in the AppUserBuild will be invoked unless the command

            module disable <moduleName>
    

    is issued.
  • All modules except the module(s) of interest should be disabled here as well.
• Read events from the specified input collections. In the examples, this is handled by setting the TCL parameter NEvent to the desired number of events. If this parameter is not specified, all events in all input collections will be read.
• Source a BetaMiniUser configuration TCL script: sourceFoundFile one of the example analysis scripts described in the next section, e.g., BetaMiniUser/MyMiniAnalysis.tcl. This script will typically source one of the BetaMiniUser scripts described in Table 3.