Interference term using Reweighting.
Hi!
I am currently trying to generate the interference term in Di-higgs production between a tree level process and a loop level process in SMEFT.
The operator OpG introduces a contact interaction between gluons and higgs which gives the tree level diagram however the other BSM contributions and the SM contribution are at loop level.
I would like to generate the full process with OpG and SM or with some other Operator giving for example:
OpG^2 + interference + O_X^2 or OpG^2 + interference + SM^2, where X is some BSM operator entering at loop level.
I have been told to do the reweighting method to get this, using the following syntax:
generate g g > h h
and in the reweight card:
change process g g > h h NP=2 QCD=2 QED=2 QCD^2==2 NP^2==4 [virt=QCD]
Where NP=2 corresponds to 1 EFT insertion. NP counts the powers of 1/Lambda so NP=2 corresponds to only 1 EFT insertion.
My question is does this give me OpG^2 + interference + O_X^2 ?
or does it only for example the interference term and then I have to generate O_X^2 term separately and add them together?
or do I need to for examples do:
change process g g > h h NP=2 QCD=2 QED=2 QCD^2==2 NP^2==2 [virt=QCD] # NP^2 = 2 Gives me interference term
change process g g > h h NP=2 QCD=2 QED=2 QCD^2==2 NP^2==4 [virt=QCD] --add
to add the Op_X^2 contribution?
Thanks for your help!
All best,
Tom
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
![]() |
#1 |
Hi,
I do not know the model so I can not comment on the meaning for your process of all your coupling order constraint.
Now the syntax [virt=QCD] is using MadLoop in standalone mode and therefore you can refer to the MadLoop paper to know what that syntax means: https:/
Eq. 3.26 indicates that the code returns the interference between a born amplittude and a loop. (in term of 3 component since it also returns the non finite peace those have to be zero for the re-weighting to make sense obviously --this might not be checked on the flight--)
change process g g > h h NP=2 QCD=2 QED=2 QCD^2==2 NP^2==2 [virt=QCD] # NP^2 = 2 Gives me interference term
change process g g > h h NP=2 QCD=2 QED=2 QCD^2==2 NP^2==4 [virt=QCD] --add
No you can not assign more than one matrix-element for a re-weighting since then the reweighting module does not know which matrix element to use. Additionally at least one of the two synntax is likely not valid. If you are interested in a loop square contribution then you need to use another syntax: [sqvirt=QCD]
Cheers,
Olivier
Revision history for this message
![]() |
#2 |
Hi,
thanks a lot for you comments!
All best,
Tom
Revision history for this message
![]() |
#3 |
Hi again!
I ran in to an additional problem. I do scan:[X,Y] over some coupling in the param_card where X and Y are some numerical values. I do the reweighting and it works for the first scanned parameter but for the second one (independent of what it is, even if X=Y), it gives me the following error:
INFO: Combining Events
=== Results Summary for run: run_02 tag: tag_1 ===
Cross-section : 15.73 +- 0.01745 pb
Nb of events : 10000
store_events
INFO: Storing parton level results
INFO: End Parton
reweight -from_cards
INFO: Extracting the banner ...
INFO: process: p p > h h QCD = 0
INFO: options: QED = 2
INFO: Running Reweighting
change mode NLO # Define type of Reweighting. For LO sample this command
WARNING: Missing information for NLO type of reweighting. Keeping the mode to LO.
change process g g > h h NP=2 QCD=2 QED=2 QCD^2==2 NP^2==4 / g [virt=QCD]
launch --rwgt_
INFO: detected model: SMEFTatNLO-LO. Loading...
INFO: generating the square matrix element for reweighting
INFO: generate p p > h h QCD = 0 QED = 2 ;
Error detected in "generate_events run_01"
write debug file /scratch3/
If you need help with this issue please contact us on https:/
str : A compilation Error occurs when trying to compile /scratch3/
The compilation fails with the following output message:
cd DHELAS; make
make[1]: Entering directory `/scratch3/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
/cvmfs/
FFVV180_
Error: Symbol ‘f1’ at (1) has no IMPLICIT type; did you mean ‘f2’?
FFVV180_
F2(1) = +F1(1)+V3(1)+V4(1)
Error: Function ‘f1’ at (1) has no IMPLICIT type
FFVV180_
F2(2) = +F1(2)+V3(2)+V4(2)
Error: Function ‘f1’ at (1) has no IMPLICIT type
FFVV180_
F2(3) = +F1(3)+V3(3)+V4(3)
Error: Function ‘f1’ at (1) has no IMPLICIT type
FFVV180_
F2(4) = +F1(4)+V3(4)+V4(4)
Error: Function ‘f1’ at (1) has no IMPLICIT type
make[1]: *** [FFVV180_2.o] Error 1
make[1]: Leaving directory `/scratch3/
make: *** [../lib/
Please try to fix this compilations issue and retry.
Help might be found at https:/
If you think that this is a bug, you can report this at https:/
INFO: Original cross-section: 15.728 +- 0.017446 pb
INFO: Computed cross-section:
quit
INFO: storing files of previous run
gzipping output file: unweighted_
INFO: Done
INFO:
MG5_aMC>exit
Can I solve this somehow? Should it be possible to do scan in the param_card while using the reweighting method?
Thanks again!
All best,
Tom
Revision history for this message
![]() |
#4 |
Hi,
Can you create a bug report about this? Such that you can attach
1) the model
2) the param_card
3) the reweight_card
This will allow me to know what FFVV180 lorentz structure is and why it is not correctly define.
Thank,
Olivier
PS: please try to use a single topic per question since this is helpfull for the community for having short thread when they face the same issue
Revision history for this message
![]() |
#5 |
Hi,
okay I submitted a bug report.
No problem and thanks for your help!
All best,
Tom
PS: Ah, I'll keep that in mind, no problem!
Revision history for this message
![]() |
#6 |
second issue is tracked here: https:/
Can you help with this problem?
Provide an answer of your own, or ask tom ingebretsen carlson for more information if necessary.