Madspin error on Generating NLO WH production in same signa final state

Asked by Siew Yan HOH on 2019-07-08

Hello expert,

I am having a madspin issue in generating my signal samples, please find the information below:

I am intend to generate W(lv)H, with H -> W(lv) W(jj), with l to be same sign.

Runcard:

import model loop_sm-ckm_no_b_mass
define p = p b b~
define j = j b b~

generate p p > w- h [QCD] @0
add process p p > w- h j [QCD] @1
add process p p > w- h j j [QCD] @2

output Wminush012j_5f_NLO_FXFX_M125_WToLV -nojpeg

Madspin Card:

set max_running_process 1
set spinmode none

define l = mu- e-
define v = vm~ ve~
decay h > w+ w- > j j l v

At the end of the compilation, i gotten a warning message:

WARNING: Order of particle in the event did not agree with parent/child order. This might be problematic for some code.

If i launch the event generation i have gotten error message:

INFO: Starting run
INFO: Compiling the code
INFO: Starting run
INFO: Using 4 cores
INFO: Generating events without running the shower.
INFO: Updating the number of unweighted events per channel

      Intermediate results:
      Random seed: 123243
      Total cross section: 1.181e+00 +- 2.3e-03 pb
      Total abs(cross section): 2.872e+00 +- 2.4e-03 pb

INFO: Generating events
WARNING: program /uscms_data/d3/shoh/private_production/running_from_tarball/tarballNLO/tmp/process/SubProcesses/P1_uxd_wmhg/ajob1 1 F 0 2 launch ends with non zero status: 127. Stop all computation
INFO: Idle: 106, Running: 0, Completed: 4 [ current time: 09h05 ]

then its stayed stuck.

Am i missing something? Thanks

Cheers,

Siewyan

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Siew Yan HOH
Solved:
2019-07-10
Last query:
2019-07-10
Last reply:
2019-07-10

This question was reopened

Hi,

According to "https://stackoverflow.com/questions/1763156/127-return-code-from"

Value 127 is returned by /bin/sh when the given command is not found within your PATH system variable and it is not a built-in shell command. In other words, the system doesn't understand your command, because it doesn't know where to find the binary you're trying to call.

So looks like that you have a configuration error in your cluster/setup.
Note that this is not linked to MadSpin at all.
Maybe this is lhapdf which is not set on the node that you run or someting else.

If you look at the log file in:

/uscms_data/d3/shoh/private_production/running_from_tarball/tarballNLO/tmp/process/SubProcesses/P1_uxd_wmhg/GXXXX

(not sure what XXXX is in this case) you might have more information on what is the missing executable.

Cheers,

Olivier

On 8 Jul 2019, at 17:13, Siew Yan HOH <<email address hidden><mailto:<email address hidden>>> wrote:

Question #681854 on MadGraph5_aMC@NLO changed:
https://answers.launchpad.net/mg5amcnlo/+question/681854

Description changed to:

Hello expert,

I am having a madspin issue in generating my signal samples, please find
the information below:

I am intend to generate W(lv)H, with H -> W(lv) W(jj), with l to be same
sign.

Runcard:

import model loop_sm-ckm_no_b_mass
define p = p b b~
define j = j b b~

generate p p > w- h [QCD] @0
add process p p > w- h j [QCD] @1
add process p p > w- h j j [QCD] @2

output Wminush012j_5f_NLO_FXFX_M125_WToLV -nojpeg

Madspin Card:

set max_running_process 1
set spinmode none

define l = mu- e-
define v = vm~ ve~
decay h > w+ w- > j j l v

At the end of the compilation, i gotten a warning message:

WARNING: Order of particle in the event did not agree with parent/child
order. This might be problematic for some code.

If i launch the event generation i have gotten error message:

INFO: Starting run
INFO: Compiling the code
INFO: Starting run
INFO: Using 4 cores
INFO: Generating events without running the shower.
INFO: Updating the number of unweighted events per channel

     Intermediate results:
     Random seed: 123243
     Total cross section: 1.181e+00 +- 2.3e-03 pb
     Total abs(cross section): 2.872e+00 +- 2.4e-03 pb

INFO: Generating events
WARNING: program /uscms_data/d3/shoh/private_production/running_from_tarball/tarballNLO/tmp/process/SubProcesses/P1_uxd_wmhg/ajob1 1 F 0 2 launch ends with non zero status: 127. Stop all computation
INFO: Idle: 106, Running: 0, Completed: 4 [ current time: 09h05 ]

then its stayed stuck.

Am i missing something? Thanks

Cheers,

Siewyan

--
You received this question notification because you are an answer
contact for MadGraph5_aMC@NLO.

Siew Yan HOH (siew-yan-hoh) said : #2

Hi Olivier,

thanks for the hint, there are two GF2 folder in /uscms_data/d3/shoh/private_production/running_from_tarball/tarballNLO/tmp/process/SubProcesses/P1_uxd_wmhg/ , each with log.txt and its reveal:

../madevent_mintMC: symbol lookup error: ../madevent_mintMC: undefined symbol: _ZN7fastjet13JetDefinitionC1ENS_12JetAlgorithmEdNS_19RecombinationSchemeENS_8StrategyEi
Error: Status code 127
+ Hostname:
cmslpc35.fnal.gov
+ Printing environment
SRT_G4LEVELGAMMADATA_SCRAMRTDEL=/cvmfs/cms.cern.ch/slc6_amd64_gcc481/external/geant4-G4PhotonEvaporation/3.0/data/PhotonEvaporation3.0

 more ENV PATH follow .....

