2013:groups:sm:blha
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
2013:groups:sm:blha [2013/08/13 09:27] gudrun.heinrich |
2013:groups:sm:blha [2013/08/13 09:30] gudrun.heinrich |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| //Comments:// | //Comments:// | ||
| - | Concerning full SM corrections, they can be accommodated by the interface (possibly split into several contributions) if AlphasPower, AlphaPower and CorrectionType can be specified on per-process basis. | + | Concerning full SM corrections, they can be accommodated by the interface (possibly split into several contributions) if CouplingPower QCD, CouplingPower QED and CorrectionType can be specified on per-process basis. |
| PDF information (if it is available) like the number of flavours used in the running coupling can be passed from MC via OLP_SetParameter. | PDF information (if it is available) like the number of flavours used in the running coupling can be passed from MC via OLP_SetParameter. | ||
| Line 19: | Line 19: | ||
| ==== Precision setting and OLP_EvalSubProcess ==== | ==== Precision setting and OLP_EvalSubProcess ==== | ||
| - | The threshold of accuracy below which the point should be considered unstable is set in the order file using | + | The target accuracy the user would like to reach is set in the order file using |
| - | <code>Precision 1e-4</code> | + | <code>AccuracyTarget 0.0001</code> |
| The information of whether accuracy has been reached is returned to MC via extra integer parameter **rstatus** | The information of whether accuracy has been reached is returned to MC via extra integer parameter **rstatus** | ||
2013/groups/sm/blha.txt · Last modified: 2013/08/13 09:33 by gudrun.heinrich
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
