Can't restrict HC_NLO_X0_UFO model when I import it

Asked by Edoardo Iannucci

Hi! I'm trying to generate a single top production process in association with a Higgs boson

p p > t x0 j

I'm using a copy of the model HC_NLO_X0_UFO and I import it with the no_b_mass restriction. I want to change some parameters, so I change them in the restrict_no_b_mass.dat file. The problem is that when I'm about to launch my process the parameters I've changed are all set to 1.

I don't know how to solve this problem

Thanks in advance for your help
Edoardo

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

Which file are present within the HC_NLO_X0_UFO model?
Do you have any other file ending with no_b_mass?
Which value did you set within the restrict_card?

Cheers,

Olivier

Revision history for this message
Edoardo Iannucci (edoiannu) said :
#2

Hi Olivier, thanks for your answer.

In the model are present:

restrict_4Fnoyb.dat
*_c_mass.dat
*_default.dat
*_heft.dat
*_no_b_mass.dat

I have another file ending with no_b_mass which is paramcard_no_b_mass.dat

I set the following values for the Block frblock in the file restrict_no_b_mass.dat:

Block frblock
    1 1.000000e+03 # Lambda
    2 0.707107e+00 # cosa
    3 1.414214e+00 # kSM
    4 1.414214e+00 # kHtt
    5 1.414214e+00 # kAtt
    6 0.000000e+00 # kHbb
    7 0.000000e+00 # kAbb
    8 0.000000e+00 # kHll
    9 0.000000e+00 # kAll
   10 0.000000e+00 # kHaa
   11 0.000000e+00 # kAaa
   12 0.000000e+00 # kHza
   13 0.000000e+00 # kAza
   14 0.000000e+00 # kHgg
   15 0.000000e+00 # kAgg
   16 0.000000e+00 # kHzz
   17 0.000000e+00 # kAzz
   18 0.000000e+00 # kHww
   19 0.000000e+00 # kAww
   20 0.000000e+00 # kHda
   21 0.000000e+00 # kHdz
   22 0.000000e+00 # kHdwR
   23 0.000000e+00 # kHdwI
  100 0.000000e+00 # kHcc
  101 0.000000e+00 # kAcc

Cheers,
Edoardo

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

So since you have the file paramcard_no_b_mass.dat
This is the file that is going to be present to the "user" when using the model with that restriction file.
The file restrict_no_b_mass.dat being then only used to run the requested restriction.

This mode allows you to setup "ugly" value that are sometimes needed to configure the restriction that you want while still presenting to the "user" quite natural value (that typically would have trigger additional restriction on the model and/or on the free parameter of the model).

If you do not want such mode, you can obviously remove that particular file.

But in your case since you seems to want to remove additional parameter, it would make sense to create another restriction file (with another name) since otherwise this will be confusing for the person that are using your model.

Cheers,

Olivier

Revision history for this message
Edoardo Iannucci (edoiannu) said :
#4

Thanks Olivier Mattelaer, that solved my question.