Changes between Version 1 and Version 2 of MadWeightFAQ


Ignore:
Timestamp:
04/06/12 16:33:02 (7 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MadWeightFAQ

    v1 v2  
    2121==== Do I have to perform selection on the events? ====
    2222
    23 <em> <strong>Question from Andre Sznajder</strong><br /> The matrix element method uses just outgoing the hard scattering partons/leptons. As a concrete example let's take the Higgs to WW semi-leptonic mode H-&gt;WW-&gt;(mu nu)(qq'). As I am using CMS reconstructed event as an input, do I have to make a pre-selection of the reconstructed muons, jets and missing energy that corresponds to the parton level objects ? Or I can put in the LHCO all reconstructed jets, and leptons and it will somehow choose the correct ones ? </em>
     23<em> **g>Question from Andre Sznajder**[[br]] The matrix element method uses just outgoing the hard scattering partons/leptons. As a concrete example let's take the Higgs to WW semi-leptonic mode H->WW->(mu nu)(qq'). As I am using CMS reconstructed event as an input, do I have to make a pre-selection of the reconstructed muons, jets and missing energy that corresponds to the parton level objects ? Or I can put in the LHCO all reconstructed jets, and leptons and it will somehow choose the correct ones ? </em>
    2424
    2525MadWeight (MW) can only process event with the correct number of reconstructed events. So MW will first reject all the "wrong" events. So in practise, if you have two muons or three jet for an event, this one will not be accepted.
     
    4343==== How can I extract the individual event weights to create my own Likelihood function ? ====
    4444
    45 You will have files with that information:<br /> ./MYPROCESS/Events/MY_RUN_NAME/MY_RUN_NAME_weights.out<br /> ./MYPROCESS/Events/MY_RUN_NAME/MY_RUN_NAME_norm_weights.out<br /> (by default MY_RUN_NAME is fermi)
     45You will have files with that information:[[br]] ./MYPROCESS/Events/MY_RUN_NAME/MY_RUN_NAME_weights.out[[br]] ./MYPROCESS/Events/MY_RUN_NAME/MY_RUN_NAME_norm_weights.out[[br]] (by default MY_RUN_NAME is fermi)
    4646
    4747The first file contains all the unormalized weight. The second want contains the weight normalized by the cross section. (Usually people are interrested in this one) The format for each file is the following:
    48 {{{ nb_card.nb_event value error}}}
     48{{{
     49nb_card.nb_event value error
     50}}}
    4951
    5052'''nb_card''' is the card number (the XXX in Cards/param_card_XXX.dat). a correspondance with your modify parameter is show in ./MYPROCESS/Events/MY_RUN_NAME/likelihood_value.out or in ./Cards/mapping_card.dat)
     
    6365}}}
    6466
    65 This indicates that your transfer functions is not loaded properly. Did you perform the generation step $&gt;./bin/newprocess ? If you Downloaded your directory from the web did you assign your transfer functions with $&gt;./bin/change_tf.py ?
     67This indicates that your transfer functions is not loaded properly. Did you perform the generation step $>./bin/newprocess ? If you Downloaded your directory from the web did you assign your transfer functions with $>./bin/change_tf.py ?
    6668
    6769   * Did you enter an appropriate MadWeight_card.dat ? If you ask to change the value of a parameter which does not exist in the model you are working in, the code will not be able to produce the cards correctly.
     
    6971==== failure of ./bin/madweight analyzer (step: 2) ====
    7072
    71    * {{{ bad proc_card information: missing request process tag }}} Did you modify the proc_card.dat after the launch of ./bin/newprocess ? Then you have to type again
     73   * {{{
     74bad proc_card information: missing request process tag
     75}}} Did you modify the proc_card.dat after the launch of ./bin/newprocess ? Then you have to type again
    7276
    73 $&gt; ./bin/newprocess<br /> Indeed the proc_card.dat must be the same between this moment and the time where you launch madweight analyzer.
     77$> ./bin/newprocess[[br]] Indeed the proc_card.dat must be the same between this moment and the time where you launch madweight analyzer.
    7478
    7579   * {{{
     
    7983
    8084This error could arrive for two different reason
    81    1. You don't use the DecayChain format in your proc_card.dat (-&gt; change your proc_card.dat)
     85   1. You don't use the DecayChain format in your proc_card.dat (-> change your proc_card.dat)
    8286   1. You apply too strict restriction on available change of variable in MadWeight_card.dat
    8387
     
    9397   * make sure that you have collected the results:
    9498
    95 $&gt;./bin/madweight.py collect plot
     99$>./bin/madweight.py collect plot
    96100
    97101-- Main.OlivierMattelaer - 19 Mar 2009