Changes between Version 2 and Version 3 of WMassMeasurmentExample


Ignore:
Timestamp:
Apr 13, 2012, 9:05:21 AM (13 years ago)
Author:
Martin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WMassMeasurmentExample

    v2 v3  
    2525Note the log are done with version: 2.5.4
    2626
    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: {{{
     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:
     28{{{
    2829no mapping card found
    2930starting the creation of the param_card
    … …  
    3536       
    3637}}}
    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. {{{
     38   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.
     39{{{
    3840     treating MW_P1_uxd_e-vex directory
    3941structure of the configuration 1:
    … …  
    7880       
    7981}}}
    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/ {{{
     82   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/
     83{{{
    8184      name : fermi
    8285      schedullar
    … …  
    103106       
    104107}}}
    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. {{{
     108   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.
     109{{{
    106110                mkdir: cannot create directory `./Events/fermi': File exists
    107111                compiling
    … …  
    121125       
    122126}}}
    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. {{{
     127   1. $> ./bin/madweight.py -7 or ./bin/madweight.py control: control the cluster status. This is cluster related, so ntohing happen in this case.
     128{{{
    124129        name : fermi
    125130        schedullar
    … …  
    127132       
    128133}}}
    129    1. $> ./bin/madweight.py -8 or ./bin/madweight.py collect: collect all the different value {{{
     134   1. $> ./bin/madweight.py -8 or ./bin/madweight.py collect: collect all the different value
     135{{{
    130136       name : fermi
    131137       schedullar
    … …  
    142148       
    143149}}}
    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) {{{
     150   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)
     151{{{
    145152        charge file  ./Events/fermi/fermi_weights.out
    146153        load cross section term ./Events/fermi/fermi_cross_weights.out
    147154        no acceptance term loaded
    148155       
    149 }}} At this stage all the output are in ./Events/fermi/ For example the computation of the likelihood (whitout the AcceptanceTerm) gives: {{{
     156}}}
     157At this stage all the output are in ./Events/fermi/ For example the computation of the likelihood (whitout the AcceptanceTerm) gives:
     158{{{
    150159        1.       40      228.955053585   0.000715345946119
    151160        2.       60      188.48197688    0.000750658557815
    … …  
    154163        5.       120     168.413249969   0.00123941979677
    155164       
    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)
     165}}}
     166The 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)
    157167
    158168-- Main.OlivierMattelaer - 14 Sep 2009