Difference between revisions of "CalcHEP tutorial"

From HEPMDB
Jump to: navigation, search
(Blanked the page)
Line 1: Line 1:
  
 +
In order to familiarise yourself with <tt>CalcHEP</tt>, we will study two examples, one sightly more complicated than the other. Hopefully, by the end of this tutorial, you will be able to use majority of the functions of <tt>CalcHEP</tt>.
 +
 +
Please note that this is not a reference manual. If you wish to look at the reference manual, it is available [[CalcHEP reference|here]].
 +
 +
__TOC__
 +
 +
== A simple leptonic process ==
 +
Let's start with a simple process and try to compute the matrix elements using <tt>CalcHEP</tt>. In this section, we will study:
 +
<center><tt>ee → μμττ</tt></center>
 +
 +
The process will be studied in the standard model framework.
 +
 +
=== Preparing <tt>HEPMDB</tt> ===
 +
First, connect to <tt>HEPMDB</tt> and go in the <tt>Calculate</tt> section. In the left panel, in the <tt>CalcHEP</tt> section, check whether the <tt>Standard Model (CKM=1)</tt> line appears. If not, in the <tt>CalcHEP</tt> menu, choose <tt>Import model</tt>. When you find the line <tt>Standard Model (CKM=1)</tt> for <tt>CalcHEP</tt> (it should be the model 43), select it and click <tt>Select</tt>. The model should now be accessible in your environment.
 +
 +
This model is the complete standard model without CKM matrix. As a consequence, it is lighter and in situation where quarks' flavours don't matter, it gives the same results as the standard model.
 +
 +
=== A template batch file ===
 +
Select the model and select <tt>Edit Full Batch File</tt> in the <tt>CalcHEP</tt> menu. A new window will appear. You will be able to edit the batch file which is the file describing the process of interest. Click on the button <tt>Load batch template</tt>.
 +
 +
You now have a template file with nearly every possible field already offered. You also have help in the comments. The comments are lines beginning with a #. They are ignored by <tt>CalcHEP</tt> and thanks to them, you can add any information you want for any body reading the batch file.
 +
 +
=== Model information ===
 +
The first three fields are information about the model.
 +
# The first line gives the model to use. You should not touch it as this is a relic of <tt>CalcHEP</tt> local batch mode.
 +
# The second option is <tt>Model changed</tt>. This tells <tt>CalcHEP</tt> that model files have been changed.
 +
# Finally, <tt>Gauge</tt> tells what gauge to use, Feynmann or unitary. Many model are built implicitly assuming that the gauge is Feynmann's. So you should not change this field either.
 +
 +
=== Defining the process ===
 +
We have several lines to define our process. Remove every <tt>Process</tt>, <tt>Decay</tt> and <tt>Composite</tt> field. You can now write:
 +
<center><tt>Process: e,E -> m,M,l,L</tt></center>
 +
 +
In the standard model of <tt>CalcHEP</tt>, <tt>e</tt> refers to electron, <tt>m</tt> to muons, <tt>l</tt> to taus and the capital letters to their anti-particle. The particle list with their names for the model is available at the <tt>View particles</tt> entry of the <tt>CalcHEP</tt> menu. You cannot access it while editing the batch file however.
 +
 +
So we set up an electron-positron scattering with a pair of muons and a pair of taus outgoing.
 +
No further information is needed to describe the process itself.
 +
 +
=== Beams configuration ===
 +
We now have to configure the beams. The next field is about the pdfs. While this is useful for proton or any composite particle scattering, we do not need it for electron-positron scattering. We can write:
 +
<center><tt>pdf1: OFF</tt></center>
 +
And the same thing for the second pdf.
 +
 +
Concerning the energy of the beam, let's set 100 GeV beams.
 +
<center><tt>p1: 100</tt></center>
 +
<center><tt>p2: 100</tt></center>
 +
 +
=== Changing model parameters ===
 +
We now have the possibility to change some model parameters. Let's say you want to change the strength of the electromagnetic force. You would write:
 +
<center><tt>Parameter: EE=0.31</tt></center>
 +
with <tt>0.31</tt> being the new value of the electrical charge of the electron in natural units.
 +
Some models are more flexible than others on that kind of point. But for our tutorial, we are not going to change the well known parameters.
 +
 +
Instead, we're going to scan the possible Higgs masses. For this, you can write:
 +
<center><tt>Run parameter: Mh</tt></center>
 +
<center><tt>Run begin:    100</tt></center>
 +
<center><tt>Run step size: 10</tt></center>
 +
<center><tt>Run n steps:  6</tt></center>
 +
