############################################################ # # LCFIPlusConfig - configuration files for LCFIPlus # # 10/2012 (Update: 4/2015) # T.Suehara, T.Tanabe (ICEPP, The University of Tokyo) ############################################################ LCFIPlusConfig/ --------------- input files for flavor tagging steer ----- example steering files vtxprob ------- input histograms used for flavor tagging used as input to the following parameters in the steering file: for new joint probability variables (d0probr2 etc, included in v3 weight files), d0/z0probv2 needed. d0/z0probv2 files are backward-compatible with v1/v2 weight files. lcfiweights ----------- TMVA weight files To use the weight files, first unpack it using e.g. tar zxvf 6q500_v02.tar.gz By default the files will be expanded into the same directory. Use the XML files from the steer/ directory corresponding to the weight files: v0X and p0X numbers should match. The following steering parameters control which weight files get used. Currently available weight files are the following: qq91_v01: e+e- --> qq at 91.2 GeV, generated by Whizard, no ISR, no beam profiles *qq91_v02: e+e- --> qq at 91.2 GeV, same as above, with more variables. The v02 steering files must be used to use these weight files. qq91_v03: e+e- --> qq at 91.2 GeV, same as above, with updated joint probability. The v03 steering files must be used to use these weight files. (All samples below are generated by Whizard and DBD beam parameters and pythia tuning.) qq250_v01: e+e- --> qq at 250 GeV. 6q500_v01: e+e- --> 6-jet samples at 500 GeV. *6q500_v02: e+e- --> 6-jet samples at 500 GeV, same as above, with more variables. The v02 steering files must be used to use these weight files. 6q1000_v01: e+e- --> 6-jet samples at 1 TeV. *6q1000_v02: e+e- --> 6-jet samples at 1 TeV, with additional variables. The v02 steering files must be used to use these weight files. *recommended for analysis (ilcsoft-v01-16, October 2012) PLEASE NOTE: v01 weight files are deprecated as they have a problem in c-tagging performance. This is fixed in v02 which incorporates additional variables. See talk by T.Suehara at LCWS12 for some description of the v02 variables. http://ilcagenda.linearcollider.org/getFile.py/access?contribId=183&sessionId=12&resId=1&materialId=slides&confId=5468 The _p0X suffix refers to the different preselection cuts applied to the tracks. It is found that their impact on b-tagging performance is small. *_p00 files are created with the following cuts: *_p01 files are created with the following cuts: (This is the configuration used in DBD mass production as of v01-16) *_p02 files are created with the following cuts: Acknowledgments ---------------- Thanks to Junping Tian for generating the 6q500 and 6q1000 samples.