Interfacing with madspin with a process using commas

Hi David,

I’m confuse about which process you are interested in:

> p p > j t~ x53 / w+ w- , x53 > j t~ t w+

and
> p p > x53 > j t~ t w+

Do not have the same final state
with the first syntax you have two anti-top in addition of one top, two j and a W
in the second you have only one anti-top and only one j.

if guess that you are interested in the second final state.
in that case, the solution is to do the following in MG:

generate p p > x53 j t~

and decay x53 in madspin with the line
decay x53 > t w+ , w+ > all all

If x53 is indeed a 4 body decay then MadSpin can not handle it, so we will need another solution (probably hack MadSpin to make it support the comma in this case)

Cheers,

Olivier

On 29 Jul 2015, at 08:57, David <email address hidden> wrote:

> New question #269772 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/269772
>
> I want to do a process:
> p p > j t~ x53 / w+ w- , x53 > j t~ t w+
>
> with definitions:
> define p = g u c d s u~ c~ d~ s~
> define j = g u c d s u~ c~ d~ s~
>
> But I need to inferface with madspin, which does not interpret commas. How do I rewrite this process in madgraph in a way that works with madspin?
>
> Things that that I have tried are:
>
> p p > j t~ x53 > j t~ t w+
> (Which does not seem to work in Madgraph)
>
> p p > x53 > j t~ t w+
> (Which working with madgraph and madspin, but produces diagrams we do not want)
>
> What is the correct way to write the original process to work with Madgraph and Madspin?
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi. Thank you for your answer.

With the suggestion, we modified to do our process like the following in Madgraph:
generate p p > x53 j t~ / h a z
add process p p > x53~ j t / h a z

and in Madspin:
decay x53 > t w+, (t > w+ b, w+ > all all), w+ > all all
decay t > w+ b, w+ > all all
decay x53~ > t~ w-, (t~ > w- b~, w- > all all), w- > all all
decay t~ > w- b~, w- > all all

There seems to be an error that comes up:

