KeyError : 'sbotmix' error when running gridpack

Hi,

Which version of MG5 did you use?

Cheers,

Olivier

On 23 Mar 2015, at 05:11, Javier Fernandez <email address hidden> wrote:

> New question #264042 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/264042
>
> Dear experts,
>
> I have aMCatNLO gridpack which is (apparently) succesfully created bt when running it crashes at Madspin step wity the following error:
>
> Moving events from events.lhe
> ************************************************************
> * *
> * W E L C O M E to M A D S P I N *
> * *
> ************************************************************
> MadSpin>INFO: process: p p > t1 t1~
> INFO: options:
> Set group_subprocesses to Auto
> Note that you need to regenerate all processes
> set loop optimized output to True
> INFO: detected model: mssm. Loading...
> INFO: reload from .py file
> INFO: load particles
> INFO: load vertices
> INFO: Restrict model mssm with file ../mgbasedir/models/mssm/restrict_default.dat .
> INFO: Run "set stdout_level DEBUG" before import for more information.
> INFO: Change particles name to pass to MG5 convention
> Defined multiparticle p = g u c d s u~ c~ d~ s~
> Defined multiparticle j = g u c d s u~ c~ d~ s~
> Defined multiparticle l+ = e+ mu+
> Defined multiparticle l- = e- mu-
> Defined multiparticle vl = ve vm vt
> Defined multiparticle vl~ = ve~ vm~ vt~
> Defined multiparticle all = g u c d s u~ c~ d~ s~ a ve vm vt e- mu- ve~ vm~ vt~ e+ mu+ go ul cl t1 ur cr t2 dl sl b1 dr sr b2 ul~ cl~ t1~ ur~ cr~ t2~ dl~ sl~ b1~ dr~ sr~ b2~ t b t~ b~ z w+ h1 h2 h3 h+ sve svm svt el- mul- ta1- er- mur- ta2- w- h- sve~ svm~ svt~ el+ mul+ ta1+ er+ mur+ ta2+ n1 n2 n3 n4 x1+ x2+ ta- x1- x2- ta+
> Set group_subprocesses to Auto
> Note that you need to regenerate all processes
> set loop optimized output to True
> Complex mass already desactivated.
> Defined multiparticle p = g u c d s u~ c~ d~ s~
> Defined multiparticle j = g u c d s u~ c~ d~ s~
> Defined multiparticle l+ = e+ mu+
> Defined multiparticle l- = e- mu-
> Defined multiparticle vl = ve vm vt
> Defined multiparticle vl~ = ve~ vm~ vt~
> Defined multiparticle p = g u d s c u~ d~ s~ c~ b b~
> Defined multiparticle j = g u d s c u~ d~ s~ c~ b b~
> Defined multiparticle q = g u d s c u~ d~ s~ c~ b b~
> Defined multiparticle s1 = ul ur dl dr sl sr cl cr ul~ ur~ dl~ dr~ sl~ sr~ cl~ cr~
> Defined multiparticle s2 = b1 b2 t1 t2 b1~ b2~ t1~ t2~
> Defined multiparticle s3 = b1 b2 t2 b1~ b2~ t2~
> Defined multiparticle sneu = n1 n2 n3 n4
> Defined multiparticle sch = x1+ x2+ x1- x2-
> Defined multiparticle sl+ = el+ er+ mul+ mur+
> Defined multiparticle svl = sve svm sve~ svm~
> Defined multiparticle sl- = el- er- mul- mur-
> Defined multiparticle l = e- mu- e+ mu+ ta- ta+
> Defined multiparticle vl = ve vm vt ve~ vm~ vt~
> Defined multiparticle all = g u d s c u~ d~ s~ c~ e- mu- ve vm vt e+ mu+ ve~ vm~ vt~ b b~ ta- ta+
> MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>Defined multiparticle ell+ = e+ mu+ ta+
> MadSpin>Defined multiparticle ell- = e- mu- ta-
> Command "launch" interrupted with error:
> KeyError : 'sbotmix'
> Please report this bug to developers
>
> More information is found in 'MS_debug'.
>
> Please attach this file to your report.
> MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>MadSpin>
>
> The MS_debug file says:
>
> import events.lhe.gz
> set seed 1000001
>
> set ms_dir ./madspingrid
>
> set Nevents_for_max_weigth 250
>
> set max_weight_ps_point 400
>
> set max_running_process 1
>
> define ell+ = e+ mu+ ta+
> define ell- = e- mu- ta-
>
> decay t1 > t n1, t > w+ b, w+ > ell+ vl
> decay t1~ > t~ n1, t~ > w- b~, w- > ell- vl~
>
>
> launch
> Traceback (most recent call last):
> File "/tmp/jfernan2/CMSSW_7_1_14/src/mgbasedir/madgraph/interface/extended_cmd
> .py", line 879, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/tmp/jfernan2/CMSSW_7_1_14/src/mgbasedir/madgraph/interface/extended_cmd
> .py", line 872, in onecmd_orig
> return func(arg, **opt)
> File "/tmp/jfernan2/CMSSW_7_1_14/src/mgbasedir/MadSpin/interface_madspin.py",
> line 423, in do_launch
> return self.run_from_pickle()
> File "/tmp/jfernan2/CMSSW_7_1_14/src/mgbasedir/MadSpin/interface_madspin.py",
> line 526, in run_from_pickle
> orig_block = generate_all.banner.param_card[name]
> KeyError: 'sbotmix'
> Value of current Options:
> BW_cut : 15.0
> onlyhelicity : False
> nb_sigma : 4.5
> max_running_process : 1
> max_weight_ps_point : 400
> Nevents_for_max_weigth : 250
> curr_dir : ./madspingrid
> ms_dir : ./madspingrid
> max_weight : -1
>
> Could you give any hing on how to debug this?
> Thanks in advance,
> Javi
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,

