Moose: BaBar Simulation Application

Last Updated: 16 March 2006
Shahram Rahatlou, UC San Diego

Recipe for R18

Then 'unsetenv CFG_DEFAULT_IMPL' and rerun Moose. Note that Moose is not validated in an analysis release. Please use the production releases found here:

Simulation Production

Purpose

Input

Output

Requirements

1. A working production release. Check the simuprod-hn forum for the latest recommended release.
2. Decay file for your favorite decay mode
3. A tcl file to configure correctly the I/O (see the example below).

Example

# setup a new test release
$ newrel -s $BFROOT/work/your_username_initial/your_username -t 14.3.2b my-14.3.2b
$ cd my-14.3.2b

# setup your path 
$ srtpath <enter> <enter>

# setup the correct condition database
$ cond14boot

# checkout the workdir package
$ addpkg workdir
$ cd workdir
$ gmake setup

Next, you must create a tcl "snippet" with your favorite options for each job you want to run. Here is an example mymoose.tcl:

# -------- mymoose.tcl: begin -----------

set ProdTclOnly              true
set RUNNUM 987655
set CONDALIAS Aug2001
set SimAppBkndInputCollection /store/SP/BkgTriggers/BkgTriggers_200108_V01
set SimAppBkndFirstEvent 1
set SimAppDigiMix true
set SimAppKanDigiMix true
set NEVENT  1000
set UDECAY PARENT/ProdDecayFiles/B0B0bar_generic.dec
set MooseHBookFile        myMoose.hbook
set MooseOutputCollection  /work/users/rahatlou/vanilla-14.3.2b/myMoose-collection
mod talk KanEventOutput
  allowDirectoryCreation set true
exit
sourceFoundFile  Moose/MooseProduction.tcl

# -------- mymoose.tcl: end -----------

• RUNNUM - set the runnumber, used also as the seed for the random number generator
• CONDALIAS - set the data taking period for which you want to generate MC
• SimAppBkndInputCollection - set the collection to use for background digi events. Must be consistent with the CONDALIAS setting. (use BbkSqlShell "select * from bbrmdc.prod_bkg" to find a complete list of available background collections)
• SimAppBkndFirstEvent - set the first event from the background digi event collection to use
• SimAppDigiMix - enables/disables digi mixing. Default is disabled
• SimAppKanDigiMix - use a CM2 collection or a BDB collection for background digis (true=CM2 collection)
• NEVENT - number of events to generate
• UDECAY - your favorite decay mode
• MooseHBookFile - name of hbook file for monitoring plots
• MooseOutputCollection - name of the output collection
• The KanEventOutput "module talk" which sets "allowDirectoryCreation" to true allows any necessary subdirectories in your /work/users/<you> area to be created automatically.

Moose with digi mixing disabled is not supported. Subsystem simulation algorithms use the background digi timestamp to match data taking conditions fully. Without this timestamp, a default of T-25 years is selected - however in many cases, the conditions corresponding to T-25 years are simply a default and will not resemble realistic detector conditions.

The location of the output collection is interpreted in the new event store and corresponds to a physical location. If you are not familiar with this, you should look at the documentation for KanUserAdmin.

You are now ready to run:

$ MooseApp mymoose.tcl

After the successful completion of your job you can check on your collection by using the KanUserAdmin and KanCollUtil utilities.

$ KanUserAdmin list /work/users/rahatlou/vanilla-14.3.2b/myMoose-collection
/work/users/rahatlou/vanilla-14.3.2b/myMoose-collection

$ KanCollUtil  /work/users/rahatlou/vanilla-14.3.2b/myMoose-collection
/work/users/rahatlou/vanilla-14.3.2b/myMoose-collection (1000 events)

See the section about utility programs for more details about inspecting the content of the output collection.

You can now use the output collection /work/users/rahatlou/vanilla-14.3.2b/myMoose-collection to run your analysis jobs.

Other Notes

Where can I find the other tcl options for MooseApp?

$ grep ";#" ~/reco/cand14.4.2-14.4.1a/Moose/MooseProduction.tcl 
FwkCfgVar MooseVerbose ;# set the ErrLoggingLevel level
FwkCfgVarRequire RUNNUM      ;# runnumber used to initialize the random numbers
FwkCfgVarRequire NEVENT      ;# number of events to generate
FwkCfgVarRequire CONDALIAS   ;# data taking month, e.g. Nov2002