Comment 12 for bug 1731086

Dear Olivier,

thanks for your reply and for your checks. I tried to replicate your test in 2.6.0 and 2.3.3, but this time included a cut on ktdurham (as is used in our setup).

I ran the following:
 import model mssm
 generate p p > go go
 add process p p > go go j
 output -f
 launch
 set ickkw 0
 set xqcut 0
 set mgo 1000
 set ktdurham 250

It looks as though you have been able to set ktdurham since 2.0.0, which we understood is needed for CKKW-L merging?

The results we get are as follows:

2.6.0
cross-section 0.2005 pm 0.000402 pb

2.3.3
cross-section 0.19147 pm 0.000345 pb

Here the p2 cross-sections increase by 50% in 2.3.3 wrt 2.6.0.

We didn't make any hack to 2.3.3 in order to deal with CKKW-L merging, we understood that the configuration should work as is. I guess the question is did the behaviour of the ktdurham variable change significantly between 2.3.3 and 2.6.0?

Thanks,
Emma & Zach