MadSpin in gridpack?

Actually this is possibility is still in development.

I would suggest to wait for 2.1.1 since it brings some fix and should be finally working properly in gridpack mode as well.

The idea of the implementation is that in the madspin_card you can set the line
set ms_dir PATH

If that PATH is not define then nothing happens except that the run is performed in that directory and is not removed at the end of the run, and that a pkl file is written with some information.
If PATH exists then it reload that information (max_weight for each channe/branching ratio/…)

Cheers,

Olivier

On Mar 27, 2014, at 5:31 PM, Eric Conte <email address hidden> wrote:

> New question #246143 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/246143
>
> Dear experts,
>
> My question is very similar to one dated back from January 2013.
> It seems that MadSpin is not included in the gridpack tarball. Is it true?
>
> I would like to include manually the MadSpin folder into the tarball and to update the run.sh script in order to call MadSpin.
> Is there something wrong with this idea?
>
> Cheers,
> Eric
>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,

Is this implemented now?
It seems not to be in 2.1.2, but perhaps I'm just doing it wrong?

Cheers,

Josh.

Hi Josh,

Could you try with the 2.1.3 development branch? Some other people had some very tricky bug with 2.1.2. Which should be solve in 2.1.3 (not yet release)

Cheers,

Olivier

Hi Olivier,

I just tried and it doesn't seem to pick up my Cards/madspin_card.dat file because I see no reference to MadSpin running either in the gridpack creation or generation of events from the gridpack.

Do you have a specific set of instructions that you would expect to work?

Cheers,

Josh.

Hi all,

I just tried this again with v2.3.2 and it still doesn't seem to be possible?
Am I wrong?

Best,

Josh.

Hi Josh,

Yes and No.
The inclusion of MadSpin inside the gridpack is not automated.
The main reason are
1) that the gridpack generation does not have enough event generated in order to have reliable maximum weight.
2) that you need to ship the full python code within the gridpack

So in order to have the correct output, you need first to generate a decent number of events and then run MadSpin on those with the options
set ms_dir=PATH
(and probably ask for more points used in the evaluation of the maximum_weight to be 100% sure to not under-estimate it)

Then you can ship this directory and the python executables/library and just run MadSpin in standalone.
I know that CMS is doing it, but this is not done at our level.

Cheers,

Olivier