SUSY parameter scan

Hi Bryan,

First, let me check if I understand what you want do
1) you generate 900 spectrum via a functionallity of FR
2) you compute the width via MG for those 900 spectrum creating 900 "new" param_card
3) you use those 900 param_card to generate a process (that you don't specify here)

And if I understand correctly your problem, all your "new" param_card always have the same value for the width.
So are you sure that you are not simply use the "old" param_card?

Otherwise, to simplify your framework, you can do the following:
1) you generate 900 spectrum via a functionallity of FR
2) edit all your param_card and replace the width by "Auto"
3) you use those 900 param_card to generate a process (that you don't specify here)

One way to run a sequence of 4 of such run is the following
./bin/madevent < command_file
where command_file has the following lines:
launch
../PARAMDIR/param_card_1.dat
set decay 1000024 Auto
set decay 1000006 Auto
launch
../PARAMDIR/param_card_2.dat
set decay 1000024 Auto
set decay 1000006 Auto
launch
../PARAMDIR/param_card_3.dat
set decay 1000024 Auto
set decay 1000006 Auto
launch
../PARAMDIR/param_card_4.dat
set decay 1000024 Auto
set decay 1000006 Auto

Cheers,

Olivier

Thanks for your reply Olivier,

So maybe my question is more about how madgraph is working. The events I am
trying to check right now are just the widths of the stops, the second
neutralino and the first and second chargino. So in madgraph I type

import model SUSYTriplet_M1M2800_UFO

> generate t1 > all all
> add process n2 > all all
> add process x1+ > all all
> add process x2+ > all all
> launch
> Triplet/Params/parm_card_50_50_M1_800_M2_800.dat
> param_card.dat (this just answers the question as to what kind of card I
> just gave it)
> 0 (to do the calculation)
> launch
> Triplet/Params/parm_card_50_100_M1_800_M2_800.dat
> param_card.dat (this just answers the question as to what kind of card I
> just gave it)
> 0 (to do the calculation)

etc

I thought that this would then generate new param_card.dat for each "event"
by calculating the widths. However, all of the calculated widths come to
the same, which cannot be true. I have tried the set width 1000006 Auto
(and the others) and I get an error

   if key in self.param_card[args[start]].param_dict:
KeyError: 'decay'

I am using the latest FeynRules (1.7.201). Maybe FR isn't generating the
decay info? In the UFO I see a decays.py but the log says decay.py not
written.

Thanks again for your help.

On Thu, Aug 15, 2013 at 4:56 PM, Olivier Mattelaer <
<email address hidden>> wrote:

> Your question #234102 on MadGraph5 changed:
> https://answers.launchpad.net/madgraph5/+question/234102
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi Bryan,
>
> First, let me check if I understand what you want do
> 1) you generate 900 spectrum via a functionallity of FR
> 2) you compute the width via MG for those 900 spectrum creating 900 "new"
> param_card
> 3) you use those 900 param_card to generate a process (that you don't
> specify here)
>
> And if I understand correctly your problem, all your "new" param_card
> always have the same value for the width.
> So are you sure that you are not simply use the "old" param_card?
>
> Otherwise, to simplify your framework, you can do the following:
> 1) you generate 900 spectrum via a functionallity of FR
> 2) edit all your param_card and replace the width by "Auto"
> 3) you use those 900 param_card to generate a process (that you don't
> specify here)
>
> One way to run a sequence of 4 of such run is the following
> ./bin/madevent < command_file
> where command_file has the following lines:
> launch
> ../PARAMDIR/param_card_1.dat
> set decay 1000024 Auto
> set decay 1000006 Auto
> launch
> ../PARAMDIR/param_card_2.dat
> set decay 1000024 Auto
> set decay 1000006 Auto
> launch
> ../PARAMDIR/param_card_3.dat
> set decay 1000024 Auto
> set decay 1000006 Auto
> launch
> ../PARAMDIR/param_card_4.dat
> set decay 1000024 Auto
> set decay 1000006 Auto
>
> Cheers,
>
> Olivier
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.launchpad.net/madgraph5/+question/234102/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/madgraph5/+question/234102
>
> You received this question notification because you asked the question.
>

--
<email address hidden>
(715) 459-6643
"Lord make me an instrument of your peace.
Where there is hatred, let me sow your love" ~ St. Francis

Hi Bryan,

Did you remove all the decay information from your param_card?
I suspect that you did, since in principle, MG should have detect automatically that the file that you provide to him is a param_card.
Your KeyError seems also related to an incorrect format for you param_card.

I was thinking that I was making the computation to crash if the param_card was not complete/wrong format, looks like I didn't.
Did you look at one computation log to see if the change in your param_card are indeed taken into account in the computation.
The spectrum should be written at the begin of the following file:
/SubProcesses/P0_XXXXXXXXXX/G3/log.txt

If you don't see your modification, this means that your param_card is not read correctly and the default value are then used.
Some warning should appear on the screen on this case, but looks like this function fails to be called. (I'll fix that)
If you don't understand what the problem is with your param_card, please send it to me via email (with your model)

Cheers,

Olivier