Using MadSpin in Gridpack creation

Asked by Zachary Marshall

Dear authors,

I'm sure we've discussed this before, but I can't find the most recent resolution. When creating a gridpack in a setup that includes a MadSpin card, we hit an error:

Command "generate_events run_01" interrupted with error:
InvalidCmd : No events file corresponding to run_01 run.

The run card has a number of events specified:

  6000 = nevents ! Number of unweighted events requested

But the log looks like this:

Generating gridpack with run name run_01
survey run_01 --accuracy=0.01 --points=2000 --iterations=8 --gridpack=.true.
INFO: compile directory
INFO: Using LHAPDF v6.5.3 interface for PDFs
compile Source Directory
Using random number seed offset = 123459
INFO: Running Survey
Creating Jobs
Working on SubProcesses
INFO: Compiling for process 1/2.
INFO: P1_gg_ttxttx
INFO: Compiling for process 2/2.
INFO: P1_qq_ttxttx
INFO: P1_gg_ttxttx
INFO: P1_qq_ttxttx
INFO: Idle: 1, Running: 2, Completed: 1 [ current time: 15h13 ]
INFO: Idle: 0, Running: 2, Completed: 2 [ current time: 15h13 ]
INFO: Idle: 0, Running: 0, Completed: 4 [ 1.5s ]
sum of cpu time of last step: 13 seconds
  === Results Summary for run: run_01 tag: tag_1 ===

     Cross-section : 1.029 +- 0.003933 pb
     Nb of events : 0

and indeed no events are generated. My recollection is that the 'solution' here is to move aside the MadSpin card during GridPack generation, and then to only apply it (separately) after event generation from the gridpack; is that right?

Thanks,
Zach

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Zachary Marshall
Solved:
Last query:
Last reply:
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#1

MadSpin has its own "gridpack" mode that does require an event sample to be setup correctly.

So the correct method to create a gridpack with madspin is
1) create a gridpack without madspin
2) run the gridpack to generate X events
3) run MadSpin on those events (and have the option "set ms_dir" in the madspin_card)
4) add the madspin_card (with the same option "set ms_dir") within the gridpack.

If you choose to have the ms_dir within the gridpack itself (with relative path in that case) then you need to add it within the gridpack tarball.

Cheers,

Olivier

Revision history for this message
Zachary Marshall (zach-marshall) said :
#2

Thanks Olivier! All clear. I think it'd be great if medium/long-term, this could be made into one step for a user — but I understand that's rather complicated to handle, and for now if we have a recipe we can work with it.

Cheers,
Zach

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#3

Sure,

Nothing really complicated to implement, (just the question of the precision that you want on the max_wgt).
My understanding so far was that CMS/Atlas wanted to do it their way and therefore not implement it but this should be quite straightforward.

Cheers,

Olivier

Revision history for this message
Zachary Marshall (zach-marshall) said :
#4

I'd definitely have no issue with this being implemented centrally :)

Best,
Zach