- bfc.C macro provides interface to StBFChain
- Chain is defined by a list of named components or keywords
- to get the current list of keys and examples of its usage by running
root4star bfc.C
Examples and Available chain components
This is the usage information that is
printed if the Chain call parameter is empty ("").
This is indicative only; it is probable that changes have been
made since that usage info page was last updated.
For up to date info, print it out in the bfc.C version you are
using via root4star bfc.C.
- Relatively easy to add a new option/chain element
- Chain defined through bfc.C call parameters; no changes to the
macro itself to select the chain you want to run
- If StBFChain does not know about your maker then you can modify bfc.C
- to laod shared library with your maker
- to instatiate the maker
- to put it in chain after/before certain maker
- Modifing bfc.C you also can adjust some parameters, IO, etc to your taste.
Organization
void bfc(const Int_t First,
const Int_t Last,
const Char_t *Chain="gstar Cy2a tfs",
Char_t *infile="", Char_t *outfile="
- The outfile parameter should normally be left alone; the output
file name(s) will be built from the input filename root plus
the appropriate extension.
- If you want to have a look at how real production jobs are
set up to use bfc.C, see the $STAR/mgr/bfc script
- Chain components are defined as ordered array of c-structs
- A '-' prefix is used to turn chain components OFF
- By default all components are turn off.
- Chain components are activated by including them in the Chain
string in the bfc.C call
- Parsing of chain components is insensitive to case, and
the all characters are significant.