Gridpack addmasses clarification

Asked by Josh McFayden

Hi all,

I just wanted a quick clarification on the use of addmasses.py with gridpacks.

Do I understand correctly that addmasses will run by default on all events produced by gridpacks, but that is not run on events not using gridpacks?

This seems a little strange to me. For example on ATLAS we have samples where we combine gridpack and non-gridpack subprocesses to get a final sample. E.g. V+jets, we have Np0,1,2,3 without a gridpack and Np4 with a gridpack. This means that the Np4 sample will be treated differently even though the parameters we pass to MG5_aMC are identical to the lower multiplicity processes. This doesn't seem right to me, we have a hidden inconsistency.

Best,

Josh.

Question information

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

Hi Josh,

That’s correct.

I’m considering to simply remove this addmasses.py
for the next version of the code actually.

Cheers,

Olivier

On 10 Sep 2015, at 18:43, Josh McFayden <email address hidden> wrote:

> New question #271270 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/271270
>
> Hi all,
>
> I just wanted a quick clarification on the use of addmasses.py with gridpacks.
>
> Do I understand correctly that addmasses will run by default on all events produced by gridpacks, but that is not run on events not using gridpacks?
>
> This seems a little strange to me. For example on ATLAS we have samples where we combine gridpack and non-gridpack subprocesses to get a final sample. E.g. V+jets, we have Np0,1,2,3 without a gridpack and Np4 with a gridpack. This means that the Np4 sample will be treated differently even though the parameters we pass to MG5_aMC are identical to the lower multiplicity processes. This doesn't seem right to me, we have a hidden inconsistency.
>
>
> Best,
>
> Josh.
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Revision history for this message
Josh McFayden (mcfayden) said :
#2

Hi Olivier,

Thanks a lot for the fast reply.

Ok that's unfortunate, since it means we now have an inconsistent mix in our samples.
I am going to modify our ATLAS MG5_aMC setup to remove the addmasses.py file by hand, unless you have an objection?
Can you confirm that this should make the gridpack and non-gridpack modes consistent?

Best,

Josh.

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

Hi Josh,

> I am going to modify our ATLAS MG5_aMC setup to remove the addmasses.py file by hand, unless you have an objection?

No problem with that.

Cheers,

Olivier

On 10 Sep 2015, at 22:37, Josh McFayden <email address hidden> wrote:

> Question #271270 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/271270
>
> Status: Answered => Open
>
> Josh McFayden is still having a problem:
> Hi Olivier,
>
> Thanks a lot for the fast reply.
>
> Ok that's unfortunate, since it means we now have an inconsistent mix in our samples.
> I am going to modify our ATLAS MG5_aMC setup to remove the addmasses.py file by hand, unless you have an objection?
> Can you confirm that this should make the gridpack and non-gridpack modes consistent?
>
> Best,
>
> Josh.
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Can you help with this problem?

Provide an answer of your own, or ask Josh McFayden for more information if necessary.

To post a message you must log in.