4l production from Higgs produced from VBF
Hi,
I am trying to produce Higgs via VBF using the command
generate p p > h j j $$ w+ w- z [QCD]
Then from that Higgs I am trying to decay it to ZZ and these two Z will further decay into 4 leptons. I tried to do that by using command like
generate p p > j j h $$ w+ w- z [QCD], (h > z z, z > l+ l-, z > l+ l-)
But it didn't work.
How can I do that?
If anyone can help me to solve this it will be great for me.
Thanking you in advance,
Arpita
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
You need to use madspin for doing the decay of the Higgs.
You have to set madspin in "spinmode=none" mode
so the following script should work
generate p p > h j j $$ w+ w- z [QCD]
output
launch
madpin=none
decay h > z > 2l+ 2l-
Now I'm not sure that
generate p p > h j j $$ w+ w- z [QCD]
correspond to the VBF process that you are looking for
should not it be
generate p p > h j j $$ w+ w- z QCD=0 [QCD]
or
generate p p > h j j QCD=0 [QCD]
Cheers,
Olivier
> On 3 Jun 2022, at 16:11, Arpita Mondal <email address hidden> wrote:
>
> New question #702058 on MadGraph5_aMC@NLO:
> https:/
>
> Hi,
>
> I am trying to produce Higgs via VBF using the command
>
> generate p p > h j j $$ w+ w- z [QCD]
>
> Then from that Higgs I am trying to decay it to ZZ and these two Z will further decay into 4 leptons. I tried to do that by using command like
> generate p p > j j h $$ w+ w- z [QCD], (h > z z, z > l+ l-, z > l+ l-)
>
> But it didn't work.
>
> How can I do that?
>
> If anyone can help me to solve this it will be great for me.
>
> Thanking you in advance,
> Arpita
>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
|
#2 |
Hi Oliver,
Thank you for your quick response.
The command "generate p p > h j j $$ w+ w- z [QCD]" is mentioned in a paper[1610.07922].
You advised to use madspin. I can do that. Actually for ggF I did using the command like
generate p p > h [QCD] > l+ l- l+ l-
and it worked fine.
If there is any possibility to do it in this way that will be helpful.
Revision history for this message
|
#3 |
Hi Oliver,
I tried to generate the process using madspin. But it is showing some error. I used the above command "generate p p > h j j $$ w+ w- z [QCD]" and then I did "madspin=ON" and in the madspin_card I added Higgs decay as " h > z z > 2l+ 2l-". But it didn't work. The details are given below.
The following switches determine which programs are run:
/======
1. Type of perturbative computation order = NLO
2. No MC@[N]LO matching / event generation fixed_order = OFF
3. Shower the generated events shower = HERWIG6
4. Decay onshell particles madspin = ON
5. Add weights to events for new hypp. reweight = Not Avail.
6. Run MadAnalysis5 on the events generated madanalysis = OFF
\======
Either type the switch number (1 to 6) to change its setting,
Set any switch explicitly (e.g. type 'fixed_order=ON' at the prompt)
Type 'help' for the list of all valid option
Type '0', 'auto', 'done' or just press enter when you are done.
>
INFO: will run in mode: aMC@NLO
INFO: modify parameter parton_shower of the run_card.dat to HERWIG6
Do you want to edit a card (press enter to bypass editing)?
/------
| 1. param : param_card.dat |
| 2. run : run_card.dat |
| 3. madspin : madspin_card.dat |
| 4. shower : shower_card.dat |
\------
you can also
- enter the path to a valid card or banner.
- use the 'set' command to modify a parameter directly.
The set option works only for param_card and run_card.
Type 'help set' for more information on this command.
- call an external program (ASperGE/
Type 'help' for the list of available command
[0, done, 1, param, 2, run, 3, madspin, 4, enter path, ... ][90s to answer]
>2
open /home/arpita/
Do you want to edit a card (press enter to bypass editing)?
/------
| 1. param : param_card.dat |
| 2. run : run_card.dat |
| 3. madspin : madspin_card.dat |
| 4. shower : shower_card.dat |
\------
you can also
- enter the path to a valid card or banner.
- use the 'set' command to modify a parameter directly.
The set option works only for param_card and run_card.
Type 'help set' for more information on this command.
- call an external program (ASperGE/
Type 'help' for the list of available command
[0, done, 1, param, 2, run, 3, madspin, 4, enter path, ... ]
>3
open /home/arpita/
Do you want to edit a card (press enter to bypass editing)?
/------
| 1. param : param_card.dat |
| 2. run : run_card.dat |
| 3. madspin : madspin_card.dat |
| 4. shower : shower_card.dat |
\------
you can also
- enter the path to a valid card or banner.
- use the 'set' command to modify a parameter directly.
The set option works only for param_card and run_card.
Type 'help set' for more information on this command.
- call an external program (ASperGE/
Type 'help' for the list of available command
[0, done, 1, param, 2, run, 3, madspin, 4, enter path, ... ]
>
INFO: Update the dependent parameter of the param_card.dat
INFO: Starting run
INFO: Compiling the code
INFO: Using built-in libraries for PDFs
INFO: Compiling source...
Error: no DISPLAY environment variable specified
INFO: ...done, continuing with P* directories
INFO: Compiling directories...
INFO: Compiling on 72 cores
INFO: Compiling P0_uu_huu...
INFO: Compiling P0_uc_huc...
INFO: Compiling P0_ud_hud...
INFO: Compiling P0_us_hus...
INFO: Compiling P0_us_hcd...
INFO: Compiling P0_uux_huux...
INFO: Compiling P0_uux_hddx...
INFO: Compiling P0_ucx_hucx...
INFO: Compiling P0_ucx_hdsx...
INFO: Compiling P0_udx_hudx...
INFO: Compiling P0_usx_husx...
INFO: Compiling P0_cd_hsu...
INFO: Compiling P0_du_hdu...
INFO: Compiling P0_dc_hsu...
INFO: Compiling P0_dc_hdc...
INFO: Compiling P0_dd_hdd...
INFO: Compiling P0_dux_hdux...
INFO: Compiling P0_ds_hds...
INFO: Compiling P0_ddx_huux...
INFO: Compiling P0_ddx_hddx...
INFO: Compiling P0_dsx_hucx...
INFO: Compiling P0_dsx_hdsx...
INFO: Compiling P0_su_hcd...
INFO: Compiling P0_uxu_huux...
INFO: Compiling P0_uxu_hddx...
INFO: Compiling P0_uxc_huxc...
INFO: Compiling P0_dcx_hdcx...
INFO: Compiling P0_uxc_hsdx...
INFO: Compiling P0_uxd_huxd...
INFO: Compiling P0_uxs_huxs...
INFO: Compiling P0_uxux_huxux...
INFO: Compiling P0_uxcx_huxcx...
INFO: Compiling P0_uxdx_huxdx...
INFO: Compiling P0_uxsx_huxsx...
INFO: Compiling P0_uxsx_hdxcx...
INFO: Compiling P0_cxdx_huxsx...
INFO: Compiling P0_dxu_hdxu...
INFO: Compiling P0_dxc_hdxc...
INFO: Compiling P0_dxd_huux...
INFO: Compiling P0_dxs_hdxs...
INFO: Compiling P0_dxs_hcux...
INFO: Compiling P0_dxd_hddx...
INFO: Compiling P0_dxux_hdxux...
INFO: Compiling P0_dxcx_huxsx...
INFO: Compiling P0_dxcx_hdxcx...
INFO: Compiling P0_dxdx_hdxdx...
INFO: Compiling P0_dxsx_hdxsx...
INFO: Compiling P0_sxux_hdxcx...
INFO: P0_dsx_hucx done.
INFO: P0_uxu_huux done.
INFO: P0_usx_husx done.
INFO: P0_uxc_hsdx done.
INFO: P0_dc_hsu done.
INFO: P0_uxc_huxc done.
INFO: P0_udx_hudx done.
INFO: P0_dd_hdd done.
INFO: P0_ucx_hdsx done.
INFO: P0_sxux_hdxcx done.
INFO: P0_dcx_hdcx done.
INFO: P0_uux_hddx done.
INFO: P0_ddx_huux done.
INFO: P0_dxd_huux done.
INFO: P0_uxu_hddx done.
INFO: P0_du_hdu done.
INFO: P0_dxs_hdxs done.
INFO: P0_dxdx_hdxdx done.
INFO: P0_cxdx_huxsx done.
INFO: P0_us_hus done.
INFO: P0_ucx_hucx done.
INFO: P0_dxd_hddx done.
INFO: P0_dxux_hdxux done.
INFO: P0_uxsx_huxsx done.
INFO: P0_uxcx_huxcx done.
INFO: P0_dxc_hdxc done.
INFO: P0_uux_huux done.
INFO: P0_uxsx_hdxcx done.
INFO: P0_dsx_hdsx done.
INFO: P0_dxs_hcux done.
INFO: P0_dxcx_hdxcx done.
INFO: P0_uu_huu done.
INFO: P0_dxu_hdxu done.
INFO: P0_us_hcd done.
INFO: P0_ds_hds done.
INFO: P0_uc_huc done.
INFO: P0_cd_hsu done.
INFO: P0_su_hcd done.
INFO: P0_dux_hdux done.
INFO: P0_dxsx_hdxsx done.
INFO: P0_dc_hdc done.
INFO: P0_uxd_huxd done.
INFO: P0_ddx_hddx done.
INFO: P0_uxdx_huxdx done.
INFO: P0_uxs_huxs done.
INFO: P0_ud_hud done.
INFO: P0_dxcx_huxsx done.
INFO: P0_uxux_huxux done.
INFO: Checking test output:
INFO: P0_uu_huu
INFO: Result for test_ME:
INFO: Passed.
INFO: Result for test_MC:
INFO: Passed.
INFO: Result for check_poles:
Error detected in "launch auto "
write debug file /home/arpita/
If you need help with this issue please contact us on https:/
aMCatNLOError : Poles do not cancel, run cannot continue
quit
INFO:
Revision history for this message
|
#4 |
So this has nothing to do with madspin,
but you should set madspin=none and not madspin=ON
(madspin=ON will crash for such decay)
Now your error is an issue of pole cancelation which is not accurate enough
They are two options:
1) you are breaking gauge invariance with your syntax that lead to a breaking of NLO accuracy.
Since I do not understand your syntax and that you are using syntax known for breaking gauge invariance you are likely in a situation where the computation is just not NLO accurate due to that.
2) You are missing some pentagon ( this is likely true) and such pentagon doe not contribute but lead to a non cancellation of the pole. In that case you can edit the FKS_params.dat to remove that threshold.
You likely have both issues here.
Cheers,
Olivier
> On 4 Jun 2022, at 11:15, Arpita Mondal <email address hidden> wrote:
>
> Question #702058 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Arpita Mondal is still having a problem:
> Hi Oliver,
> I tried to generate the process using madspin. But it is showing some error. I used the above command "generate p p > h j j $$ w+ w- z [QCD]" and then I did "madspin=ON" and in the madspin_card I added Higgs decay as " h > z z > 2l+ 2l-". But it didn't work. The details are given below.
>
> The following switches determine which programs are run:
> /======
> 1. Type of perturbative computation order = NLO
> 2. No MC@[N]LO matching / event generation fixed_order = OFF
> 3. Shower the generated events shower = HERWIG6
> 4. Decay onshell particles madspin = ON
> 5. Add weights to events for new hypp. reweight = Not Avail.
> 6. Run MadAnalysis5 on the events generated madanalysis = OFF
> \======
> Either type the switch number (1 to 6) to change its setting,
> Set any switch explicitly (e.g. type 'fixed_order=ON' at the prompt)
> Type 'help' for the list of all valid option
> Type '0', 'auto', 'done' or just press enter when you are done.
>>
> INFO: will run in mode: aMC@NLO
> INFO: modify parameter parton_shower of the run_card.dat to HERWIG6
> Do you want to edit a card (press enter to bypass editing)?
> /------
> | 1. param : param_card.dat |
> | 2. run : run_card.dat |
> | 3. madspin : madspin_card.dat |
> | 4. shower : shower_card.dat |
> \------
> you can also
> - enter the path to a valid card or banner.
> - use the 'set' command to modify a parameter directly.
> The set option works only for param_card and run_card.
> Type 'help set' for more information on this command.
> - call an external program (ASperGE/
> Type 'help' for the list of available command
> [0, done, 1, param, 2, run, 3, madspin, 4, enter path, ... ][90s to answer]
>> 2
> open /home/arpita/
> Do you want to edit a card (press enter to bypass editing)?
> /------
> | 1. param : param_card.dat |
> | 2. run : run_card.dat |
> | 3. madspin : madspin_card.dat |
> | 4. shower : shower_card.dat |
> \------
> you can also
> - enter the path to a valid card or banner.
> - use the 'set' command to modify a parameter directly.
> The set option works only for param_card and run_card.
> Type 'help set' for more information on this command.
> - call an external program (ASperGE/
> Type 'help' for the list of available command
> [0, done, 1, param, 2, run, 3, madspin, 4, enter path, ... ]
>> 3
> open /home/arpita/
> Do you want to edit a card (press enter to bypass editing)?
> /------
> | 1. param : param_card.dat |
> | 2. run : run_card.dat |
> | 3. madspin : madspin_card.dat |
> | 4. shower : shower_card.dat |
> \------
> you can also
> - enter the path to a valid card or banner.
> - use the 'set' command to modify a parameter directly.
> The set option works only for param_card and run_card.
> Type 'help set' for more information on this command.
> - call an external program (ASperGE/
> Type 'help' for the list of available command
> [0, done, 1, param, 2, run, 3, madspin, 4, enter path, ... ]
>>
> INFO: Update the dependent parameter of the param_card.dat
> INFO: Starting run
> INFO: Compiling the code
> INFO: Using built-in libraries for PDFs
> INFO: Compiling source...
> Error: no DISPLAY environment variable specified
> INFO: ...done, continuing with P* directories
> INFO: Compiling directories...
> INFO: Compiling on 72 cores
> INFO: Compiling P0_uu_huu...
> INFO: Compiling P0_uc_huc...
> INFO: Compiling P0_ud_hud...
> INFO: Compiling P0_us_hus...
> INFO: Compiling P0_us_hcd...
> INFO: Compiling P0_uux_huux...
> INFO: Compiling P0_uux_hddx...
> INFO: Compiling P0_ucx_hucx...
> INFO: Compiling P0_ucx_hdsx...
> INFO: Compiling P0_udx_hudx...
> INFO: Compiling P0_usx_husx...
> INFO: Compiling P0_cd_hsu...
> INFO: Compiling P0_du_hdu...
> INFO: Compiling P0_dc_hsu...
> INFO: Compiling P0_dc_hdc...
> INFO: Compiling P0_dd_hdd...
> INFO: Compiling P0_dux_hdux...
> INFO: Compiling P0_ds_hds...
> INFO: Compiling P0_ddx_huux...
> INFO: Compiling P0_ddx_hddx...
> INFO: Compiling P0_dsx_hucx...
> INFO: Compiling P0_dsx_hdsx...
> INFO: Compiling P0_su_hcd...
> INFO: Compiling P0_uxu_huux...
> INFO: Compiling P0_uxu_hddx...
> INFO: Compiling P0_uxc_huxc...
> INFO: Compiling P0_dcx_hdcx...
> INFO: Compiling P0_uxc_hsdx...
> INFO: Compiling P0_uxd_huxd...
> INFO: Compiling P0_uxs_huxs...
> INFO: Compiling P0_uxux_huxux...
> INFO: Compiling P0_uxcx_huxcx...
> INFO: Compiling P0_uxdx_huxdx...
> INFO: Compiling P0_uxsx_huxsx...
> INFO: Compiling P0_uxsx_hdxcx...
> INFO: Compiling P0_cxdx_huxsx...
> INFO: Compiling P0_dxu_hdxu...
> INFO: Compiling P0_dxc_hdxc...
> INFO: Compiling P0_dxd_huux...
> INFO: Compiling P0_dxs_hdxs...
> INFO: Compiling P0_dxs_hcux...
> INFO: Compiling P0_dxd_hddx...
> INFO: Compiling P0_dxux_hdxux...
> INFO: Compiling P0_dxcx_huxsx...
> INFO: Compiling P0_dxcx_hdxcx...
> INFO: Compiling P0_dxdx_hdxdx...
> INFO: Compiling P0_dxsx_hdxsx...
> INFO: Compiling P0_sxux_hdxcx...
> INFO: P0_dsx_hucx done.
> INFO: P0_uxu_huux done.
> INFO: P0_usx_husx done.
> INFO: P0_uxc_hsdx done.
> INFO: P0_dc_hsu done.
> INFO: P0_uxc_huxc done.
> INFO: P0_udx_hudx done.
> INFO: P0_dd_hdd done.
> INFO: P0_ucx_hdsx done.
> INFO: P0_sxux_hdxcx done.
> INFO: P0_dcx_hdcx done.
> INFO: P0_uux_hddx done.
> INFO: P0_ddx_huux done.
> INFO: P0_dxd_huux done.
> INFO: P0_uxu_hddx done.
> INFO: P0_du_hdu done.
> INFO: P0_dxs_hdxs done.
> INFO: P0_dxdx_hdxdx done.
> INFO: P0_cxdx_huxsx done.
> INFO: P0_us_hus done.
> INFO: P0_ucx_hucx done.
> INFO: P0_dxd_hddx done.
> INFO: P0_dxux_hdxux done.
> INFO: P0_uxsx_huxsx done.
> INFO: P0_uxcx_huxcx done.
> INFO: P0_dxc_hdxc done.
> INFO: P0_uux_huux done.
> INFO: P0_uxsx_hdxcx done.
> INFO: P0_dsx_hdsx done.
> INFO: P0_dxs_hcux done.
> INFO: P0_dxcx_hdxcx done.
> INFO: P0_uu_huu done.
> INFO: P0_dxu_hdxu done.
> INFO: P0_us_hcd done.
> INFO: P0_ds_hds done.
> INFO: P0_uc_huc done.
> INFO: P0_cd_hsu done.
> INFO: P0_su_hcd done.
> INFO: P0_dux_hdux done.
> INFO: P0_dxsx_hdxsx done.
> INFO: P0_dc_hdc done.
> INFO: P0_uxd_huxd done.
> INFO: P0_ddx_hddx done.
> INFO: P0_uxdx_huxdx done.
> INFO: P0_uxs_huxs done.
> INFO: P0_ud_hud done.
> INFO: P0_dxcx_huxsx done.
> INFO: P0_uxux_huxux done.
> INFO: Checking test output:
> INFO: P0_uu_huu
> INFO: Result for test_ME:
> INFO: Passed.
> INFO: Result for test_MC:
> INFO: Passed.
> INFO: Result for check_poles:
> Error detected in "launch auto "
> write debug file /home/arpita/
> If you need help with this issue please contact us on https:/
> aMCatNLOError : Poles do not cancel, run cannot continue
> quit
> INFO:
>
> --
> 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 Arpita Mondal for more information if necessary.