MG3.1.0 undershoots events for VBS ssWWjj LT and TL production
Hello,
I'm using the following script to produce a gridpack (using MG3.1.0 and running with LCG_99-
generate p p > w+{0} w+{T} j j QCD=0, w+ > l+ vl, w+ > l+ vl @0
add process p p > w-{0} w-{T} j j QCD=0, w- > l- vl~ @0
add process p p > w+{T} w+{0} j j QCD=0, w+ > l+ vl, w+ > l+ vl @0
add process p p > w-{T} w-{0} j j QCD=0, w- > l- vl~ @0
output PROC_ssWWjj_EW_LTTL
launch
set hard_survey 1
set nevents 0
set gridpack True
set use_syst False
However, when extracting the gridpack, and running
./run.sh 10000 randomSeed 1
For each job, the seed is randomSeed=$(( ${ClusterId} + ${ProcId} )) where the ProcId and ClusterId are respectively the last and 1-before-last items in the list below. (e.g. ClusterId=2353020 and ProcId=9 in the file LCG_99-
I get the follwing event count in the LHE produced files:
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
LCG_99-
As you can see we're very far from 10k events. I thought that setting hard_survey 1 was meant to help in such cases (cf https:/
Generation of {0}{0} and {T}{T} events seems to work fine. I haven't yet tested separating {0}{T} and {T}{0}, or the charges, nor using different @x process identifiers. These are on my to-do but I would be surprised if they helped.
Could you please let me know if there's something I can do to obtain more events per run ? Also, is it safe to nevertheless combine these events or am I biasing the distributions ?
I am happy to run further tests you might suggest if that helps.
Thanks a lot.
Best,
Karolos
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask Karolos Potamianos for more information if necessary.