Difference: AtlasDataAnalysis (100 vs. 101)

Revision 1012011-08-16 - AlistairGemmell

  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
- META TOPICPARENT
+ name="WebHome"
 It is possible for the inputs to the ANN to have more events in than those that you want to pass to on for processing. We only want to train the ANN on those samples that would pass our preselection cuts - general cleaning cuts and the like.  (There was a previous version of our inputs where we also required 'sensible states' - for each candidate event we required it to reconstruct tops and Ws with vaguely realistic masses.  However - this is a Neural Net analysis, so it has been decided to remove these cuts - they will after all in effect be reintroduced by the net itself if they would have been useful, and by not applying them ourselves, we are passing more information to the net.)  We therefore have filters so that Computentp and the ANN only look at events of our choosing. These filters take the place of various bitwise tests in TMVAsteer.txt (created in genemflat_batch_Complete2.sh) (not currently used, as explained below) and TreeSpecATLAStth.txt.
-<
<
+In TreeSpecATLAStth.txt the filters control what is used for the templating, and Computentp:
->
>
+ TreeSpecATLAStth.txt 

In TreeSpecATLAStth.txt, we establish the filters which control what is used for the templating, and Computentp:
 ListParameter SpecifyVariable:Higgs:cutMask 1 Type:int:Default:3
ListParameter SpecifyVariable:Higgs:invertWord 1 Type:int:Default:0

InvertWord is used to invert the relevant bits (in this case no bits are inverted) before the cut from cutMask is applied.  The cutMask will exclude from templating those events where the matching bits are equal to zero AFTER the inversion.  So here, with no inversion applied, those events with my_failEvent == 3 will be used for templating.
-<
<
+The constraint
->
>
+ TMVAsteer.txt (genemflat_batch_Complete2.sh)
 GeneralParameter string 1 Constraint=(my_failEvent&3)==3
-<
<
+in genemflat_batch_Complete2.sh controls the events used in the training, using a bitwise comparison.  If the constraint is true (i.e. the first two bits are set, and not equal to zero), then the event is used for training.  This filter is not used currently, as training of the net takes place based on the Computentp output - this Computentp output only contains sensible states (as specified in the TreeSpecATLAStth.txt file's filter).  If further filtering is required, then care must be taken to ensure that my_failEvent (or whatever you wish to base your filter on) is specified in the VariableTreeToNTP file, so that Computentp will copy it into its output.
->
>
+This controls the events used in the training, using a bitwise comparison.  If the constraint is true (i.e. the first two bits are set, and not equal to zero), then the event is used for training.  This filter is not used currently, as training of the net takes place based on the Computentp output - this Computentp output only contains sensible states (as specified in the TreeSpecATLAStth.txt file's filter).  If further filtering is required, then care must be taken to ensure that my_failEvent (or whatever you wish to base your filter on) is specified in the VariableTreeToNTP file, so that Computentp will copy it into its output.
-<
<
+If USEHILOSB is set to 1 then && must be appended to cut criteria, e.g. GeneralParameter string 1 Constraint=(my_failEvent&65536)==0&&.  This is because USEHILOSB adds more constraints.
->
>
+**If USEHILOSB is set to 1 then && must be appended to cut criteria, e.g. GeneralParameter string 1 Constraint=(my_failEvent&65536)==0&&.  This is because USEHILOSB adds more constraints.**
  Running

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