I am not sure what does it mean since this is done internally during subprocess folder creation..

On the other hand if i only run in LO, the error message :

WARNING: Order of particle in the event did not agree with parent/child order. This might be problematic for some code.

still persist, but the generation of event ran smoothly.. Its look like the decay is not properly done...

Do you have any idea what is going on?

THanks!

Cheers,

Siewyan

So looks like that your issue is with fastjet.
I would suggest that you remove fastjet from the configurtion file (or remove it from the PATH).
Such that we will use fjcore instead. fjcore/fastjet are not used at LO, explaining why you do not face such issue at LO.

WARNING: Order of particle in the event did not agree with parent/child
order. This might be problematic for some code.

This is not a problem for MG5aMC/MadSpin. Some parser does not like such ordering issue and crash on such events (if you face that, you actually just need to re-order the particle within the lhe file)

Cheers,

Olivier

On 8 Jul 2019, at 22:28, Siew Yan HOH <<email address hidden><mailto:<email address hidden>>> wrote:

symbol lookup error:

Siew Yan HOH (siew-yan-hoh) said : #4

Hi Olivier,

Thanks for the answer on the NLO generation with fastjet env interference.. i will see to it to have it fixed.

Regarding the parent/child ordering warning from generation, would it be an issue if remain unordered and fed into pythia?

Also, i found that another syntex to generate wh , w->lv , h > w(lv) w(jj) diagram is to generate:

generate p p > w- > w- w- w+ / a z h [QCD]

and later decay all the w in madspin, but as a trade off i am getting a triboson decay from the very off-shell W- (s-channel). My followup question is:

1.) Which approach do you its accurate to simulate WH same sign process?

generate p p > w- > w- w- w+ / a z [QCD]
and later decay all w in Madspin

or

generate p p > w- h [QCD] @0
decay w and h appropriately?

2.) if the former is more accurate, is that a way to filter the triboson contribution (generate p p > w- > w- w- w+ / a z h [QCD] )?

Thanks you very much >.<

Cheers,

Siewyan

Siew Yan HOH (siew-yan-hoh) said : #5

TYPO: generate p p > w- > w- w- w+ / a z h [QCD]

after "Also, i found that another syntex to generate wh , w->lv , h > w(lv) w(jj) diagram is to generate:"

CORRECTION
** generate p p > w- > w- w- w+ / a z [QCD] ** (No h after slash)

For pythia, As far as I know no.

For the syntax, for me the two are COMPLETLY different process. One request a Onshell HIggs decaying into 4 lepton (with one off-shell W). While the second request THREE onshell W (and therefore a Off-shell Higgs when a HIggs propagator is present). So they produce different result for different configuration. You will need to use one or the other (or both) depending of your analysis.

Cheers,

Olivier

Siew Yan HOH (siew-yan-hoh) said : #7

Thanks for the answers.

For my analysis, I am looking for WH production, which, W- and H produced on-shell, we expect one of the W from Higgs is offshell,

based on the information from your side..., the correct syntex should be:

generate p p > w- h [QCD]

at madspin

set spinmode none
define l- = mu- e-
define vl~ = vm~ ve~
decay w- > l- vl~
decay h > l- vl~ w+ , w+ > j j

?

Thanks!

Siewyan

Siew Yan HOH (siew-yan-hoh) said : #8

Thanks Olivier Mattelaer, that solved my question.

Siew Yan HOH (siew-yan-hoh) said : #9

Hi Oliver,

I have adapted the above syntex on my generation, but at the end of pythia8 I have 0 cross section... Could you help me to understand why?...

Notably..

During Madspin generation,

CRITICAL: start gridpack! interface_madspin.py at line 732

Pop up for decaying particle , please look at full log here:
https://shoh.web.cern.ch/shoh/Topics/public/troubleshoot/Wminush012j_5f_NLO_FXFX_M125_WToLV.log

I have untar the gridpack and successfully generate the events (LHE),

The LHE file is here:

wget https://shoh.web.cern.ch/shoh/Topics/public/troubleshoot/cmsgrid_final.lhe

later I did feed in the FXFX hadronizer to perform hadronization on the LHE file. At the end its yield zero cross section... and the full log file is here:

https://shoh.web.cern.ch/shoh/Topics/public/troubleshoot/log

All 2000 times reported End of LHE event, i wonder does this has to do with the unordering parent and child warning seen at madspin?

Thanks and i am looking forward to hear from you.

Cheers,

Siewyan

Hi,

My guess is that your version of pythia8 is not recent enough to handle such type of event syntax.
I have never heard about such issue before and the lhe seems fine (I do not even spot issue with the decay ordering in that file).

You are using very old version of both MG5aMC and Pythia8. So It will be quite difficult for us to help you on this as long as you do not use the latest version of our software.

Cheers,

Olivier

Siew Yan HOH (siew-yan-hoh) said : #11

Hi Olivier,

Thanks for the answer... I guess I have to move to a newer version of MG5 and PY8..

Thanks for promptly reply.

Cheers,

Siewyan