This means we're going to scan the following values for <tt>Mh</tt>: 100 Gev, 110 GeV, 120 GeV, 130 GeV, 140 GeV, 150 GeV.
 +
This is of course a pretty useful possibility when studying a new model.
 +
 +
We then have the possibility to set some parameters about QCD but this will be studied in the next example.
 +
 +
=== Cuts ===
 +
Various cuts are possible. For our simple tutorial, we are not going to study them. Please refer to the reference manual if you are interested in them.
 +
 +
=== Kinematics and regularization ===
 +
To tell <tt>CalcHEP</tt> how to handle the phase space, you should fill the kinematic information.
 +
Using this information, a nice parametrisation of the phase space is used.
 +
 +
In our case, the two ingoing particles will give two bosons, each of them decaying in a lepton pair. Hence, our kinematics are written as:
 +
<center><tt>Kinematics :      12 -> 34, 56</tt></center>
 +
<center><tt>Kinematics :      34 -> 3 , 4</tt></center>
 +
<center><tt>Kinematics :      56 -> 5 , 6</tt></center>
 +
 +
To improve the precision of the computation, it is important to tell <tt>CalcHEP</tt> where the resonances are.
 +
In our case, we have resonance on the dimuon and ditau masses for the Z boson and for the Higgs.
 +
So we will write:
 +
<center><tt>Regularization momentum: 34</tt></center>
 +
<center><tt>Regularization mass:    MZ</tt></center>
 +
<center><tt>Regularization width:    wZ</tt></center>
 +
<center><tt>Regularization power:    2</tt></center>
 +
 +
<center><tt>Regularization momentum: 34</tt></center>
 +
<center><tt>Regularization mass:    Mh</tt></center>
 +
<center><tt>Regularization width:    wh</tt></center>
 +
<center><tt>Regularization power:    2</tt></center>
 +
 +
<center><tt>Regularization momentum: 56</tt></center>
 +
<center><tt>Regularization mass:    MZ</tt></center>
 +
<center><tt>Regularization width:    wZ</tt></center>
 +
<center><tt>Regularization power:    2</tt></center>
 +
 +
<center><tt>Regularization momentum: 56</tt></center>
 +
<center><tt>Regularization mass:    Mh</tt></center>
 +
<center><tt>Regularization width:    wh</tt></center>
 +
<center><tt>Regularization power:    2</tt></center>
 +
 +
=== Plots ===
 +
<tt>CalcHEP</tt> has automated plot capacities. However, with <tt>HEPMDB</tt>, they are of little use. We will ignore them.
 +
 +
=== Event generation ===
 +
For event generation, we really have two main parameters:
 +
#The number of events. We'll write: <tt>Number of events (per run step): 100000</tt>
 +
#The output file name. <tt>Filename: tutorial_ee_mmll</tt>
 +
 +
=== Parallelization ===
 +
When using the template file of <tt>HEPMDB</tt>, all parallelization parameters are good. It is possible though, to set the maximum number of CPU to 24.
 +
 +
=== Vegas session ===
 +
Finally, the Vegas session has some parameters. It will be used to compute the cross-section and to prepare the grid for event generation. Two sessions with 5 calls of 100,000 points is usually sufficient. With the number of calls there is a trade-off; the higher the number of calls means it will take longer to run the batch file on HEPMDB but reducing the number of calls leads to a decrease in accuracy of the cross sections. It is therefore worth experimenting with a couple of points in the batch interface of CalcHEP to see what optimization can be made.
 +
<center><tt>nSess_1:  5</tt></center>
 +
<center><tt>nCalls_1:  100000</tt></center>
 +
<center><tt>nSess_2:  5</tt></center>
 +
<center><tt>nCalls_2:  100000</tt></center>
 +
 +
=== Final words ===
 +
The batch file is now complete and ready to run. I recommend plotting the number of events as a function of the tau pair invariant mass.
 +
 +
== Involving partons ==

Revision as of 02:07, 2 October 2013

In order to familiarise yourself with CalcHEP, we will study two examples, one sightly more complicated than the other. Hopefully, by the end of this tutorial, you will be able to use majority of the functions of CalcHEP.

Please note that this is not a reference manual. If you wish to look at the reference manual, it is available here.

A simple leptonic process

Let's start with a simple process and try to compute the matrix elements using CalcHEP. In this section, we will study:

ee → μμττ

The process will be studied in the standard model framework.

Preparing HEPMDB

First, connect to HEPMDB and go in the Calculate section. In the left panel, in the CalcHEP section, check whether the Standard Model (CKM=1) line appears. If not, in the CalcHEP menu, choose Import model. When you find the line Standard Model (CKM=1) for CalcHEP (it should be the model 43), select it and click Select. The model should now be accessible in your environment.

