This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
2017:groups:tools:resonance_aware [2017/06/12 19:04] emanuele.re |
2017:groups:tools:resonance_aware [2017/06/12 19:10] emanuele.re |
||
---|---|---|---|
Line 30: | Line 30: | ||
* make sure that numerical accuracy reached in event generation from MC is the same as in TH-paper | * make sure that numerical accuracy reached in event generation from MC is the same as in TH-paper | ||
- | * possible to have grids from the authors (seems to be a viable solution, as atlas and cms will agree - or already agreed - on the settings | + | * possible to have grids from the authors (seems to be a viable solution, as atlas and cms will agree - or already agreed - on the settings) |
* if grids will be provided, need to agree on parameters to scan upon. It seems that order 20 runs will be enough (a scan would mostly be done using 5-10 values for mtop, and 2-3 values for hdamp) | * if grids will be provided, need to agree on parameters to scan upon. It seems that order 20 runs will be enough (a scan would mostly be done using 5-10 values for mtop, and 2-3 values for hdamp) | ||
- | * | + | * It might even be possible to use the powheg reweighting machinery to avoid having to re-run all the grids. This might depend on how far mtop is moved from the central value. T. Jezo and collaborators have tried this. Perhaps it'd be useful to perform a closure-test, but using the outermost mtop values that atlas/cms would use. |
+ | |||
+ | * this reweighting would be missing mtop dependence in R/B | ||