I´m using VERSION 2.2.2 2014-11-06

Thanks,
Javi

Hi Javi,

Thanks, I succeed to fix the problem which is specific to the mssm model.
(This model is always tricky).

I’m afraid that the fix will only work with version 2.3 of the code which is not yet public.
So I can not give you an easy fix to have this working.

Cheers,

Olivier

On 23 Mar 2015, at 16:26, Javier Fernandez <email address hidden> wrote:

> Question #264042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/264042
>
> Javier Fernandez posted a new comment:
> Hi Olivier,
>
> I´m using VERSION 2.2.2 2014-11-06
>
> Thanks,
> Javi
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,

couldn´t you make the 2.3 version available in a private way somehow?
Is there anything I can do to overcome the problem? I mean, full Madspin
decays instead of dileptonic ones would give the problem too?
If the answer is not, what is the timescale for this release to be public?

Thank you,
Javi

El 23/03/2015 a las 9:36, Olivier Mattelaer escribió:
> Your question #264042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/264042
>
> Olivier Mattelaer proposed the following answer:
> Hi Javi,
>
> Thanks, I succeed to fix the problem which is specific to the mssm model.
> (This model is always tricky).
>
> I’m afraid that the fix will only work with version 2.3 of the code which is not yet public.
> So I can not give you an easy fix to have this working.
>
> Cheers,
>
> Olivier
>
> On 23 Mar 2015, at 16:26, Javier Fernandez
> <email address hidden> wrote:
>
>> Question #264042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>
>> Javier Fernandez posted a new comment:
>> Hi Olivier,
>>
>> I´m using VERSION 2.2.2 2014-11-06
>>
>> Thanks,
>> Javi
>>
>> --
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.

--
+--------------------------------------------------------------+
  Javier Fernandez Menendez

  Grupo de Fisica de AAEE
  Universidad de Oviedo
  C/ Calvo Sotelo, s/n
  33005 Oviedo
  http://www.hep.uniovi.es

  Phone: +34 985106252
  mailto:<email address hidden>
+---------------------------------------------------------------+

Hi Javi,

