Difference: AtlasDataAnalysis (105 vs. 106)

Revision 1062011-09-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 { } -->

Computentp, Neural Nets and MCLIMITS

Line: 402 to 402
  The <sequence> parameter (in this case '0') is there so that you can specify the parameters for a given error for multiple channels, without falling foul of the uniqueness requirement for <tag>:<sequence>. We have chosen it so that it equals my_Eventtype for that process. 'Channel' is present just in case you're considering multiple channels. We're only considering the one channel in this case (SemiLeptonic). The final parameter (Process) is not actually used - the second parameter tells the ANN which errors are which, but this isn't very easily read by you, so feel free to add it in to help you keep track of the various errors! These final few parameters can be placed in any order, so long as they are separated by semicolons.
Added:
>
>

teststeerFlatReaderATLAStthSemileptonic-v16.txt

This file contains parameters to control the loops over events.

GeneralParameter int    1 NEvent=20000000
GeneralParameter int    0 FirstEvent=1
GeneralParameter int    0 LastEvent=10

FirstEvent and LastEvent allow you to specify a range of events to run over - this is liable only to be useful during debugging. (Note that these parameters are currently turned off). NEvent gives the maximum number of events processed for any given sample - take care with this, if you are running a particularly large sample through the code....

 

Passing preselection and sensible states

Many of the generated events in our samples will not pass the preselection cuts we would use in our final analysis. Sometimes to pass preselection requires some mistakes on the part of the reconstruction (e.g. tt + 0j), othertimes to fail preselection requires either the final state particles to be inherently unsuitable for our reconstruction, or to be mis-reconstructed. However, even if an event passes preselection it is possible that the events as reconstructed give a nonsensical final state - for example, the the light jets might not be able to be combined in such a way as to give a reasonable value of the W mass. Based on a few simple mass cuts, an event passing preselection can be determined to have a sensible state or not.

 
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