Difference: AtlasDataAnalysis (106 vs. 107)

Revision 1072011-09-08 - AlistairGemmell

Line: 1 to 1
<-- 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 { } -->

Computentp, Neural Nets and MCLIMITS

Line: 743 to 743

Debugging the code

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)

# Set where your GlaNtp installation is                                                                                                                                                                        

source ~/GlaNtp/cleanpath3.sh                                                                                                                                                                                  
export PATH=\${PATH}:${GLANTPDIR}/bin/Linux2.6-GCC_4_1                                                                                                                                                         
export LD_LIBRARY_PATH=\${LD_LIBRARY_PATH}:${GLANTPDIR}/shlib/Linux2.6-GCC_4_1                                                                                                                                 
 To debug the code, 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). The debug switches are:
GeneralParameter bool 1 Debug=0
GeneralParameter bool 1 DebugGlobalInfo=0

Line: 759 to 771
  The easiest switch is to set NEvent=10 - however, if desired you can run over a specified range, by switching of the NEvent switch (changing it to int 0 NEvent) and switching on the other two switches, using them to specify the events you wish to run over.
Then you can run a subset of a complete run, but altering the flags found in genemflat:

# Flags to limit the scope of the run if desired                                                                                                                                                               

However, sometimes even this can not produce enough information., so there exist a few other options for checking your code. The first option is

runFlatReader FlatReaderATLAStthNoNN.txt /data/atlas09/ahgemmell/NNInputFiles_v16/mergedfilesProcessed/ttH-v16.root

This produces a lot of printout, so be sure to restrict the number of events as described above!


Various other switches of interest

In FlatReader:

This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback