Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Understand LHE files despite wrong XML #219

Open
johannbrehmer opened this issue Jan 21, 2019 · 1 comment
Open

Understand LHE files despite wrong XML #219

johannbrehmer opened this issue Jan 21, 2019 · 1 comment

Comments

@johannbrehmer
Copy link
Collaborator

johannbrehmer commented Jan 21, 2019

The LHE files that MadGraph produces ostensibly conform to the XML standard. But sometimes MadGraph produces headers that crudely violate this standard, for instance in this part about the weight groups:

<weightgroup name="PDF4LHC15_nlo_30" combine="symmhessian"> # 90900: PDF4LHC15_nlo_30. mem=0 ; alphas(MZ)=0.118 central value; mem=1-30 ; PDF symmetric eigenvectors
<weight id="5" MUR="1.0" MUF="1.0" PDF="90900" >  </weight>
[...]
<weight id="35" MUR="1.0" MUF="1.0" PDF="90930" > PDF=90900 MemberID=30 </weight>
<weightgroup name="Central scale variation" combine="envelope">
</weightgroup> PDF
<weight id="36" MUR="1.0" MUF="1.0" DYN_SCALE="1" PDF="90900" > dyn_scale_choice=sum pt  </weight>
[...]
<weight id="39" MUR="1.0" MUF="1.0" DYN_SCALE="4" PDF="90900" > dyn_scale_choice=sqrts  </weight>
</weightgroup>

(two lines in the middle are swapped).

I'm not sure what exactly triggers this MadGraph behavior (I've seen it when calculating PDF uncertainties with PDF4LHC, but it was fine with CTEQ14nlo and identical settings otherwise).

But this can be a problem for MadMiner, which relies on an XML parser to read the weight setup and the events. In this particular example, the weights related to the PDF uncertainties are not identified out properly.

We should

  • talk to MadGraph people to understand this behavior, and
  • make sure it doesn't happen, or repair the files before reading them.
@johannbrehmer johannbrehmer added bug Something isn't working high priority Should be fixed as soon as possible labels Jan 21, 2019
@johannbrehmer johannbrehmer self-assigned this Jan 21, 2019
@johannbrehmer
Copy link
Collaborator Author

Actually, it seems that the parsing is pretty robust to some errors in the XML. My isssue came from something else (now fixed). I'll leave this open, but it might not be super important.

@johannbrehmer johannbrehmer removed bug Something isn't working high priority Should be fixed as soon as possible labels Jan 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants