Difference: AtlasDataAnalysis (138 vs. 139)

Revision 1392012-02-07 - AlistairGemmell

Line: 1 to 1

META TOPICPARENT	name="WebHome"

<-- p { margin-bottom: 0.21cm; }h1 { margin-bottom: 0.21cm; }h1.western { font-family: "Liberation Serif",serif; }h1.cjk { font-family: "DejaVu Sans"; }h1.ctl { font-family: "DejaVu Sans"; }h2 { margin-bottom: 0.21cm; }h4 { margin-bottom: 0.21cm; }h5 { margin-bottom: 0.21cm; }h3 { margin-bottom: 0.21cm; }h3.western { font-family: "Liberation Serif",serif; }h3.cjk { font-family: "DejaVu Sans"; }h3.ctl { font-family: "DejaVu Sans"; }pre.cjk { font-family: "DejaVu Sans",monospace; }a:link { } -->

Line: 410 to 410

atlastth_hislist_flat-v15.txt

Changed:

<
<

This file provides a map for the ANN, giving it the output file names (and in which directory they are to be stored, relative to ${template_area} - set in genemflat) and the tree structure where the final result of the ANN will be stored in the output (in the example below, the output file is ${template_area}/11602-filter.root, and the result graph will be FlatPlotter/NNScoreAny_0_0_0 0). The number to the left of the file name indicates which process it is - this is established using a file called TMVAsteer.txt, which is created through the running of genemflat_batch_Complete2_SL5.sh), and corresponds to the variable my_Eventtype in the input files (this can also be influenced in genemflat). Thus it is possible to assign multiple files to the same process (e.g. a file for the electron stream and muon stream are both assigned to Data), by giving them a common number at the start of the line.

>
>

This file provides a map for the ANN, giving it the output file names (and in which directory they are to be stored, relative to ${template_area} - set in genemflat) and the tree structure where the final result of the ANN will be stored in the output (in the example below, the output file is ${template_area}/11602-filter.root, and the result graph will be FlatPlotter/NNScoreAny_0_0_0 0). The number to the left of the file name indicates which process it is - this is also used in the files AtlasttHRealTitles.txt and FlatAtlastthPhysicsProc1.txt, and needs to be consistent with them), and corresponds to the variable my_Eventtype in the input files (this can also be influenced in genemflat). Thus it is possible to assign multiple files to the same process (e.g. a file for the electron stream and muon stream are both assigned to Data), by giving them a common number at the start of the line.

0 116102-filter.root    FlatPlotter/NNScoreAny_0_0_0 0

Line: 424 to 424

AtlasttHRealTitles.txt

Changed:

<
<

The list of signal/background processes can be found in AtlasttHRealTitles.txt (where the names are specified and associated with numbers). At present these are:

>
>

The list of signal/background processes can be found in AtlasttHRealTitles.txt (where the names are specified and associated with process numbers - these process/number associations need to be the same as in atlastth_hislist_flat-v15.txt and FlatAtlastthPhysicsProc1.txt). At present these are:

Process_0_0 TTjj:Semileptonic

Line: 443 to 443

GeneralParameter  string      1 FileString=my_Eventtype

Changed:

<
<

Indicates the leaf in the input file which shows which process the event belongs to - this is the same number as we've specified as in atlastth_hislist_flat-v15.txt and AtlasttHRealTitles.txt.

>
>

Indicates the leaf in the input file which shows which process the event belongs to - this is the same number as we specify later in genemflat for steerComputentp.txt - it does not have to be consistent with the process numbers as defined in atlastth_hislist_flat-v15.txt, AtlasttHRealTitles.txt and FlatAtlastthPhysicsProc1.txt.

ColumnParameter   File         1 OnOff=1:SorB=1:Process=tth

Line: 474 to 474

ColumnParameter SignalList 1 ttH=1 ColumnParameter DataList 1 Data=11

Changed:

<
<

Here you specify once again the numbers assigned to the processes by my_Eventtype (for tt0j it equals zero), and list things as BackgroundList, SignalList or DataList. The number after 'BackgroundList' or 'SignalList' is unique for each process (to preserve the uniqueness of <tag>:<sequence>), but it must be sequential, running from 0 to n-1 (where you have n samples) - apart from for DataList entries (as shown above). It also does not need to correspond to my_Eventtype, however, for completeness' sake within this file I have set it as such. The number at the end of this declaration (tt0j=0 in this case) needs to be sequential - it instructs the net of the order in which to process the samples, so it must go from 0 to n-1 (when you have n samples). It must match up with the numbers provided in atlastth_histlist_flat-v16.txt so that processes and data can be matched to the various individual files.

>
>

Here you specify once again the numbers assigned to the processes by my_Eventtype (for tt0j it equals zero), and list things as BackgroundList, SignalList or DataList. The number after 'BackgroundList' or 'SignalList' is unique for each process (to preserve the uniqueness of <tag>:<sequence>), but it must be sequential, running from 0 to n-1 (where you have n samples) - apart from for DataList entries (as shown above). It also does not need to correspond to my_Eventtype, however, for completeness' sake within this file I have set it as such. The number at the end of this declaration (tt0j=0 in this case) needs to be sequential - it instructs the net of the order in which to process the samples, so it must go from 0 to n-1 (when you have n samples). It must match up with the numbers provided in atlastth_histlist_flat-v16.txt and AtlasttHRealTitles.txt so that processes and data can be matched to the various individual files.

ColumnParameter PseudoDataList 0 tt0j=0

Line: 1001 to 1001

Before trying debugging, you should set up the environment in your terminal (when running the code normally, this is done automatically by tr${run}.job). This can be done by sourcing setup_glantp.sh, which automates setting of the relevant paths - remember to specify the release number of GlaNtp that you have in your area:

Changed:

<
<

source setup_glantp.sh 00-00-17

>
>

source setup_glantp.sh 00-00-32

At any point you can check that the a given steering file can be read by GlaNtp by using testSteerrv5.exe - found inside your GlaNtp package:

Line: 1012 to 1012

Please note that the

Linux2.6-GCC_4_1

may change depending on your system architecture. It is set during the installation of GlaNtp, and can be checked with the command

echo $BFARCH

Added:

>
>

Another debugging script checks you have defined the processes correctly:

testFlatProcessInforv5.exe FlatAtlastthPhysicsProc1.txt

The output from the near the end of this is the important bit:

Table of what category each process is falling under
IP :       PN :       LB : B : D : S : P : O
 0 :       tt : t#bar{t} : 1 : 0 : 0 : 1 : 0

IP is something or other (need to ask Rick to remind me), PN is process name, LB is the label of the process. B, D and S are whether or not the process is Background, Data or Signal respectively. P is whether or not that process is included in the manufacture of Pseudoexperiments, and O is the order in which that process is plotted.

To debug the code further, two things need to be done - first, all the debug switches need to be turned on, and then you need to restrict the number of events to ~10 (for a Computentp run this will still manage to generate a 2 GB log file!). All of these switches are found in teststeerFlatReaderATLAStthSemileptonic.txt (the progenitor for all FlatReader files) and steerComputentp.txt (created by genemflat). The debug switches are:

GeneralParameter bool 1 Debug=0
GeneralParameter bool 1 DebugGlobalInfo=0

View topic | History: r161 < r160 < r159 < r158 | More topic actions...