What you can try is to comment the following line:

        for name, block in self.banner.param_card.items():
            if name.startswith('decay'):
                continue

            orig_block = generate_all.banner.param_card[name]
            if block != orig_block:
                raise Exception, """The directory %s is specific to a mass spectrum.
                Your event file is not compatible with this one. (Different param_card: %s different)
                orig block:
                %s
                new block:
                %s""" \
                % (self.options[‘ms_dir'], name, orig_block, block)

(around line 565 of MadSpin/interfqce_madspin.py)

Otherwise the public beta release of 2.3 should be imminent, and this version is going to stay in beta for at least a month (probably two) before being the recommended version.

Cheers,

Olivier

On 23 Mar 2015, at 20:36, Javier Fernandez <email address hidden> wrote:

> Question #264042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/264042
>
> Status: Answered => Open
>
> Javier Fernandez is still having a problem:
> Hi Olivier,
>
> couldn´t you make the 2.3 version available in a private way somehow?
> Is there anything I can do to overcome the problem? I mean, full Madspin
> decays instead of dileptonic ones would give the problem too?
> If the answer is not, what is the timescale for this release to be public?
>
> Thank you,
> Javi
>
> El 23/03/2015 a las 9:36, Olivier Mattelaer escribió:
>> Your question #264042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>
>> Olivier Mattelaer proposed the following answer:
>> Hi Javi,
>>
>> Thanks, I succeed to fix the problem which is specific to the mssm model.
>> (This model is always tricky).
>>
>> I’m afraid that the fix will only work with version 2.3 of the code which is not yet public.
>> So I can not give you an easy fix to have this working.
>>
>> Cheers,
>>
>> Olivier
>>
>> On 23 Mar 2015, at 16:26, Javier Fernandez
>> <email address hidden> wrote:
>>
>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>
>>> Javier Fernandez posted a new comment:
>>> Hi Olivier,
>>>
>>> I´m using VERSION 2.2.2 2014-11-06
>>>
>>> Thanks,
>>> Javi
>>>
>>> --
>>> You received this question notification because you are an answer
>>> contact for MadGraph5_aMC@NLO.
>
> --
> +--------------------------------------------------------------+
> Javier Fernandez Menendez
>
> Grupo de Fisica de AAEE
> Universidad de Oviedo
> C/ Calvo Sotelo, s/n
> 33005 Oviedo
> http://www.hep.uniovi.es
>
> Phone: +34 985106252
> mailto:<email address hidden>
> +---------------------------------------------------------------+
>
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,

commenting those lines, the gridpack works!!

Should I comment them at gridpack generation step too?

Thanks for the fast resolution!!

Javi

El 23/03/2015 a las 13:21, Olivier Mattelaer escribió:
> Your question #264042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/264042
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi Javi,
>
> What you can try is to comment the following line:
>
> for name, block in self.banner.param_card.items():
> if name.startswith('decay'):
> continue
>
> orig_block = generate_all.banner.param_card[name]
> if block != orig_block:
> raise Exception, """The directory %s is specific to a mass spectrum.
> Your event file is not compatible with this one. (Different param_card: %s different)
> orig block:
> %s
> new block:
> %s""" \
> % (self.options[‘ms_dir'], name, orig_block, block)
>
> (around line 565 of MadSpin/interfqce_madspin.py)
>
> Otherwise the public beta release of 2.3 should be imminent, and this
> version is going to stay in beta for at least a month (probably two)
> before being the recommended version.
>
> Cheers,
>
> Olivier
>
> On 23 Mar 2015, at 20:36, Javier Fernandez
> <email address hidden> wrote:
>
>> Question #264042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>
>> Status: Answered => Open
>>
>> Javier Fernandez is still having a problem:
>> Hi Olivier,
>>
>> couldn´t you make the 2.3 version available in a private way somehow?
>> Is there anything I can do to overcome the problem? I mean, full Madspin
>> decays instead of dileptonic ones would give the problem too?
>> If the answer is not, what is the timescale for this release to be public?
>>
>> Thank you,
>> Javi
>>
>> El 23/03/2015 a las 9:36, Olivier Mattelaer escribió:
>>> Your question #264042 on MadGraph5_aMC@NLO changed:
>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>
>>> Olivier Mattelaer proposed the following answer:
>>> Hi Javi,
>>>
>>> Thanks, I succeed to fix the problem which is specific to the mssm model.
>>> (This model is always tricky).
>>>
>>> I’m afraid that the fix will only work with version 2.3 of the code which is not yet public.
>>> So I can not give you an easy fix to have this working.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>> On 23 Mar 2015, at 16:26, Javier Fernandez
>>> <email address hidden> wrote:
>>>
>>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>
>>>> Javier Fernandez posted a new comment:
>>>> Hi Olivier,
>>>>
>>>> I´m using VERSION 2.2.2 2014-11-06
>>>>
>>>> Thanks,
>>>> Javi
>>>>
>>>> --
>>>> You received this question notification because you are an answer
>>>> contact for MadGraph5_aMC@NLO.
>> --
>> +--------------------------------------------------------------+
>> Javier Fernandez Menendez
>>
>> Grupo de Fisica de AAEE
>> Universidad de Oviedo
>> C/ Calvo Sotelo, s/n
>> 33005 Oviedo
>> http://www.hep.uniovi.es
>>
>> Phone: +34 985106252
>> mailto:<email address hidden>
>> +---------------------------------------------------------------+
>>
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.

--
+--------------------------------------------------------------+
  Javier Fernandez Menendez

  Grupo de Fisica de AAEE
  Universidad de Oviedo
  C/ Calvo Sotelo, s/n
  33005 Oviedo
  http://www.hep.uniovi.es

  Phone: +34 985106252
  mailto:<email address hidden>
+---------------------------------------------------------------+

Hi,

> Should I comment them at gridpack generation step too?

Not really needed.

Just note than without those line, we do not check anymore that the card used to generate the events and the one used to generate the MadSpin gridpack are
identical. So you need to check this point yourself.

Cheers,

Olivier

On 23 Mar 2015, at 21:36, Javier Fernandez <email address hidden> wrote:

> Question #264042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/264042
>
> Status: Answered => Open
>
> Javier Fernandez is still having a problem:
> Hi Olivier,
>
> commenting those lines, the gridpack works!!
>
> Should I comment them at gridpack generation step too?
>
> Thanks for the fast resolution!!
>
> Javi
>
> El 23/03/2015 a las 13:21, Olivier Mattelaer escribió:
>> Your question #264042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>
>> Status: Open => Answered
>>
>> Olivier Mattelaer proposed the following answer:
>> Hi Javi,
>>
>> What you can try is to comment the following line:
>>
>> for name, block in self.banner.param_card.items():
>> if name.startswith('decay'):
>> continue
>>
>> orig_block = generate_all.banner.param_card[name]
>> if block != orig_block:
>> raise Exception, """The directory %s is specific to a mass spectrum.
>> Your event file is not compatible with this one. (Different param_card: %s different)
>> orig block:
>> %s
>> new block:
>> %s""" \
>> % (self.options[‘ms_dir'], name, orig_block, block)
>>
>> (around line 565 of MadSpin/interfqce_madspin.py)
>>
>> Otherwise the public beta release of 2.3 should be imminent, and this
>> version is going to stay in beta for at least a month (probably two)
>> before being the recommended version.
>>
>> Cheers,
>>
>> Olivier
>>
>> On 23 Mar 2015, at 20:36, Javier Fernandez
>> <email address hidden> wrote:
>>
>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>
>>> Status: Answered => Open
>>>
>>> Javier Fernandez is still having a problem:
>>> Hi Olivier,
>>>
>>> couldn´t you make the 2.3 version available in a private way somehow?
>>> Is there anything I can do to overcome the problem? I mean, full Madspin
>>> decays instead of dileptonic ones would give the problem too?
>>> If the answer is not, what is the timescale for this release to be public?
>>>
>>> Thank you,
>>> Javi
>>>
>>> El 23/03/2015 a las 9:36, Olivier Mattelaer escribió:
>>>> Your question #264042 on MadGraph5_aMC@NLO changed:
>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>
>>>> Olivier Mattelaer proposed the following answer:
>>>> Hi Javi,
>>>>
>>>> Thanks, I succeed to fix the problem which is specific to the mssm model.
>>>> (This model is always tricky).
>>>>
>>>> I’m afraid that the fix will only work with version 2.3 of the code which is not yet public.
>>>> So I can not give you an easy fix to have this working.
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> On 23 Mar 2015, at 16:26, Javier Fernandez
>>>> <email address hidden> wrote:
>>>>
>>>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>
>>>>> Javier Fernandez posted a new comment:
>>>>> Hi Olivier,
>>>>>
>>>>> I´m using VERSION 2.2.2 2014-11-06
>>>>>
>>>>> Thanks,
>>>>> Javi
>>>>>
>>>>> --
>>>>> You received this question notification because you are an answer
>>>>> contact for MadGraph5_aMC@NLO.
>>> --
>>> +--------------------------------------------------------------+
>>> Javier Fernandez Menendez
>>>
>>> Grupo de Fisica de AAEE
>>> Universidad de Oviedo
>>> C/ Calvo Sotelo, s/n
>>> 33005 Oviedo
>>> http://www.hep.uniovi.es
>>>
>>> Phone: +34 985106252
>>> mailto:<email address hidden>
>>> +---------------------------------------------------------------+
>>>
>>> You received this question notification because you are an answer
>>> contact for MadGraph5_aMC@NLO.
>
> --
> +--------------------------------------------------------------+
> Javier Fernandez Menendez
>
> Grupo de Fisica de AAEE
> Universidad de Oviedo
> C/ Calvo Sotelo, s/n
> 33005 Oviedo
> http://www.hep.uniovi.es
>
> Phone: +34 985106252
> mailto:<email address hidden>
> +---------------------------------------------------------------+
>
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,

I understand, however, the case is that they are identical. I mean, the
gridpack saves the input cards and then they are used to generate n
additional events. It is in that moment when the crash is being produced.

So, somehow I´m puzzled, or what datacard do you actually mean? The
madspin one, the proc card, the run card, the customize one? Or the
param card? Those four are supposed to be identical at gridpack creation
and running time so, if you feel they are not, there´s bug from my side
too, but I have not seen it so far. The param card I agree it is being
modified since I do not know how to exactly plug it in MG apart from
copying it as the default one.

Thanks,
Javi

El 23/03/2015 a las 13:51, Olivier Mattelaer escribió:
> Your question #264042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/264042
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi,
>
>> Should I comment them at gridpack generation step too?
> Not really needed.
>
> Just note than without those line, we do not check anymore that the card used to generate the events and the one used to generate the MadSpin gridpack are
> identical. So you need to check this point yourself.
>
> Cheers,
>
> Olivier
>
>
> On 23 Mar 2015, at 21:36, Javier Fernandez
> <email address hidden> wrote:
>
>> Question #264042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>
>> Status: Answered => Open
>>
>> Javier Fernandez is still having a problem:
>> Hi Olivier,
>>
>> commenting those lines, the gridpack works!!
>>
>> Should I comment them at gridpack generation step too?
>>
>> Thanks for the fast resolution!!
>>
>> Javi
>>
>> El 23/03/2015 a las 13:21, Olivier Mattelaer escribió:
>>> Your question #264042 on MadGraph5_aMC@NLO changed:
>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>
>>> Status: Open => Answered
>>>
>>> Olivier Mattelaer proposed the following answer:
>>> Hi Javi,
>>>
>>> What you can try is to comment the following line:
>>>
>>> for name, block in self.banner.param_card.items():
>>> if name.startswith('decay'):
>>> continue
>>>
>>> orig_block = generate_all.banner.param_card[name]
>>> if block != orig_block:
>>> raise Exception, """The directory %s is specific to a mass spectrum.
>>> Your event file is not compatible with this one. (Different param_card: %s different)
>>> orig block:
>>> %s
>>> new block:
>>> %s""" \
>>> % (self.options[‘ms_dir'], name, orig_block, block)
>>>
>>> (around line 565 of MadSpin/interfqce_madspin.py)
>>>
>>> Otherwise the public beta release of 2.3 should be imminent, and this
>>> version is going to stay in beta for at least a month (probably two)
>>> before being the recommended version.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>> On 23 Mar 2015, at 20:36, Javier Fernandez
>>> <email address hidden> wrote:
>>>
>>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>
>>>> Status: Answered => Open
>>>>
>>>> Javier Fernandez is still having a problem:
>>>> Hi Olivier,
>>>>
>>>> couldn´t you make the 2.3 version available in a private way somehow?
>>>> Is there anything I can do to overcome the problem? I mean, full Madspin
>>>> decays instead of dileptonic ones would give the problem too?
>>>> If the answer is not, what is the timescale for this release to be public?
>>>>
>>>> Thank you,
>>>> Javi
>>>>
>>>> El 23/03/2015 a las 9:36, Olivier Mattelaer escribió:
>>>>> Your question #264042 on MadGraph5_aMC@NLO changed:
>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>
>>>>> Olivier Mattelaer proposed the following answer:
>>>>> Hi Javi,
>>>>>
>>>>> Thanks, I succeed to fix the problem which is specific to the mssm model.
>>>>> (This model is always tricky).
>>>>>
>>>>> I’m afraid that the fix will only work with version 2.3 of the code which is not yet public.
>>>>> So I can not give you an easy fix to have this working.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Olivier
>>>>>
>>>>> On 23 Mar 2015, at 16:26, Javier Fernandez
>>>>> <email address hidden> wrote:
>>>>>
>>>>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>>
>>>>>> Javier Fernandez posted a new comment:
>>>>>> Hi Olivier,
>>>>>>
>>>>>> I´m using VERSION 2.2.2 2014-11-06
>>>>>>
>>>>>> Thanks,
>>>>>> Javi
>>>>>>
>>>>>> --
>>>>>> You received this question notification because you are an answer
>>>>>> contact for MadGraph5_aMC@NLO.
>>>> --
>>>> +--------------------------------------------------------------+
>>>> Javier Fernandez Menendez
>>>>
>>>> Grupo de Fisica de AAEE
>>>> Universidad de Oviedo
>>>> C/ Calvo Sotelo, s/n
>>>> 33005 Oviedo
>>>> http://www.hep.uniovi.es
>>>>
>>>> Phone: +34 985106252
>>>> mailto:<email address hidden>
>>>> +---------------------------------------------------------------+
>>>>
>>>> You received this question notification because you are an answer
>>>> contact for MadGraph5_aMC@NLO.
>> --
>> +--------------------------------------------------------------+
>> Javier Fernandez Menendez
>>
>> Grupo de Fisica de AAEE
>> Universidad de Oviedo
>> C/ Calvo Sotelo, s/n
>> 33005 Oviedo
>> http://www.hep.uniovi.es
>>
>> Phone: +34 985106252
>> mailto:<email address hidden>
>> +---------------------------------------------------------------+
>>
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.

--
+--------------------------------------------------------------+
  Javier Fernandez Menendez

  Grupo de Fisica de AAEE
  Universidad de Oviedo
  C/ Calvo Sotelo, s/n
  33005 Oviedo
  http://www.hep.uniovi.es

  Phone: +34 985106252
  mailto:<email address hidden>
+---------------------------------------------------------------+

Hi Javi,

> I understand, however, the case is that they are identical. I mean, the
> gridpack saves the input cards and then they are used to generate n
> additional events. It is in that moment when the crash is being produced.

The crash was occurring when the code checks that the param_card used to generate the events to decay
is identical to the one used to generate the gridpack. I clearly identified (and fixed in 2.3) situation where the param_card
where wrongly identified as not identical. (Which is linked to some mssm trick).

> Those four are supposed to be identical at gridpack creation
> and running time so, if you feel they are not, there´s bug from my side
> too, but I have not seen it so far.

At this stage, I do not think that you have modified any of those card in a wrong way.
So everything is fine on your side.
I’m just stressing that you comment the line which are there to prevent a potential mistake on your side.

Cheers,

Olivier

On 23 Mar 2015, at 22:01, Javier Fernandez <email address hidden> wrote:

> Question #264042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/264042
>
> Status: Answered => Open
>
> Javier Fernandez is still having a problem:
> Hi Olivier,
>
> I understand, however, the case is that they are identical. I mean, the
> gridpack saves the input cards and then they are used to generate n
> additional events. It is in that moment when the crash is being produced.
>
> So, somehow I´m puzzled, or what datacard do you actually mean? The
> madspin one, the proc card, the run card, the customize one? Or the
> param card? Those four are supposed to be identical at gridpack creation
> and running time so, if you feel they are not, there´s bug from my side
> too, but I have not seen it so far. The param card I agree it is being
> modified since I do not know how to exactly plug it in MG apart from
> copying it as the default one.
>
> Thanks,
> Javi
>
> El 23/03/2015 a las 13:51, Olivier Mattelaer escribió:
>> Your question #264042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>
>> Status: Open => Answered
>>
>> Olivier Mattelaer proposed the following answer:
>> Hi,
>>
>>> Should I comment them at gridpack generation step too?
>> Not really needed.
>>
>> Just note than without those line, we do not check anymore that the card used to generate the events and the one used to generate the MadSpin gridpack are
>> identical. So you need to check this point yourself.
>>
>> Cheers,
>>
>> Olivier
>>
>>
>> On 23 Mar 2015, at 21:36, Javier Fernandez
>> <email address hidden> wrote:
>>
>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>
>>> Status: Answered => Open
>>>
>>> Javier Fernandez is still having a problem:
>>> Hi Olivier,
>>>
>>> commenting those lines, the gridpack works!!
>>>
>>> Should I comment them at gridpack generation step too?
>>>
>>> Thanks for the fast resolution!!
>>>
>>> Javi
>>>
>>> El 23/03/2015 a las 13:21, Olivier Mattelaer escribió:
>>>> Your question #264042 on MadGraph5_aMC@NLO changed:
>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>
>>>> Status: Open => Answered
>>>>
>>>> Olivier Mattelaer proposed the following answer:
>>>> Hi Javi,
>>>>
>>>> What you can try is to comment the following line:
>>>>
>>>> for name, block in self.banner.param_card.items():
>>>> if name.startswith('decay'):
>>>> continue
>>>>
>>>> orig_block = generate_all.banner.param_card[name]
>>>> if block != orig_block:
>>>> raise Exception, """The directory %s is specific to a mass spectrum.
>>>> Your event file is not compatible with this one. (Different param_card: %s different)
>>>> orig block:
>>>> %s
>>>> new block:
>>>> %s""" \
>>>> % (self.options[‘ms_dir'], name, orig_block, block)
>>>>
>>>> (around line 565 of MadSpin/interfqce_madspin.py)
>>>>
>>>> Otherwise the public beta release of 2.3 should be imminent, and this
>>>> version is going to stay in beta for at least a month (probably two)
>>>> before being the recommended version.
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> On 23 Mar 2015, at 20:36, Javier Fernandez
>>>> <email address hidden> wrote:
>>>>
>>>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>
>>>>> Status: Answered => Open
>>>>>
>>>>> Javier Fernandez is still having a problem:
>>>>> Hi Olivier,
>>>>>
>>>>> couldn´t you make the 2.3 version available in a private way somehow?
>>>>> Is there anything I can do to overcome the problem? I mean, full Madspin
>>>>> decays instead of dileptonic ones would give the problem too?
>>>>> If the answer is not, what is the timescale for this release to be public?
>>>>>
>>>>> Thank you,
>>>>> Javi
>>>>>
>>>>> El 23/03/2015 a las 9:36, Olivier Mattelaer escribió:
>>>>>> Your question #264042 on MadGraph5_aMC@NLO changed:
>>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>>
>>>>>> Olivier Mattelaer proposed the following answer:
>>>>>> Hi Javi,
>>>>>>
>>>>>> Thanks, I succeed to fix the problem which is specific to the mssm model.
>>>>>> (This model is always tricky).
>>>>>>
>>>>>> I’m afraid that the fix will only work with version 2.3 of the code which is not yet public.
>>>>>> So I can not give you an easy fix to have this working.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Olivier
>>>>>>
>>>>>> On 23 Mar 2015, at 16:26, Javier Fernandez
>>>>>> <email address hidden> wrote:
>>>>>>
>>>>>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>>>
>>>>>>> Javier Fernandez posted a new comment:
>>>>>>> Hi Olivier,
>>>>>>>
>>>>>>> I´m using VERSION 2.2.2 2014-11-06
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Javi
>>>>>>>
>>>>>>> --
>>>>>>> You received this question notification because you are an answer
>>>>>>> contact for MadGraph5_aMC@NLO.
>>>>> --
>>>>> +--------------------------------------------------------------+
>>>>> Javier Fernandez Menendez
>>>>>
>>>>> Grupo de Fisica de AAEE
>>>>> Universidad de Oviedo
>>>>> C/ Calvo Sotelo, s/n
>>>>> 33005 Oviedo
>>>>> http://www.hep.uniovi.es
>>>>>
>>>>> Phone: +34 985106252
>>>>> mailto:<email address hidden>
>>>>> +---------------------------------------------------------------+
>>>>>
>>>>> You received this question notification because you are an answer
>>>>> contact for MadGraph5_aMC@NLO.
>>> --
>>> +--------------------------------------------------------------+
>>> Javier Fernandez Menendez
>>>
>>> Grupo de Fisica de AAEE
>>> Universidad de Oviedo
>>> C/ Calvo Sotelo, s/n
>>> 33005 Oviedo
>>> http://www.hep.uniovi.es
>>>
>>> Phone: +34 985106252
>>> mailto:<email address hidden>
>>> +---------------------------------------------------------------+
>>>
>>> You received this question notification because you are an answer
>>> contact for MadGraph5_aMC@NLO.
>
> --
> +--------------------------------------------------------------+
> Javier Fernandez Menendez
>
> Grupo de Fisica de AAEE
> Universidad de Oviedo
> C/ Calvo Sotelo, s/n
> 33005 Oviedo
> http://www.hep.uniovi.es
>
> Phone: +34 985106252
> mailto:<email address hidden>
> +---------------------------------------------------------------+
>
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,

thanks for the explanation, it is clear now.

I related question (it may be part of problem ?) to this same process
which led us to the bug you have found, if I may abuse from your time
(otherwise tell me and I will open another thread): I´m trying to make
Madspin to decay stops up to leptons + neutrino, i.e t1 -> t n1 -> w b
n1 -> l neu b n1

However, Madspin seems to ignore the last step of the decay, I mean it
decays up to w b n1. I´m trying to something like:

define ell+ = e+ mu+ ta+
define ell- = e- mu- ta-
decay t1 > t n1, t > w+ b, w+ > ell+ vl
decay t1~ > t~ n1, t~ > w- b~, w- > ell- vl~
decay t > w+ b
decay t~ > w- b~
decay w+ > ell+ vl
decay w- > ell- vl~

Is Madspin able to handle the full chain? If so, how should I set it?

Thanks in advance,
Javi

El 23/03/2015 a las 23:07, Olivier Mattelaer escribió:
> Your question #264042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/264042
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi Javi,
>
>> I understand, however, the case is that they are identical. I mean, the
>> gridpack saves the input cards and then they are used to generate n
>> additional events. It is in that moment when the crash is being produced.
>
> The crash was occurring when the code checks that the param_card used to generate the events to decay
> is identical to the one used to generate the gridpack. I clearly identified (and fixed in 2.3) situation where the param_card
> where wrongly identified as not identical. (Which is linked to some mssm trick).
>
>
>> Those four are supposed to be identical at gridpack creation
>> and running time so, if you feel they are not, there´s bug from my side
>> too, but I have not seen it so far.
>
> At this stage, I do not think that you have modified any of those card in a wrong way.
> So everything is fine on your side.
> I’m just stressing that you comment the line which are there to prevent a potential mistake on your side.
>
> Cheers,
>
> Olivier
>
>
> On 23 Mar 2015, at 22:01, Javier Fernandez
> <email address hidden> wrote:
>
>> Question #264042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>
>> Status: Answered => Open
>>
>> Javier Fernandez is still having a problem:
>> Hi Olivier,
>>
>> I understand, however, the case is that they are identical. I mean, the
>> gridpack saves the input cards and then they are used to generate n
>> additional events. It is in that moment when the crash is being produced.
>>
>> So, somehow I´m puzzled, or what datacard do you actually mean? The
>> madspin one, the proc card, the run card, the customize one? Or the
>> param card? Those four are supposed to be identical at gridpack creation
>> and running time so, if you feel they are not, there´s bug from my side
>> too, but I have not seen it so far. The param card I agree it is being
>> modified since I do not know how to exactly plug it in MG apart from
>> copying it as the default one.
>>
>> Thanks,
>> Javi
>>
>> El 23/03/2015 a las 13:51, Olivier Mattelaer escribió:
>>> Your question #264042 on MadGraph5_aMC@NLO changed:
>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>
>>> Status: Open => Answered
>>>
>>> Olivier Mattelaer proposed the following answer:
>>> Hi,
>>>
>>>> Should I comment them at gridpack generation step too?
>>> Not really needed.
>>>
>>> Just note than without those line, we do not check anymore that the card used to generate the events and the one used to generate the MadSpin gridpack are
>>> identical. So you need to check this point yourself.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>>
>>> On 23 Mar 2015, at 21:36, Javier Fernandez
>>> <email address hidden> wrote:
>>>
>>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>
>>>> Status: Answered => Open
>>>>
>>>> Javier Fernandez is still having a problem:
>>>> Hi Olivier,
>>>>
>>>> commenting those lines, the gridpack works!!
>>>>
>>>> Should I comment them at gridpack generation step too?
>>>>
>>>> Thanks for the fast resolution!!
>>>>
>>>> Javi
>>>>
>>>> El 23/03/2015 a las 13:21, Olivier Mattelaer escribió:
>>>>> Your question #264042 on MadGraph5_aMC@NLO changed:
>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>
>>>>> Status: Open => Answered
>>>>>
>>>>> Olivier Mattelaer proposed the following answer:
>>>>> Hi Javi,
>>>>>
>>>>> What you can try is to comment the following line:
>>>>>
>>>>> for name, block in self.banner.param_card.items():
>>>>> if name.startswith('decay'):
>>>>> continue
>>>>>
>>>>> orig_block = generate_all.banner.param_card[name]
>>>>> if block != orig_block:
>>>>> raise Exception, """The directory %s is specific to a mass spectrum.
>>>>> Your event file is not compatible with this one. (Different param_card: %s different)
>>>>> orig block:
>>>>> %s
>>>>> new block:
>>>>> %s""" \
>>>>> % (self.options[‘ms_dir'], name, orig_block, block)
>>>>>
>>>>> (around line 565 of MadSpin/interfqce_madspin.py)
>>>>>
>>>>> Otherwise the public beta release of 2.3 should be imminent, and this
>>>>> version is going to stay in beta for at least a month (probably two)
>>>>> before being the recommended version.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Olivier
>>>>>
>>>>> On 23 Mar 2015, at 20:36, Javier Fernandez
>>>>> <email address hidden> wrote:
>>>>>
>>>>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>>
>>>>>> Status: Answered => Open
>>>>>>
>>>>>> Javier Fernandez is still having a problem:
>>>>>> Hi Olivier,
>>>>>>
>>>>>> couldn´t you make the 2.3 version available in a private way somehow?
>>>>>> Is there anything I can do to overcome the problem? I mean, full Madspin
>>>>>> decays instead of dileptonic ones would give the problem too?
>>>>>> If the answer is not, what is the timescale for this release to be public?
>>>>>>
>>>>>> Thank you,
>>>>>> Javi
>>>>>>
>>>>>> El 23/03/2015 a las 9:36, Olivier Mattelaer escribió:
>>>>>>> Your question #264042 on MadGraph5_aMC@NLO changed:
>>>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>>>
>>>>>>> Olivier Mattelaer proposed the following answer:
>>>>>>> Hi Javi,
>>>>>>>
>>>>>>> Thanks, I succeed to fix the problem which is specific to the mssm model.
>>>>>>> (This model is always tricky).
>>>>>>>
>>>>>>> I’m afraid that the fix will only work with version 2.3 of the code which is not yet public.
>>>>>>> So I can not give you an easy fix to have this working.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Olivier
>>>>>>>
>>>>>>> On 23 Mar 2015, at 16:26, Javier Fernandez
>>>>>>> <email address hidden> wrote:
>>>>>>>
>>>>>>>> Question #264042 on MadGraph5_aMC@NLO changed:
>>>>>>>> https://answers.launchpad.net/mg5amcnlo/+question/264042
>>>>>>>>
>>>>>>>> Javier Fernandez posted a new comment:
>>>>>>>> Hi Olivier,
>>>>>>>>
>>>>>>>> I´m using VERSION 2.2.2 2014-11-06
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Javi
>>>>>>>>
>>>>>>>> --
>>>>>>>> You received this question notification because you are an answer
>>>>>>>> contact for MadGraph5_aMC@NLO.
>>>>>> --
>>>>>> +--------------------------------------------------------------+
>>>>>> Javier Fernandez Menendez
>>>>>>
>>>>>> Grupo de Fisica de AAEE
>>>>>> Universidad de Oviedo
>>>>>> C/ Calvo Sotelo, s/n
>>>>>> 33005 Oviedo
>>>>>> http://www.hep.uniovi.es
>>>>>>
>>>>>> Phone: +34 985106252
>>>>>> mailto:<email address hidden>
>>>>>> +---------------------------------------------------------------+
>>>>>>
>>>>>> You received this question notification because you are an answer
>>>>>> contact for MadGraph5_aMC@NLO.
>>>> --
>>>> +--------------------------------------------------------------+
>>>> Javier Fernandez Menendez
>>>>
>>>> Grupo de Fisica de AAEE
>>>> Universidad de Oviedo
>>>> C/ Calvo Sotelo, s/n
>>>> 33005 Oviedo
>>>> http://www.hep.uniovi.es
>>>>
>>>> Phone: +34 985106252
>>>> mailto:<email address hidden>
>>>> +---------------------------------------------------------------+
>>>>
>>>> You received this question notification because you are an answer
>>>> contact for MadGraph5_aMC@NLO.
>>
>> --
>> +--------------------------------------------------------------+
>> Javier Fernandez Menendez
>>
>> Grupo de Fisica de AAEE
>> Universidad de Oviedo
>> C/ Calvo Sotelo, s/n
>> 33005 Oviedo
>> http://www.hep.uniovi.es
>>
>> Phone: +34 985106252
>> mailto:<email address hidden>
>> +---------------------------------------------------------------+
>>
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.
>

--
-
+--------------------------------------------------------------+
  Javier Fernandez Menendez

  Grupo de Fisica de AAEE
  Universidad de Oviedo
  C/ Calvo Sotelo, s/n
  33005 Oviedo
  http://www.hep.uniovi.es

  Phone: +34 985106252
  mailto:<email address hidden>
+---------------------------------------------------------------+

Thanks Olivier Mattelaer, that solved my question.