This is a feature which works as describe in the manual. So this is not my definition of bug.
But the definition of a feature which doesn’t work as some people expects.
So this is indeed a feature request and not a bug.
Cheers,
Olivier
On Apr 30, 2014, at 1:06 AM, Rakhi Mahbubani <email address hidden> wrote:
> Dear Olivier,
>
> I think in the auto_ptj_mjj documentation refers to directly-produced
> jets (e.g. the forward jets in WBF) and not decay products. I would
> expect any cuts on the latter to be solely controlled by the cut_decays
> flag. In this case, I would agree with Rikkert that this is a bug.
> Moreover MG/ME gives (me at least) a wildly incorrect cross section for
> the process. This is exactly the problem I was describing in my bug
> report #1311186.
>
> Cheers,
>
> Rakhi
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1243543
>
> Title:
> automatic ptj and mjj cuts from xqcut are also applied to jets that
> are not relevant for the matching
>
> Status in MadGraph5_aMC@NLO Generator:
> Triaged
>
> Bug description:
> Hi Olivier,
>
> When doing matching, for example for ttbar production, including hadronic decays, the auto_ptj_mjj flag and the cut_decays flag are not working as expected. I would have expected that, no matter what I put for the cut_decays flag, the ptj and mjj cuts that are set automatically from the xqcut with the auto_ptj_mjj are always only applied to the jets that enter the matching, and certainly not to the top quark decay products.
> Moreover, it's not so easy to spot that this is going wrong, because all the matching plots are rather smooth. Only the cross section is a bit lower than expected.
>
> Cheers,
> Rikkert
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/1243543/+subscriptions
Dear Rakhi,
This is a feature which works as describe in the manual. So this is not my definition of bug.
But the definition of a feature which doesn’t work as some people expects.
So this is indeed a feature request and not a bug.
Cheers,
Olivier
On Apr 30, 2014, at 1:06 AM, Rakhi Mahbubani <email address hidden> wrote:
> Dear Olivier, /bugs.launchpad .net/bugs/ 1243543 /bugs.launchpad .net/mg5amcnlo/ +bug/1243543/ +subscriptions
>
> I think in the auto_ptj_mjj documentation refers to directly-produced
> jets (e.g. the forward jets in WBF) and not decay products. I would
> expect any cuts on the latter to be solely controlled by the cut_decays
> flag. In this case, I would agree with Rikkert that this is a bug.
> Moreover MG/ME gives (me at least) a wildly incorrect cross section for
> the process. This is exactly the problem I was describing in my bug
> report #1311186.
>
> Cheers,
>
> Rakhi
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> Title:
> automatic ptj and mjj cuts from xqcut are also applied to jets that
> are not relevant for the matching
>
> Status in MadGraph5_aMC@NLO Generator:
> Triaged
>
> Bug description:
> Hi Olivier,
>
> When doing matching, for example for ttbar production, including hadronic decays, the auto_ptj_mjj flag and the cut_decays flag are not working as expected. I would have expected that, no matter what I put for the cut_decays flag, the ptj and mjj cuts that are set automatically from the xqcut with the auto_ptj_mjj are always only applied to the jets that enter the matching, and certainly not to the top quark decay products.
> Moreover, it's not so easy to spot that this is going wrong, because all the matching plots are rather smooth. Only the cross section is a bit lower than expected.
>
> Cheers,
> Rikkert
>
> To manage notifications about this bug go to:
> https:/