Changes between Version 23 and Version 24 of Reweight


Ignore:
Timestamp:
Feb 1, 2016, 4:15:52 PM (9 years ago)
Author:
Olivier Mattelaer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Reweight

    v23 v24  
    150150 
    151151 The cards is compose of two sections:
    152  1. '''Options'': those are options which change the behavior of the reweighting. Those lines need to be specified before the first 'launch' line to have effects.
    153    1. "change model <XXX>" performed the reweighting within a new model (you then need to profide a full param_card and not a difference)
    154    2. "change process <XXX>" change the process definition of the process.
    155    3. "change process <XXX> --add" add one process definition of the process to the new list.
    156    4. "change output <i>": Three options: 'default'(i.e. lhef version3 format), '2.0' (i.e. lhef version2 format, the main weight is replace), 'unweight' (a new unweighting is applied on the events sample.)
    157    5. "change helicity <True|False>": perform reweighting for the given helicity (True --default--) or do the sum over helicity.
    158    6. "change rwgt_dir <PATH>": change directory where the computation is performed. This can be use to avoid to recreate/recompile the fortran executable if pointing to a previously existing directory.
    159    7. change mode LO: For NLO sample, this flag force to use the kamikaze reweighting (available in 2.4.0)
    160 
    161  2. '''benchmark definition''': starting one benchmark starts with the line
    162     {{{
     152 1. '''Options''': [[BR]]
     153   Those are options which change the behavior of the reweighting. Those lines need to be specified before the first 'launch' line to have effects.
     154   1. '''change model <XXX>''' performed the reweighting within a new model (you then need to profide a full param_card and not a difference)
     155   2. '''change process <XXX>''' change the process definition of the process.
     156   3. '''change process <XXX> --add''' add one process definition of the process to the new list.
     157   4. '''change output <i>''': Three options: 'default'(i.e. lhef version3 format), '2.0' (i.e. lhef version2 format, the main weight is replace), 'unweight' (a new unweighting is applied on the events sample.)
     158   5. '''change helicity <True|False>''': perform reweighting for the given helicity (True --default--) or do the sum over helicity.
     159   6. '''change rwgt_dir <PATH>''': change directory where the computation is performed. This can be use to avoid to recreate/recompile the fortran executable if pointing to a previously existing directory.
     160   7. '''change mode LO''': For NLO sample, this flag force to use the kamikaze reweighting (available in 2.4.0)
     161
     162 2. '''benchmark definition''':[[BR]]
     163   Starting one benchmark starts with the line
     164   {{{
    163165launch
    164166    }}}
    165     then you can have either a series of "set command" to specify how to edit the param_card from the original one. Are a couple of equivalent options:
    166     {{{
     167   then you can have either a series of "set command" to specify how to edit the param_card from the original one. Are a couple of equivalent options:
     168   {{{
    167169    set mt 150
    168170    set mass 6 150
    169171    }}} 
    170     For a scan over parameter, you can use one of the following options (all are equivalent):
    171     {{{
     172   instead of using the "set command" you can also specify the path to a (valid) param_card
     173   {{{
     174    PATH
     175    }}}
     176   For a scan over parameter:
     177   1. You can have multiple line "launch" in the file, each of them followed by the associated "set" lines
     178   2. You can use the scan syntax of MadGraph5_aMC@NLO and use one of the following syntax:
     179   {{{
    172180    set mt 6 scan:range(100,200,20)
    173181    set mass 6 scan:[100,120,140,160,180]
    174182    }}}
    175     instead of using the "set command" you can also specify the path to a (valid) param_card
    176     {{{
    177     PATH
    178     }}}
     183
    179184
    180185 === Options of the code: