Madspin max_weight_ps_point question

Asked by Hanlin Xu

Dear experts,

I am wondering how max_weight_ps_point (also Nevents_for_max_weigth) affecting the precision of Madspin.

The default when I want to the following decay(~6000 events) is "Probing the first 75 events with 400 phase space points"
However this cost too much time, one event need "INFO: Event 1/75 : 14m 36s"

So I wonder if it is possible to reduce the max_weight_ps_point(Nevents_for_max_weigth) to make it faster?
Because our CPU has an limit on running time

Best,
Hanlin

Decay Infomation:
generate p p > H++ H-- / EXCL, (H++ > w+ w+ , w+ > fermions fermions , w+ > fermions fermions QCD=99), (H-- > w- w- , w- > fermions fermions , w- > fermions fermions QCD=99) --no_warning=duplicate;

fermions ,means all fermions include leptons and quarks, so there are huge amount of diagrams

Question information

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

Did you put all the mass of the light quark and lepton to zero?

Madspin will then need much less cpu time to do the computation thanks to symmetry.

Now you can indeed play with those parameters. If this leads to an under estimation of the max weights you will get warning/crash when the actual decay occurs.

Now you can also save that part of the computation to reuse it later. This can help your cpu limitation. The parameter to set is madspin_dir if I remember correctly

Get Outlook for iOS<https://aka.ms/o0ukef>

________________________________
From: <email address hidden> on behalf of Hanlin Xu <email address hidden>
Sent: Wednesday, February 20, 2019 11:52 AM
To: Olivier Mattelaer
Subject: [Question #678674]: Madspin max_weight_ps_point question

New question #678674 on MadGraph5_aMC@NLO:
https://answers.launchpad.net/mg5amcnlo/+question/678674

Dear experts,

I am wondering how max_weight_ps_point (also Nevents_for_max_weigth) affecting the precision of Madspin.

The default when I want to the following decay(~6000 events) is "Probing the first 75 events with 400 phase space points"
However this cost too much time, one event need "INFO: Event 1/75 : 14m 36s"

So I wonder if it is possible to reduce the max_weight_ps_point(Nevents_for_max_weigth) to make it faster?
Because our CPU has an limit on running time

Best,
Hanlin

Decay Infomation:
generate p p > H++ H-- / EXCL, (H++ > w+ w+ , w+ > fermions fermions , w+ > fermions fermions QCD=99), (H-- > w- w- , w- > fermions fermions , w- > fermions fermions QCD=99) --no_warning=duplicate;

fermions ,means all fermions include leptons and quarks, so there are huge amount of diagrams

--
You received this question notification because you are an answer
contact for MadGraph5_aMC@NLO.

Revision history for this message
Hanlin Xu (hanlinxuy) said :
#2

Dear Olivier,

Thank you very much for answering!
These almost solve my question.

Did you put all the mass of the light quark and lepton to zero?
>>No. This would a good choice

Now you can indeed play with those parameters. If this leads to an under estimation of the max weights you will get warning/crash when the actual decay occurs.
>>Just want to confirm on thing. May I understand it like: I can lower those two variables as much as I can, just need to make sure there will be no warning message from Maspin then everything is OK? If so, I can tune them myself and solve this question.

Best,
Hanlin

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

Hi,

Yes you understood correctly.

Cheers,

Olivier

Revision history for this message
Hanlin Xu (hanlinxuy) said :
#4

Thanks Olivier Mattelaer, that solved my question.