Changes between Initial Version and Version 1 of TOPMassMeasurmentExample


Ignore:
Timestamp:
Feb 3, 2014, 6:08:56 PM (10 years ago)
Author:
Olivier Mattelaer
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • TOPMassMeasurmentExample

    v1 v1  
     1
     2== Preparation of the code ==
     3
     4=== Generation of the sample of events ===
     5
     6   1. installation of pythia-pgs and Delphes(3) package:
     7      * run ./bin/mg5_amc which starts a shell
     8      * run the command (inside that shell) '''install pythia-pgs'''
     9      * run the command '''install Delphes'''
     10 
     11   2. Generate the sample of events:
     12      * write a file with the following command:
     13        {{{
     14        generate p p > t t~ , t > b l+ vl, t~ > b~ l- vl~
     15        output TUTO_MW_MADEVENT
     16        launch
     17        delphes=ON
     18        }}}
     19      * Run MG5 on that file via the command: ./bin/mg5_amc PATH_TO_FILE
     20      * Your lhco events file should be place at: '''TUTO_MW_MADEVENT/Events/run_01/tag_1_delphes_events.lhco.gz'''
     21   
     22   '''NOTE:''' A sample of event obtained via the above method is available in attachment of this thread.
     23   It can be used as default.
     24 
     25=== Preparing MadWeight Run:
     26
     27   1. Create the MadWeight run directory. This step is the same as the one of the generation of the sample. But asking for a MW output:
     28      * write a file with the following command:
     29        {{{
     30        generate p p > t t~ , t > b l+ vl, t~ > b~ l- vl~
     31        output madweight TUTO_MW_MADWEIGHT
     32        }}}
     33      * Run MG5 on that file via the command: ./bin/mg5_amc PATH_TO_FILE
     34
     35=== Configure the run
     36   Go to the directory TUTO_MW_MADWEIGHT:
     37        {{{
     38        cd TUTO_MW_MADWEIGHT
     39        }}}
     40      and launch the code
     41        {{{
     42        ./bin/madweight.py
     43        }}}
     44   The code will print the following:
     45       {{{WARNING: No transfer function currently define. Please use the change_tf command to define one.
     46Do you want to edit a card (press enter to bypass editing)?
     47  1 / param      : param_card.dat
     48  2 / run        : run_card.dat
     49  3 / madweight  : madweight_card.dat
     50  4 / transfer   : transfer_card.dat
     51  5 / lhco       : input.lhco
     52 you can also
     53   - enter the path to a valid card or banner.
     54   - use the 'set' command to modify a parameter directly.
     55     The set option works only for param_card and run_card.
     56     Type 'help set' for more information on this command.
     57   - use the 'change_tf' command to set a transfer functions.
     58 [0, done, 1, param, 2, run, 3, madweight, 4, enter path, ... ][60s to answer]
     59
     60}}}
     61
     62  1. You need to define which type of '''transer_function''' you want to use (the analytical form). For this example, we will use one of the pre-defined one. GO to the page TRANSFERFUNCTIONS for details on how implement additional functions. so type
     63     {{{
     64       change_tf
     65     }}}
     66     It returns:
     67     {{{
     68Please choose your transfer_function between
     69 0 / all_delta
     70 1 / dbl_gauss_pt_jet
     71 2 / gauss_on_leptons
     72 3 / single_gaussian
     73 4 / uniform
     74 5 / user
     75 [dbl_gauss_pt_jet, all_delta, gauss_on_leptons, single_gaussian, uniform, user, 0, 1, 2, ... ][60s to answer]
     76     }}}
     77     Type "1" to select the dbl_gauss_pt_jet transfer functions. This correspond to have the direction and the energy of the lepton in delta functions and the direction of the (b)-jets in delta as well. On the contrary, the pt of the jet is associated to a double gaussian where each of the 5 parameters depends of the eneregy like $a + b * \sqrt{E} + c * E$. The value of $a,b,c$ will be assigned in the transfer_card.dat in the next step of the code.
     78 
     79  2. We are now back to the first question and are ready to enter the parameter of the transfer_functions. 
     80     Type 4, will open a text editor (vi or emacs depending of your configuration) where you can edit the parameters.
     81     The current file is:
     82     {{{
     83#+-----------------------------------------------------------------------+
     84#|                         TRANSFER_CARD.DAT                             |
     85#|                                                                       |
     86#|     Author: Pierre Artoisenet (UCL-CP3)                               |
     87#|             Olivier Mattelaer (UCL-CP3)                               |
     88#+-----------------------------------------------------------------------+
     89#|     This file is generated automaticly by MADWEIGHT                   |
     90#|     card generation version: 2.0.0                                    |
     91#+-----------------------------------------------------------------------+
     92#|                                                                       |
     93#|    To change the transfer function run ./bin/change_tf.py             |
     94#|    Current parametrization :dbl_gauss_pt_jet                          |
     95#|                                                                       |
     96#+-----------------------------------------------------------------------+
     97BLOCK TF_jet_E
     98#+-----------------------------------------------------------------------+
     99#|    Parameter for particles: u,d,s,c,b,g                               |
     100#|    Information: double gaussian with parameter depending of the energy|
     101#|                 as A+B*sqrt(E)+C*E                                    |
     102#+-----------------------------------------------------------------------+
     103     1       1.5591d0    # biais first gaussian b1=#1+#2*sqrt(E)*#3*E
     104     2       0.2933      # biais first gaussian
     105     3       0.0100d0    # biais first gaussian
     106     4       0.9518d0    # sigma first gaussian s1=#4+#5*sqrt(E)+#6*E
     107     5       0.5222d0    # sigma first gaussian
     108     6       0.0191d0    # sigma first gaussian
     109     7       0.1997d0    # relative weigth      r=#7+#8*sqrt(E)+#9*E
     110     8       0d0         # relative weigth
     111     9       0d0         # relative weigth
     112     10      1.16352d1   # biais second gaussian b2=#10+#11*sqrt(E)*#12*E
     113     11      -2.3937d0   # biais second gaussian
     114     12      0.3156d0    # biais second gaussian
     115     13      3.3218d0    # sigma second gaussian s1=#13+#14*sqrt(E)+#15*E
     116     14      -0.0856d0   # sigma second gaussian
     117     15      0.1375d0    # sigma second gaussian
     118}}}
     119    In this example, we will study the sensitivity to the sigma parameter of the transfer function by comparing the difference in weights in three different value for the parameter of the transfer function (one being the above default, the two other being the same with the sigma increas/decrease by 20%). The card used is:
     120{{{
     121#+-----------------------------------------------------------------------+
     122#|                         TRANSFER_CARD.DAT                             |
     123#|                                                                       |
     124#|     Author: Pierre Artoisenet (UCL-CP3)                               |
     125#|             Olivier Mattelaer (UCL-CP3)                               |
     126#+-----------------------------------------------------------------------+
     127#|     This file is generated automaticly by MADWEIGHT                   |
     128#|     card generation version: 2.0.0                                    |
     129#+-----------------------------------------------------------------------+
     130#|                                                                       |
     131#|    To change the transfer function run ./bin/change_tf.py             |
     132#|    Current parametrization :dbl_gauss_pt_jet                          |
     133#|                                                                       |
     134#+-----------------------------------------------------------------------+
     135BLOCK TF_jet_E
     136#+-----------------------------------------------------------------------+
     137#|    Parameter for particles: u,d,s,c,b,g                               |
     138#|    Information: double gaussian with parameter depending of the energy|
     139#|                 as A+B*sqrt(E)+C*E                                    |
     140#+-----------------------------------------------------------------------+
     141# Parameter with sigma increased by 20%
     142     1       1.5591d0    # biais first gaussian b1=#1+#2*sqrt(E)*#3*E
     143     2       0.2933      # biais first gaussian
     144     3       0.0100d0    # biais first gaussian
     145     4       1.14216d0    # sigma first gaussian s1=#4+#5*sqrt(E)+#6*E
     146     5       0.62664d0    # sigma first gaussian
     147     6       0.02292d0    # sigma first gaussian
     148     7       0.1997d0    # relative weigth      r=#7+#8*sqrt(E)+#9*E
     149     8       0d0         # relative weigth
     150     9       0d0         # relative weigth
     151     10      1.16352d1   # biais second gaussian b2=#10+#11*sqrt(E)*#12*E
     152     11      -2.3937d0   # biais second gaussian
     153     12      0.3156d0    # biais second gaussian
     154     13      3.98616d0    # sigma second gaussian s1=#13+#14*sqrt(E)+#15*E
     155     14      -0.10272d0   # sigma second gaussian
     156     15      0.165d0    # sigma second gaussian
     157# Parameter with default value
     158     1       1.5591d0    # biais first gaussian b1=#1+#2*sqrt(E)*#3*E
     159     2       0.2933      # biais first gaussian
     160     3       0.0100d0    # biais first gaussian
     161     4       0.9518d0    # sigma first gaussian s1=#4+#5*sqrt(E)+#6*E
     162     5       0.5222d0    # sigma first gaussian
     163     6       0.0191d0    # sigma first gaussian
     164     7       0.1997d0    # relative weigth      r=#7+#8*sqrt(E)+#9*E
     165     8       0d0         # relative weigth
     166     9       0d0         # relative weigth
     167     10      1.16352d1   # biais second gaussian b2=#10+#11*sqrt(E)*#12*E
     168     11      -2.3937d0   # biais second gaussian
     169     12      0.3156d0    # biais second gaussian
     170     13      3.3218d0    # sigma second gaussian s1=#13+#14*sqrt(E)+#15*E
     171     14      -0.0856d0   # sigma second gaussian
     172     15      0.1375d0    # sigma second gaussian
     173# Parameter with sigma decreased by 20%
     174     1       1.5591d0    # biais first gaussian b1=#1+#2*sqrt(E)*#3*E
     175     2       0.2933      # biais first gaussian
     176     3       0.0100d0    # biais first gaussian
     177     4       0.9518d0    # sigma first gaussian s1=#4+#5*sqrt(E)+#6*E
     178     5       0.41776d0    # sigma first gaussian
     179     6       0.01528d0    # sigma first gaussian
     180     7       0.1997d0    # relative weigth      r=#7+#8*sqrt(E)+#9*E
     181     8       0d0         # relative weigth
     182     9       0d0         # relative weigth
     183     10      1.16352d1   # biais second gaussian b2=#10+#11*sqrt(E)*#12*E
     184     11      -2.3937d0   # biais second gaussian
     185     12      0.3156d0    # biais second gaussian
     186     13      2.65744d0    # sigma second gaussian s1=#13+#14*sqrt(E)+#15*E
     187     14      -0.06848d0   # sigma second gaussian
     188     15      0.110000d0    # sigma second gaussian
     189}}}
     190   The weigths evaluated for those three transfer-function will be computed '''simultaneously''' on the same phase-space point. The integration will be optimised for the first one. This method is valid '''ONLY''' if the transfer function have the same domain. For precision point of view, it is therefore advised to set the broader transfer function as the first one in the file.
     191
     192   3. After exiting the text editor, we are once again back to the same question (Do you want to edit a card (press enter to bypass editing)?...): We will now details the content of the MadWeight_card. After typing "3", you open a text editor with the following:
     193      {{{
     194##########################################################################
     195##                                                                      ##
     196##                             MadWeigth                                ##
     197##                             =============                            ##
     198##                                                                      ##
     199##                              Run control                             ##
     200##                              -----------                             ##
     201##                                                                      ##
     202##                                                                      ##
     203##    Author: Mattelaer Olivier (UCL-CP3)                               ##
     204##            Artoisenet Pierre (UCL-CP3)                               ##
     205##                                                                      ##
     206##    Version:     5.0.0                                                ##
     207##    Last change: 01/10/14                                             ##
     208##                                                                      ##
     209##########################################################################
     210##                                                                      ##
     211##  This Card defines all specific parameters of Madweight              ##
     212##                                                                      ##
     213##########################################################################
     214#*************************************************************************
     215##                      select run options                              ##
     216#*************************************************************************
     217Block MW_Run
     218#   TAG                 VALUE                    UTILITY
     219     name                fermi    # name for the run
     220     nb_exp_events        4       # number of experimental events to consider
     221     MW_int_points        2000    # number of points (by permutation) in MadWeight integration for survey
     222     MW_int_refine        10000   # number of points (by permutation) in MadWeight integration for refine
     223     precision            0.005   # stops computation if precision is reached.
     224     nb_event_by_node     1       # one job submission compute the weight for N events
     225     log_level            weight  # from low level of log to extensive log:
     226                                  # weight, permutation, channel, full
     227     use_cut              F       # use the cut defined in run_card.dat
     228     bw_cut               F       # use the BW cut
     229     nwa                  0.1     # width below narrow width approximation is used.
     230     isr                  0       # isr=0 : ignore ISR effect (except if all FS particles are visible)
     231                                  # isr=1 : correct kinematic based on reconstructed Pt(isr)
     232     inputfile          './Events/input.lhco' # path to the input file (in lhco format)
     233
     234
     235#*************************************************************************
     236##                  define the different param_card's                   ##
     237#*************************************************************************
     238Block MW_parameter
     239#   TAG      VALUE                     UTILITY
     240    mode         1         #    type of input
     241                           #    0 : inputs are read from the cards: param_card_1.dat, param_card_2.dat,...
     242                           #    1 : redefines some values from param_card.dat according to the form below
     243                           #    2 : same but the value for different parameters are modified simultaneously
     244#
     245#                             # first parameter #
     246     11       mass          # Block of the parameter to change
     247     12       6             # id of the parameter to change
     248     13       180           # here you can enter the different values:
     249     13       190           #         add a new line with tag 13 to introduce a new value
     250#
     251#                            #  second parameter #
     252#                            !DELETE ALL THE FOLLOWING TAG IF YOU WANT TO RUN WITH ONLY ONE PARAM!
     253#     21       MGCKM          # Block of the parameter to change
     254#     22       1              # id of the paramter to change
     255#     22       2              # id2 of the paramter to change
     256#     23       1.5E-02        # here you can enter the different values:
     257#     23       1.8E-02        #        add a new line with tag 23 to introduce a new value
     258#
     259#  use same syntax for parameters 3,4,...
     260#*************************************************************************
     261##                                Permutations                          ##
     262#*************************************************************************
     263Block MW_perm
     264#   TAG           VALUE                    UTILITY
     265     permutation  T         # make permutation
     266     bjet_is_jet  T         # consider permutation between b-jets and light jets
     267     montecarlo   T         # Monte-Carlo over permutation (Huge speed up if many permutation)
     268     preselect    'default' # How to pre-select the correct permutation set.
     269                            # put 'None' if no pre-selection to perform.
     270                            # You can set the path to a fortran file defining the require function
     271                            # See file SubProcesses/permutation_weight_default.dat for
     272                            # instructions.
     273     min_perm_cut 5e-4      # Cut for discarding permutation on the preselected method
     274#*************************************************************************
     275##                       Phase-Space Integration mapping                ##
     276#*************************************************************************
     277Block MW_gen
     278    force_nwa     2         # Only consider the change of variable alligning particles
     279                            # with width smaller than this value. This speed up the code
     280                            # but can lead to zero weight for background event where the
     281                            # kinematic doesn't agree with the associated mass.
     282                            # if "mw_run nwa" parameter is bigger than this value, that
     283                            # value is used for this parameter automatically.
     284}}}
     285     Here is a details for the non trivial parameters:
     286       || *Block*  || *parameter* || *functionality* ||   
     287       || MW_RUN || name      || is used for the output directory and to give a unique name to each run ||
     288       ||        || MW_int_points || Number of points used to have a first idea of the contribution of each integral/permutation to evaluate ||
     289       ||        || MW_int_refine || Same but only for the refine made on the relevant contribution selected at the previous step ||
     290       ||        || nb_event_by_node || How many event are grouped inside a unique run submitted on the cluster ||
     291       ||        || log_level        || Indicates how much information as to be kept from the run. The two physical level are '''weights''' and '''permutations'''. '''full'' will return the log associated to each run' ||
     292       ||        || nwa              || The integral on the invariant mass of particles with width below this threshold will be done in Narrow-width approximation (i.e. the mass of that particles will be kept fixed during the computation and the integral on the invariant mass assumed to correspond to the Breit-Wigner Shape. The default correspond to use this approximation ONLY for the Higgs. ||
     293       ||        || isr              || -> Pierre ||
     294       ||        || inputfile        || The path of the input_file in lhco (or lhco.gz) to use to get the events.||
     295       ||        ||                  ||           ||
     296       || MW_parameter || mode || Decide how the scan on the param_card has to be done (See the details in the cards) ||
     297       || MW_perm      || permutation || Decide if we have to make the jet-parton assignment or not (should always be on in principle) ||
     298       ||              || bjet_is_jet || Consider if a bjet should be seen as a jet or not. If set on False, then MW will require to have the correct number of tagged jet in the lhco file and the permutation will not be done between those two class of events. ||
     299       ||              || montecarlo || Instead of performing one integral by permuation, doing a single one, where for each phase-space point we change the permutation under consideration and use VEGAS to select automatically the contributting one. This is extremelly usefull (=much faster) as soon as the number of permutation is larger than 4). If they are two permuation or less it's sometimes usefull to set this one on False. ||
     300       ||              || preselect || It's possible to know in advance (up to a given extend) which permutation are the relevant one. The idea of this input is to allow you to make the selection before the numerical integration. If set on '''none''' then you will bypass this module and evaluate all permuation. Otherwise the idea is to assign to each permutation a number. Then the code removes the contribution which have a relative weight to the sum lower than a given threshold. If you set the value on '''default''' the weight is given by the product of breit-wigner of the propagator associated to fully visible particles. The width of the Breit-wigner is replaced by an effective width given by $\sqrt{\Gamma_M**2+\sum \Gamma_TF**2}$, where $\Gamma_M$ is the width associated to the particle of that given propagator, and $\Gamma_TF$ the width associated to the transfer function of one of the final state particle on which the particle decays. '''A path to an arbitrary file''' can be set in order to define this selection in a different way (like forcing at least one b to be b-tagged, using information even in presence of neutrino,...)
     301       ||              || min_perm_cut || The cut of below which one permutation is discarded.||
     302       || MW_gen       || force_nwa    || MW will try to parametrize the phase-space in a way where the NWA approximation can be applied on particles which have a with below this value. This can increase the number of zero-result for background events (events which didn't have that particles) but those events will have negligeable weights anyway. The interest is that this options speed up the code in most of the case. ||
     303
     304       For this tutorial, we will perform a scan in the top mass. I've reduce the number of points in the first iteration, since this process the integration is relatively simple to perform and reduce the require precision to 1%.
     305       To obtain the same MadWeight_card as me (set in attachment), you can enter the following command to answer the question:
     306       {{{
     307       set nb_exp_events 2
     308       set nb_event_by_node 2
     309       set MW_int_points 1000
     310       set MW_parameter 13 165 170 175 180 185
     311       set precision 0.01
     312       set inputfile ../TUTO_MW_MADEVENT/Events/run_01/tag_1_delphes_events.lhco.gz
     313       }}}
     314
     315       3. After exiting the text editor, we are once again back to the same question (Do you want to edit a card (press enter to bypass editing)?...): The content of the latest two files: param_card and run_card are the same as those from a MadEvent run but note that
     316          * The cut are by default deactivated by a parameter of the MadWeight_card
     317          * The parameter can be changed via the MadWeight_card via the MW_parameter options.
     318
     319       4. You can also enter directly from this shell the input file (instead of writting it in the card) the interest stands in the auto_completion which can be usefull to find the correct file.
     320
     321       5. You can type enter and the computation will start.
     322       {{{no mapping card found
     323treatcards
     324starting the creation of the param_card
     325define new mapping file
     326define new mapping file
     327we have created  5  param_card's
     328get_integration_channel
     329treating P0_gg_ttx_t_bepve_tx_bxemvex directory
     330structure of the configuration 1:
     331particle: 3     pid :   5       level: 1        mother: -4      twin: -3
     332particle: 6     pid : -5        level: 1        mother: -2      twin: -1
     333particle: 4     pid : -11       level: 2        mother: -3      twin: 5
     334particle: 5     pid :  12       level: 2        mother: -3      twin: 4
     335particle: 7     pid :  11       level: 2        mother: -1      twin: 8
     336particle: 8     pid : -12       level: 2        mother: -1      twin: 7
     337particle: -1    pid : -24       level: 2        channel: S      des: 8 7        mother: -2      mass/width: 80.419002/2.0476
     338particle: -2    pid : -6        level: 1        channel: S      des: -1 6       mother: -5      mass/width: 165.0/1.4915
     339particle: -3    pid :  24       level: 2        channel: S      des: 5 4        mother: -4      mass/width: 80.419002/2.0476
     340particle: -4    pid :   6       level: 1        channel: S      des: -3 3       mother: -5      mass/width: 165.0/1.4915
     341particle: -5    pid :  21       level: 0        channel: T      des: -2 -4                      mass/width: 0.0/0.0
     3421 ECS('s) 5 propagator(s) 2 missing particles(s)
     343detail :
     344d(4)   
     3454 blob(s) associated
     346Blob details: main 3
     347blob generation: [0|3 :]
     348Blob details: main 4
     349blob generation: [0|4 :]
     350Blob details: main 6
     351blob generation: [0|6 :]
     352Blob details: main 7
     353blob generation: [0|7 :]
     354
     355treating P0_gg_ttx_t_bepve_tx_bxmumvmx directory
     356structure of the configuration 1:
     357particle: 3     pid :   5       level: 1        mother: -4      twin: -3
     358particle: 6     pid : -5        level: 1        mother: -2      twin: -1
     359particle: 4     pid : -11       level: 2        mother: -3      twin: 5
     360particle: 5     pid :  12       level: 2        mother: -3      twin: 4
     361particle: 7     pid :  13       level: 2        mother: -1      twin: 8
     362particle: 8     pid : -14       level: 2        mother: -1      twin: 7
     363particle: -1    pid : -24       level: 2        channel: S      des: 8 7        mother: -2      mass/width: 80.419002/2.0476
     364particle: -2    pid : -6        level: 1        channel: S      des: -1 6       mother: -5      mass/width: 165.0/1.4915
     365particle: -3    pid :  24       level: 2        channel: S      des: 5 4        mother: -4      mass/width: 80.419002/2.0476
     366particle: -4    pid :   6       level: 1        channel: S      des: -3 3       mother: -5      mass/width: 165.0/1.4915
     367particle: -5    pid :  21       level: 0        channel: T      des: -2 -4                      mass/width: 0.0/0.0
     3681 ECS('s) 5 propagator(s) 2 missing particles(s)
     369detail :
     370d(4)   
     3714 blob(s) associated
     372Blob details: main 3
     373blob generation: [0|3 :]
     374Blob details: main 4
     375blob generation: [0|4 :]
     376Blob details: main 6
     377blob generation: [0|6 :]
     378Blob details: main 7
     379blob generation: [0|7 :]
     380
     381treating P0_gg_ttx_t_bmupvm_tx_bxemvex directory
     382structure of the configuration 1:
     383particle: 3     pid :   5       level: 1        mother: -4      twin: -3
     384particle: 6     pid : -5        level: 1        mother: -2      twin: -1
     385particle: 4     pid : -13       level: 2        mother: -3      twin: 5
     386particle: 5     pid :  14       level: 2        mother: -3      twin: 4
     387particle: 7     pid :  11       level: 2        mother: -1      twin: 8
     388particle: 8     pid : -12       level: 2        mother: -1      twin: 7
     389particle: -1    pid : -24       level: 2        channel: S      des: 8 7        mother: -2      mass/width: 80.419002/2.0476
     390particle: -2    pid : -6        level: 1        channel: S      des: -1 6       mother: -5      mass/width: 165.0/1.4915
     391particle: -3    pid :  24       level: 2        channel: S      des: 5 4        mother: -4      mass/width: 80.419002/2.0476
     392particle: -4    pid :   6       level: 1        channel: S      des: -3 3       mother: -5      mass/width: 165.0/1.4915
     393particle: -5    pid :  21       level: 0        channel: T      des: -2 -4                      mass/width: 0.0/0.0
     3941 ECS('s) 5 propagator(s) 2 missing particles(s)
     395detail :
     396d(4)   
     3974 blob(s) associated
     398Blob details: main 3
     399blob generation: [0|3 :]
     400Blob details: main 4
     401blob generation: [0|4 :]
     402Blob details: main 6
     403blob generation: [0|6 :]
     404Blob details: main 7
     405blob generation: [0|7 :]
     406
     407treating P0_gg_ttx_t_bmupvm_tx_bxmumvmx directory
     408structure of the configuration 1:
     409particle: 3     pid :   5       level: 1        mother: -4      twin: -3
     410particle: 6     pid : -5        level: 1        mother: -2      twin: -1
     411particle: 4     pid : -13       level: 2        mother: -3      twin: 5
     412particle: 5     pid :  14       level: 2        mother: -3      twin: 4
     413particle: 7     pid :  13       level: 2        mother: -1      twin: 8
     414particle: 8     pid : -14       level: 2        mother: -1      twin: 7
     415particle: -1    pid : -24       level: 2        channel: S      des: 8 7        mother: -2      mass/width: 80.419002/2.0476
     416particle: -2    pid : -6        level: 1        channel: S      des: -1 6       mother: -5      mass/width: 165.0/1.4915
     417particle: -3    pid :  24       level: 2        channel: S      des: 5 4        mother: -4      mass/width: 80.419002/2.0476
     418particle: -4    pid :   6       level: 1        channel: S      des: -3 3       mother: -5      mass/width: 165.0/1.4915
     419particle: -5    pid :  21       level: 0        channel: T      des: -2 -4                      mass/width: 0.0/0.0
     4201 ECS('s) 5 propagator(s) 2 missing particles(s)
     421detail :
     422d(4)   
     4234 blob(s) associated
     424Blob details: main 3
     425blob generation: [0|3 :]
     426Blob details: main 4
     427blob generation: [0|4 :]
     428Blob details: main 6
     429blob generation: [0|6 :]
     430Blob details: main 7
     431blob generation: [0|7 :]
     432
     433compile
     434compile P0_gg_ttx_t_bepve_tx_bxemvex
     435compile P0_gg_ttx_t_bepve_tx_bxmumvmx
     436compile P0_gg_ttx_t_bmupvm_tx_bxemvex
     437compile P0_gg_ttx_t_bmupvm_tx_bxmumvmx
     438MadWeight code has been compiled.
     439check_events
     440time  verif event Lhco_filter 0.0441360473633
     4412 selected  events for  ./SubProcesses/P0_gg_ttx_t_bepve_tx_bxemvex  subprocess
     442time Lhco_filter 0.0454130172729
     443time  verif event Lhco_filter 0.0328230857849
     4442 selected  events for  ./SubProcesses/P0_gg_ttx_t_bepve_tx_bxmumvmx  subprocess
     445time Lhco_filter 0.0334248542786
     446time  verif event Lhco_filter 0.0493149757385
     4472 selected  events for  ./SubProcesses/P0_gg_ttx_t_bmupvm_tx_bxemvex  subprocess
     448time Lhco_filter 0.0499160289764
     449time  verif event Lhco_filter 0.0263900756836
     4502 selected  events for  ./SubProcesses/P0_gg_ttx_t_bmupvm_tx_bxmumvmx  subprocess
     451time Lhco_filter 0.0269908905029
     452submit_jobs
     453INFO:  Idle: 12,  Running: 8,  Completed: 0 [ current time: 16h58 ]
     454INFO:  Idle: 11,  Running: 8,  Completed: 1 [  8.8s  ]
     455INFO:  Idle: 10,  Running: 8,  Completed: 2 [  10.4s  ]
     456INFO:  Idle: 9,  Running: 8,  Completed: 3 [  11s  ]
     457INFO:  Idle: 8,  Running: 8,  Completed: 4 [  12.4s  ]
     458INFO:  Idle: 7,  Running: 8,  Completed: 5 [  13.7s  ]
     459INFO:  Idle: 6,  Running: 8,  Completed: 6 [  15.1s  ]
     460INFO:  Idle: 5,  Running: 8,  Completed: 7 [  20.4s  ]
     461INFO:  Idle: 4,  Running: 8,  Completed: 8 [  20.4s  ]
     462INFO:  Idle: 3,  Running: 8,  Completed: 9 [  23.4s  ]
     463INFO:  Idle: 2,  Running: 8,  Completed: 10 [  24.3s  ]
     464INFO:  Idle: 1,  Running: 8,  Completed: 11 [  25.6s  ]
     465INFO:  Idle: 0,  Running: 8,  Completed: 12 [  26.7s  ]
     466INFO:  Idle: 0,  Running: 7,  Completed: 13 [  27.9s  ]
     467INFO:  Idle: 0,  Running: 6,  Completed: 14 [  31.3s  ]
     468INFO:  Idle: 0,  Running: 5,  Completed: 15 [  32.2s  ]
     469INFO:  Idle: 0,  Running: 4,  Completed: 16 [  32.9s  ]
     470INFO:  Idle: 0,  Running: 3,  Completed: 17 [  33.5s  ]
     471INFO:  Idle: 0,  Running: 2,  Completed: 18 [  37s  ]
     472INFO:  Idle: 0,  Running: 1,  Completed: 19 [  37.3s  ]
     473INFO:  Idle: 0,  Running: 0,  Completed: 20 [  40.6s  ]
     474collect
     475Write output file with weight information: /Users/omatt/Documents/eclipse/madweight/TUTO_MW_MADWEIGHT/Events/fermi/weights.out
     476}}}
     477       5. The beginning of the output file is:{{{
     47821 1 1 1.67034745571e-27 1.88712282418e-29
     47921 1 2 5.01313265975e-28 2.00924122048e-29
     48021 1 3 6.40423688607e-29 2.02076553468e-29
     48121 2 1 1.39101532551e-27 1.58406349379e-29
     48221 2 2 4.12116704446e-28 1.73765684537e-29
     48321 2 3 5.18022329645e-29 1.75616795687e-29
     48421 3 1 3.10351972857e-28 2.58934359519e-30
     48521 3 2 8.44266819734e-29 2.90551251901e-30
     48621 3 3 9.80205747396e-30 2.93096140371e-30
     48721 4 1 4.93982689464e-28 5.87788490875e-30
     48821 4 2 1.47211327235e-28 6.52593427533e-30
     48921 4 3 1.91822859246e-29 6.60825546984e-30
     49021 5 1 9.45452606419e-28 1.0083326944e-29
     49121 5 2 2.93719655368e-28 1.12977034602e-29
     49221 5 3 3.94442924868e-29 1.14159825308e-29
     49322 1 1 0.0 0.0
     49422 1 2 0.0 0.0
     49522 1 3 0.0 0.0
     49622 2 1 0.0 0.0
     49722 2 2 0.0 0.0
     49822 2 3 0.0 0.0
     49922 3 1 0.0 0.0
     50022 3 2 0.0 0.0
     50122 3 3 0.0 0.0
     50222 4 1 0.0 0.0
     50322 4 2 0.0 0.0
     50422 4 3 0.0 0.0
     50522 5 1 0.0 0.0
     50622 5 2 0.0 0.0
     50722 5 3 0.0 0.0
     508}}}
     509       The first column being the event number, the second one being the theoretical hyppothesis number and the third one the TF number. The zero results typically shows case where one of the b-jet is missed in the beam and another jet is comming from some radiation.
     510
     511    6. You can check the precision of the run and refine the weights which are not precise enough. The command is the following:
     512       {{{./bin/mw_options}}}
     513       then type
     514       {{{refine 0.01}}}
     515       The code will then ask you if you want to edit the MW_card, it is advise to '''ONLY''' modify the following two parameters: MW_int_points and MW_int_refine.
     516
     517
     518    NOTE:
     519       * If only one transfer function would have been used the computation would have been done in 38.3s instead of 40.6s
     520       * The number of events selected are for each flavor of lepton if more than one flavor is present.
     521       * MadWeight selects the events in the event file corresponding to the expected topology (correct number of jets/lepton/...) The other events are discarded. 
     522
     523     
     524       
     525=== Analyse the output