fail to reach target events

Asked by Gennaro Corcella

Hello, I am using version 3.4.1 and the following steps:
import model heft
generate p p > h > mu+ mu- mu+ mu- / a

Then, regardless of whether I use the Pyhtia interface or not for the parton shower, I always get:
fail to reach target events

Could you help me please?

Thanks, Gennaro

Question information

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

Hi,

For some reason, I do not have that issue with the Long Term Stable, so I'm going to investigate why this process does not have the same efficiency compare to our LTS version.

But the quick work around is to use our LTS version.

Cheers,

Olivier

Revision history for this message
Gennaro Corcella (gcorcella) said :
#2

Hello,

Thank you. What do you mean by LTS version, version 2.9.12 (downloadable from https://launchpad.net/mg5amcnlo) ?

Cheers, Gennaro

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#3

Yes, 2.9.12 is the latest bug fix release for our LTS version.

Cheers,

Olivier

Revision history for this message
Gennaro Corcella (gcorcella) said :
#4

Hello Oliver,

Thanks for your further message. However, I installed mg5_amc_v2_9_12 and I still get. e.g., fail to reach target 5000'.

Any idea on how to fix this problem?

Gennaro

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#5

You did keep all default value correct?

I have run the following script
import model heft
generate p p > h > mu+ mu- mu+ mu- / a
output
launch -f

and it was working... Weird that it does not work for you...
To be honest I'm using the alpha version of 2.9.13 but I doubt that this is the reason (but will double check)

Cheers,

Olivier

Revision history for this message
Best Olivier Mattelaer (olivier-mattelaer) said :
#6

So yes indeed, this will be fixed in the next LTS version.
The change is just the default integration strategy which is going to change,
so the solution is to edit the run_card and set sde_strategy = 1
that should solve the problem in this case.

Cheers,

Olivier

Revision history for this message
Gennaro Corcella (gcorcella) said :
#7

Hello,

Thanks a lot. It does work after setting sde_strategy = 1 in the run_card.

By the way, is there any way to set this option in the source code at the beginning, rather than on the fly during the event simulation?

Thanks again,

Gennaro

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#8

In principle you can change the file
Template/LO/Cards/run_card.dat and hardcode the value that you want to change.
But I have never did it (so some side effect are not out of the equation)

I personally just use script like this

import model heft
generate p p > h > mu+ mu- mu+ mu- / a
output
launch
set SDE_strategy 1

that allow me to edit the cards without to have to edit the file and does not impact any other future run.

Cheers,

Olivier

Revision history for this message
Gennaro Corcella (gcorcella) said :
#9

Hello,

Indeed, hardcoding the value creates other problems, while the script on the fly works well.

Thanks again,

Gennaro

Revision history for this message
Gennaro Corcella (gcorcella) said :
#10

Thanks Olivier Mattelaer, that solved my question.