This model is the complete standard model without CKM matrix. As a consequence, it is lighter and in situation where quarks' flavours don't matter, it gives the same results as the standard model.

A template batch file

Select the model and select Edit Full Batch File in the CalcHEP menu. A new window will appear. You will be able to edit the batch file which is the file describing the process of interest. Click on the button Load batch template.

You now have a template file with nearly every possible field already offered. You also have help in the comments. The comments are lines beginning with a #. They are ignored by CalcHEP and thanks to them, you can add any information you want for any body reading the batch file.

Model information

The first three fields are information about the model.

  1. The first line gives the model to use. You should not touch it as this is a relic of CalcHEP local batch mode.
  2. The second option is Model changed. This tells CalcHEP that model files have been changed.
  3. Finally, Gauge tells what gauge to use, Feynmann or unitary. Many model are built implicitly assuming that the gauge is Feynmann's. So you should not change this field either.

Defining the process

We have several lines to define our process. Remove every Process, Decay and Composite field. You can now write:

Process: e,E -> m,M,l,L

In the standard model of CalcHEP, e refers to electron, m to muons, l to taus and the capital letters to their anti-particle. The particle list with their names for the model is available at the View particles entry of the CalcHEP menu. You cannot access it while editing the batch file however.

So we set up an electron-positron scattering with a pair of muons and a pair of taus outgoing. No further information is needed to describe the process itself.

Beams configuration

We now have to configure the beams. The next field is about the pdfs. While this is useful for proton or any composite particle scattering, we do not need it for electron-positron scattering. We can write:

pdf1: OFF

And the same thing for the second pdf.

Concerning the energy of the beam, let's set 100 GeV beams.

p1: 100
p2: 100

Changing model parameters

We now have the possibility to change some model parameters. Let's say you want to change the strength of the electromagnetic force. You would write:

Parameter: EE=0.31

with 0.31 being the new value of the electrical charge of the electron in natural units. Some models are more flexible than others on that kind of point. But for our tutorial, we are not going to change the well known parameters.

Instead, we're going to scan the possible Higgs masses. For this, you can write:

Run parameter: Mh
Run begin: 100
Run step size: 10
Run n steps: 6

This means we're going to scan the following values for Mh: 100 Gev, 110 GeV, 120 GeV, 130 GeV, 140 GeV, 150 GeV. This is of course a pretty useful possibility when studying a new model.

We then have the possibility to set some parameters about QCD but this will be studied in the next example.

Cuts

Various cuts are possible. For our simple tutorial, we are not going to study them. Please refer to the reference manual if you are interested in them.

Kinematics and regularization

To tell CalcHEP how to handle the phase space, you should fill the kinematic information. Using this information, a nice parametrisation of the phase space is used.

In our case, the two ingoing particles will give two bosons, each of them decaying in a lepton pair. Hence, our kinematics are written as:

Kinematics : 12 -> 34, 56
Kinematics : 34 -> 3 , 4
Kinematics : 56 -> 5 , 6

To improve the precision of the computation, it is important to tell CalcHEP where the resonances are. In our case, we have resonance on the dimuon and ditau masses for the Z boson and for the Higgs. So we will write:

Regularization momentum: 34
Regularization mass: MZ
Regularization width: wZ
Regularization power: 2
Regularization momentum: 34
Regularization mass: Mh
Regularization width: wh
Regularization power: 2
Regularization momentum: 56
Regularization mass: MZ
Regularization width: wZ
Regularization power: 2
Regularization momentum: 56
Regularization mass: Mh
Regularization width: wh
Regularization power: 2

Plots

CalcHEP has automated plot capacities. However, with HEPMDB, they are of little use. We will ignore them.

Event generation

For event generation, we really have two main parameters:

  1. The number of events. We'll write: Number of events (per run step): 100000
  2. The output file name. Filename: tutorial_ee_mmll

Parallelization

When using the template file of HEPMDB, all parallelization parameters are good. It is possible though, to set the maximum number of CPU to 24.

Vegas session

Finally, the Vegas session has some parameters. It will be used to compute the cross-section and to prepare the grid for event generation. Two sessions with 5 calls of 100,000 points is usually sufficient. With the number of calls there is a trade-off; the higher the number of calls means it will take longer to run the batch file on HEPMDB but reducing the number of calls leads to a decrease in accuracy of the cross sections. It is therefore worth experimenting with a couple of points in the batch interface of CalcHEP to see what optimization can be made.

nSess_1: 5
nCalls_1: 100000
nSess_2: 5
nCalls_2: 100000

Final words

The batch file is now complete and ready to run. I recommend plotting the number of events as a function of the tau pair invariant mass.

Involving partons