INFO: generate matrix element for decay only (1 - > N).
INFO: output standalone_msF /scratch/dzou/GridPackProduction/genproductions/bin/MadGraph5_aMCatNLO/tW_t_x53_madspin_narrow_RH_M700/tW_t_x53_madsp\
in_narrow_RH_M700_gridpack/work/process/madspingrid/decay_me
INFO: Done 84
INFO: Compiling code
INFO: detect independant decays
^[[1;31mCommand "launch" interrupted with error:
KeyError : -4
Please report this bug to developers
           More information is found in 'MS_debug'.
           Please attach this file to your report.^[[0m
MadSpin>
rm: cannot remove `/data/dzou/GridPackProduction/genproductions/bin/MadGraph5_aMCatNLO/tW_t_x53_madspin_narrow_RH_M700/tW_t_x53_madspin_narrow_RH_M700_gridpack/work/unweighted_even\
ts.lhe.gz': No such file or directory

The full log file can be found here:
https://dzou.web.cern.ch/dzou/mgms_x53_single/tW_t_x53_madspin_narrow_RH_M700.log

Hi,

Could you make the debug file available?
Such that I can have the basic information about this error.

Cheers,

Olivier

On 12 Aug 2015, at 11:46, David <email address hidden> wrote:

> Question #269772 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/269772
>
> Status: Answered => Open
>
> David is still having a problem:
> Hi. Thank you for your answer.
>
> With the suggestion, we modified to do our process like the following in Madgraph:
> generate p p > x53 j t~ / h a z
> add process p p > x53~ j t / h a z
>
> and in Madspin:
> decay x53 > t w+, (t > w+ b, w+ > all all), w+ > all all
> decay t > w+ b, w+ > all all
> decay x53~ > t~ w-, (t~ > w- b~, w- > all all), w- > all all
> decay t~ > w- b~, w- > all all
>
> There seems to be an error that comes up:
>
> INFO: generate matrix element for decay only (1 - > N).
> INFO: output standalone_msF /scratch/dzou/GridPackProduction/genproductions/bin/MadGraph5_aMCatNLO/tW_t_x53_madspin_narrow_RH_M700/tW_t_x53_madsp\
> in_narrow_RH_M700_gridpack/work/process/madspingrid/decay_me
> INFO: Done 84
> INFO: Compiling code
> INFO: detect independant decays
> ^[[1;31mCommand "launch" interrupted with error:
> KeyError : -4
> Please report this bug to developers
> More information is found in 'MS_debug'.
> Please attach this file to your report.^[[0m
> MadSpin>
> rm: cannot remove `/data/dzou/GridPackProduction/genproductions/bin/MadGraph5_aMCatNLO/tW_t_x53_madspin_narrow_RH_M700/tW_t_x53_madspin_narrow_RH_M700_gridpack/work/unweighted_even\
> ts.lhe.gz': No such file or directory
>
> The full log file can be found here:
> https://dzou.web.cern.ch/dzou/mgms_x53_single/tW_t_x53_madspin_narrow_RH_M700.log
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,

Sorry about that the debug file is here:
https://dzou.web.cern.ch/dzou/mgms_x53_single/MS_debug

Hi,

I see that this topic has been assigned to someone. Is there further input needed from me? Also, is there a estimate of what the problem might be and how long it might take to be solve -- I understand that these may not be questions that are easily answered.

Hi David,

I can have a look now.
Can you put your model and the bug report in some public space ?
I don't have a CERN account

Thanks,

Pierre

Hi Pierre,

The bug report is here:
http://ohm.bu.edu/~dzou/MG/MS_debug.txt

And copy of the STP_UFO_freeWidth model, which has the x53 is here:
http://ohm.bu.edu/~dzou/MG/STP_UFO_freeWidth.tar.gz

Please let me know if I additional or different information.

Thanks,
~Dave

HI David,

Thanks.

I have just tried your process, with a simplification though:

I replaced w+ > all all by w+ > mu+ vm

and w- > all all by w- > mu- vm~

just to try to reduce the running time.

On my laptop, it still takes a long time to decay the events

INFO: Event nb 1000 6m 10s

 but it seems to run smoothly.

Could you try the muonic channel on your side as well ? If it thus not work, can you
make sure that you are using the latest version of mg5 ?
(on my side I have version = 2.3.2, date = 2015-08-20)

Pierre

Hi, I am now using version 2.3.2 and tried to run but get Fortran runtime errors

With an eventual message:
"generate_events pilotrun" interrupted with error:
ValueError : need more than 5 values to unpack
Please report this bug on https://bugs.launchpad.net/madgraph5

The full logs are here:
http://ohm.bu.edu/~dzou/MG/Oct13/full_rh700.log
http://ohm.bu.edu/~dzou/MG/Oct13/tW_t_x53_madspin_narrow_RH_M700.log

The associated debug log is here:
http://ohm.bu.edu/~dzou/MG/Oct13/pilotrun_tag_1_debug.log

Hi,

Apologizes, a link I submitted from my previous post was broken, but I have re-uploaded the log and it should be up now.

I should also add, that these particular logs come from trying to run with w+ > all all (and similarly with w-) but I also tried running using only muonic channel as suggested earlier and ran into the same Fortran runtime errors.

Please let know if you have any ideas on what the problem is or what to try next. Or if any more information is needed.

Hi David, hi Olivier,

I have just had a look at the log files.
Even in the mad spin mode, it seems that the problem
is unrelated to mad spin itself.

In both cases there is an error in the madevent phase:

ERROR DETECTED
At line 338 of file unwgt.f
Fortran runtime error: Index '538976288' of dimension 1 of array 'store_event' above upper bound of 200000

I am not an expert for this part, but it looks like the number of requested events is too large.
What is the requested number in the run_card.dat ?

Olivier, what do you think ?

Pierre

Hi, since this is done in gridpack mode, the number of requested should be irrelevant.
I guess Rikkert can tell more about this.

Cheers,

Olivier

Dear David,

I just tried out your process with exactly the same run_card and param_card you used and I'm not able to reproduce your problem. I've been using the same version of the code as you, apart from the:

patching file MG5_aMC_v2_3_2_2/madgraph/various/cluster.py
patching file MG5_aMC_v2_3_2_2/MadSpin/decay.py
patching file MG5_aMC_v2_3_2_2/Template/LO/bin/internal/Gridpack/run.sh
patching file MG5_aMC_v2_3_2_2/Template/NLO/SubProcesses/MCmasses_PYTHIA8.inc
patching file MG5_aMC_v2_3_2_2/Template/NLO/SubProcesses/setscales.f
patching file MG5_aMC_v2_3_2_2/models/loop_sm/restrict_ckm_no_b_mass.dat
patching file MG5_aMC_v2_3_2_2/models/sm/restrict_ckm_lepton_masses.dat
patching file MG5_aMC_v2_3_2_2/models/sm/restrict_ckm_lepton_masses_no_b_mass.dat
patching file MG5_aMC_v2_3_2_2/models/sm/restrict_lepton_masses_no_b_mass.dat
patching file MG5_aMC_v2_3_2_2/models/sm/restrict_ckm_no_b_mass.dat

which I don't know what it does...

Could you try with the latest release (v2.3.3) to see if the problem persists?

Best regards,
Rikkert