MadGraph5_aMC@NLO

TW+X production in MG5_3.5.X with and without MadSTR

Asked by Andrej Saibel

Dear all,

I'm trying to produce a sample of tWZ and tWH with MG5_aMC_v3_5_2.
However, using python3.9 bin/mg5_aMC --mode=MadSTR gives me the error

Plugin PLUGIN.MadSTR is not supported by this version of MG5aMC.

Does MadSTR work with 3.5.X or is there a way to perform DR/DS with these versions?
Is there documentation on which amplitudes are to be removed with the new way how they're written out into the matrix_X.f files?

Kind regards,

Andrej

Question information

Language:
English Edit question
Status:
Answered
For:
MadGraph5_aMC@NLO Edit question
Assignee:
marco zaro Edit question
Last query:
Last reply:
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said : 		#1

As far as I know MadSTR is not 3.x compatible.

I assign this to Marco in case more details are needed.

Olivier

Revision history for this message
Andrej Saibel (asaibel) said : 		#2

Dear all,
thank you very much for your answer.

Could you please provide an example of how to produce tW processes in MG5 3.5?
If I remove the same diagrams in the matrix.f files as were removed in the past for earlier versions, I get a 20% difference in the total cross-section.

Thank you very much.

Kind regards,

Andrej

Revision history for this message
marco zaro (marco-zaro) said : 		#3

Hi,
in principle you should just set to zero the AMP(i) corresponding to the feynman diagrams where the top resonates...
When you say you get 20% difference, are you sure you are using the very same settings?

Thanks!

Marco

Revision history for this message
Hesham El Faham (helfaham) said : 		#4

Hi Andrej,

As Olivier mentioned, Mad_STR is not compatible with 3. X.

Suppose you followed Marco's suggestion by setting the AMP(i)= DCMPLX(0D0,0D0) in the relevant matrix_*.f files for the resonant amplitudes, you should be able to cross-check with MadSTR in v2 using the DR1 setting in the run_card. The latter setting removes all the resonant amplitudes.
The DR2 setting keeps the interference between the resonant and the non-resonant terms and its handling in the matrix_*.f files is a bit more involved than DR1.

Please let me know if you need more help.

Best,
Hesham

Can you help with this problem?

Provide an answer of your own, or ask Andrej Saibel for more information if necessary.

To post a message you must log in.