Changes between Version 10 and Version 11 of ComplexMassScheme


Ignore:
Timestamp:
Aug 13, 2015, 2:58:34 AM (9 years ago)
Author:
Valentin Hirschi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ComplexMassScheme

    v10 v11  
    3838Finally, the following options are available and we detail their usage in the next sections.
    3939
     40 * Basic options
     41   * {{{ --name }}}
     42   * {{{ --tweak }}}
     43   * {{{ --seed }}}
     44   * {{{ --offshellness }}}
     45   * {{{ --energy }}}
     46   * {{{ --lambdaCMS }}}
     47   * {{{ --show_plot }}}
     48   * {{{ --recompute_width }}}
     49   * {{{ --CTModeRun }}}
     50   * {{{ --helicity }}}
     51   * {{{ --reduction }}}
     52 * More technical options
     53   * {{{ --cms }}}
     54   * {{{ --diff_lambda_power }}}
     55   * {{{ --loop_filter }}}
     56   * {{{ --resonances }}}
     57 * Special option
     58   * {{{ --analyze }}}
     59
    4060== Basic options ==
    4161
     
    4363   This will serve as the base_name for the fortran output folder for the loop matrix element and for the pickle files storing the results generated. The default 'auto' tries to smartly automatically assign one, but it is recommended to specify your own.
    4464   * Example: --name=fully_decayed_ttx
     65
     66 {{{--tweak=default()}}}::
     67   The tweak option is an important one as it lets you automatically performs changes to the computational setup which should deteriorate the quality of the CMS check (i.e. induce non-zero values of $\kappa^{\text{NLO}}_0$) so that one can appreciate to which level of accuracy the current implementation is consistent. The keyword 'default' means no changes and would yield the blue curve in the figures below. What follows the tweak in parenthesis is its name which will be used to label the curve and to build the name of the pickle file storing this tweak. Possible tweak ares:
     68   * <param_name>->expr(<param_name>): for instance 'WZ->1.1*WZ' would multiply the LO-accurate Z-boson width by 10%. Notice that you can use the keyword 'allwidths' which will automatically apply the rule to all widths.
     69   * seed<int>: for instance seed669 which specifies that for this tweak one must change the seed to value <int>
     70   * [logp|logm|log]->[logp|logm|log]: for instance logp->logm which would change the matrix element fortran output so as to change the logarithms continued with '+2$\pi$i'  to '-2$\pi$i'
     71 These tweaks can be chained together with the symbol '&' to form a bigger tweak, e.g. '--tweak=WZ->1.01*WZ&logp->logm&logm->logp(Widths_changed_and_log_inverted)' which runs the CMS test with both the logs inverted and the width changed. Finally, one can put these global tweak in a list (with string quotes) to have MG5_aMC run them one after the other (if their pickle file is not found and recycled) and plot together.
     72   * Example: --tweak=['default','allwidths->1.1*all_withds&seed333(Increased_widths_and_seed_333)','logp->logm&logm->logp(inverted_logs)']
     73 In this case one will make the CMS test successively in three different setups. The first one is the original one (where it is supposed to pass). The second one is for a different kinematic configuration and all widths increased by 10%. Finally the last one inverts the analytic continuation of all logs.
     74   * Example: --tweak=alltweaks
     75 This is a shorthand for the specification of all tweaks typically relevant;
     76 that is --tweak=['default','seed667(seed667)','seed668(seed668)','allwidths->0.9*allwidths(widths_x_0.9)','allwidths->0.99*allwidths(widths_x_0.99)','allwidths->1.01*allwidths(widths_x_1.01)','allwidths->1.1*allwidths(widths_x_1.1)','logp->logm(logp2logm)','logm->logp(logm2logp)']
    4577
    4678 {{{--seed=666}}}::
     
    71103   * Example: --recompute_width=never
    72104
    73 == Special option ==
     105 {{{--CTModeRun=-1}}}::
     106    By default MadLoop will run in double precision, make stability tests and only if they are unsuccessful go to quadruple precision. Given the nature of the cancellation we are probing with this test, the $\Delta/\lambda$ plot can quickly become unstable for complicated processes and low $\lambda$ values. It is then necessary to force MadLoop to perform the test in quadruple precision. This can be done by changing this option from its default -1 (which is where it performs stability tests) to 4 (forced quadruple precision).
     107   * Example: --CTModeRun=4
    74108
    75  {{{--analyze=None}}}::
    76     This option must be used without any process definition. It is intended to specify the path of pickle files storing the results of previous results to be re-analyzed and replotted. A common usage of this option is:
    77    * Example: check cms --analyze=my_default_run.pkl,increased_widths.pkl(Increased_widths),logs_modified.pkl(Inverted_logs),seed_668.pkl(Different_seed)
    78  This will reanalyze the data in my_default_run.pkl and plot them while also including the curves from the list of pickle paths following the first one. The name in parenthesis will serve as the legend (underscores will be replaced by spaces)
     109 {{{--helicity=-1}}}::
     110    The default value of -1 means that the test is performed with the matrix element summed over all helicity configurations. This can be slow when enforcing quadruple precision and looking at complicated processes. With this parameter set to '--helicity=<int>', the matrix elements will be evaluated on only the helicity configuration #<int> (check their order in the file HelConfigs.dat of the directory MadLoop5Resources output along with the process).
     111   * Example: --helicity=1
     112
     113 {{{--reduction=1|2|3|4}}}::
     114    Specifies which reduction method to use and in which order (see comments on the option #MLReductionLib of the card MadLoopParams.dat for details.)
     115   * Example: --reduction=3|1
     116 This examples tell MadLoop to first try reducing with IREGI and then CutTools if unstable, but never use PJFry or Golem95.
    79117
    80118== More technical options ==
     
    103141   * Example:  --resonances=[(24,(3,4)),(24,(4,5))]
    104142 Run on the kinematic configurations generated starting from a W and a Z (decaying into particles 3,4 and 4,5 respectively).
     143
     144== Special option ==
     145
     146 {{{--analyze=None}}}::
     147    This option must be used without any process definition. It is intended to specify the path of pickle files storing the results of previous results to be re-analyzed and replotted. A common usage of this option is:
     148   * Example: check cms --analyze=my_default_run.pkl,increased_widths.pkl(Increased_widths),logs_modified.pkl(Inverted_logs),seed_668.pkl(Different_seed)
     149 This will reanalyze the data in my_default_run.pkl and plot them while also including the curves from the list of pickle paths following the first one. The name in parenthesis will serve as the legend (underscores will be replaced by spaces)