Changes between Version 1 and Version 2 of WMassMeasurmentExample


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

--

Legend:

Unmodified
Added
Removed
Modified
  • WMassMeasurmentExample

    v1 v2  
    55==== Prepare the directory ====
    66
    7    1. Duplication of Template directory $>cp -r Template First_test
    8    1. Change diretory: $> cd First_test
    9    1. Switch to MadWeight mode: $> ./bin/PassToMadWeight
    10    1. Parametrize the proc_card.dat. For this example the decay chain is the following one: pp>(W+>e+ve) and the transfer functions is dbl_gauss_pt_jet (the one foreseen for PGS in the CMS-like configuration). You can download this [attachment:proc_card.dat proc_card here].
    11    1. Generate the process: $> ./bin/newprocess
     7   1. Duplication of Template directory $>cp -r Template First_test
     8   1. Change diretory: $> cd First_test
     9   1. Switch to MadWeight mode: $> ./bin/PassToMadWeight
     10   1. Parametrize the proc_card.dat. For this example the decay chain is the following one: pp>(W+>e+ve) and the transfer functions is dbl_gauss_pt_jet (the one foreseen for PGS in the CMS-like configuration). You can download this [attachment:proc_card.dat proc_card here].
     11   1. Generate the process: $> ./bin/newprocess
    1212   1. Put the events sample in the ./Events directory under the name input.lhco. Our events sample is generated with MadGraph/Pythia/PGS: and is available [attachment:input.lhco here].
    1313
     
    2525Note the log are done with version: 2.5.4
    2626
    27    1. $&gt;./bin/madweight.py -1 or $&gt;./bin/madweight.py param:<br /> Create the different param_card and files related to the different cards.<br /> output: {{{
     27   1. $>./bin/madweight.py -1 or $>./bin/madweight.py param:[[br]] Create the different param_card and files related to the different cards.[[br]] output: {{{
    2828no mapping card found
    2929starting the creation of the param_card
     
    3333create file ./Source/madweight_card.inc
    3434create file ./Source/MadWeight_File/Transfer_Fct/transfer_card.inc
    35        }}}
    36    1. $&gt; ./bin/madweight.py -2 or $&gt; ./bin/madweight.py analyzer:<br /> Analyzes the Feynman diagrams, the transfer function and creates the fortran code for the integration.<br /> output, indicates how MW analyzes your decay chains. and which change of variable it will apply on it. {{{
     35       
     36}}}
     37   1. $> ./bin/madweight.py -2 or $> ./bin/madweight.py analyzer:[[br]] Analyzes the Feynman diagrams, the transfer function and creates the fortran code for the integration.[[br]] output, indicates how MW analyzes your decay chains. and which change of variable it will apply on it. {{{
    3738     treating MW_P1_uxd_e-vex directory
    3839structure of the configuration 1:
     
    5859Blob details: main 3
    5960blob generation: [0||3 :]
    60      }}}
    61    1. $&gt; ./bin/madweight.py -3 or $&gt; ./bin/madweight.py compilation: Compilation of the code. (Long and pointless output)
    62    1. $&gt; ./bin/madweight.py -4 or ./bin/madweight.py event: Check if the events in the input.lhco files are coherent for each subprocesses. {{{
     61     
     62}}}
     63   1. $> ./bin/madweight.py -3 or $> ./bin/madweight.py compilation: Compilation of the code. (Long and pointless output)
     64   1. $> ./bin/madweight.py -4 or ./bin/madweight.py event: Check if the events in the input.lhco files are coherent for each subprocesses. {{{
    6365      name : fermi
    6466time  init Lhco_filter 0.0028760433197
     
    7476schedullar
    7577done
    76        }}}
    77    1. $&gt; ./bin/madweight.py -5 or ./bin/madweight.py dir: Creates the directory for each parralel run. The name of the directory is for cross-section computation: ./SubProcesses/P1_uxd_e-vex/fermi/card_1/ for weight computation:./SubProcesses/MW_P1_uxd_e-vex/fermi/card_1/event_0/ {{{
     78       
     79}}}
     80   1. $> ./bin/madweight.py -5 or ./bin/madweight.py dir: Creates the directory for each parralel run. The name of the directory is for cross-section computation: ./SubProcesses/P1_uxd_e-vex/fermi/card_1/ for weight computation:./SubProcesses/MW_P1_uxd_e-vex/fermi/card_1/event_0/ {{{
    7881      name : fermi
    7982      schedullar
     
    98101      created 100 directories
    99102      done
    100        }}}
    101    1. $&gt; ./bin/madweight.py -6 or ./bin/madweight.py launch: Launches the computation of the weights on the cluster. (here by default on a single machine. {{{
     103       
     104}}}
     105   1. $> ./bin/madweight.py -6 or ./bin/madweight.py launch: Launches the computation of the weights on the cluster. (here by default on a single machine. {{{
    102106                mkdir: cannot create directory `./Events/fermi': File exists
    103107                compiling
     
    115119                ...(lot of launch ../../../comp_madweight)...
    116120                launch ../../madevent.py
    117        }}}
    118    1. $&gt; ./bin/madweight.py -7 or ./bin/madweight.py control: control the cluster status. This is cluster related, so ntohing happen in this case. {{{
     121       
     122}}}
     123   1. $> ./bin/madweight.py -7 or ./bin/madweight.py control: control the cluster status. This is cluster related, so ntohing happen in this case. {{{
    119124        name : fermi
    120125        schedullar
    121126        done
    122        }}}
    123    1. $&gt; ./bin/madweight.py -8 or ./bin/madweight.py collect: collect all the different value {{{
     127       
     128}}}
     129   1. $> ./bin/madweight.py -8 or ./bin/madweight.py collect: collect all the different value {{{
    124130       name : fermi
    125131       schedullar
     
    134140       /data/0/O/omatt/MG_ME/TEST_MW2
    135141       /data/0/O/omatt/MG_ME/TEST_MW2
    136        }}}
    137    1. $&gt; ./bin/madweight.py -9 or ./bin/madweight.py plot: compute the likelihood and try to make plot (here I don't have gnuplot on my cluster, so it fails) {{{
     142       
     143}}}
     144   1. $> ./bin/madweight.py -9 or ./bin/madweight.py plot: compute the likelihood and try to make plot (here I don't have gnuplot on my cluster, so it fails) {{{
    138145        charge file  ./Events/fermi/fermi_weights.out
    139146        load cross section term ./Events/fermi/fermi_cross_weights.out
    140147        no acceptance term loaded
    141        }}} At this stage all the output are in ./Events/fermi/ For example the computation of the likelihood (whitout the AcceptanceTerm) gives: {{{
     148       
     149}}} At this stage all the output are in ./Events/fermi/ For example the computation of the likelihood (whitout the AcceptanceTerm) gives: {{{
    142150        1.       40      228.955053585   0.000715345946119
    143151        2.       60      188.48197688    0.000750658557815
     
    145153        4.       100     159.014840519   0.00113245384668
    146154        5.       120     168.413249969   0.00123941979677
    147        }}} The first column is the card_number, the second the W mass, the third the value of the likelihood, and the last one the error associate. In this simple example, we can claim that the correct mass is around 80 GeV. (In this case, the error is dominated by the binning)
     155       
     156}}} The first column is the card_number, the second the W mass, the third the value of the likelihood, and the last one the error associate. In this simple example, we can claim that the correct mass is around 80 GeV. (In this case, the error is dominated by the binning)
    148157
    149158-- Main.OlivierMattelaer - 14 Sep 2009
     
    158167
    159168
     169