| 4 | | The easiest way to implement momentum dependent form factors, without changing all the details in the {{{matrix.f}}} files in a process is by adding them in the model files. In particular the {{{couplings.f}}} can contain momentum dependent form factors. The following steps explain most of the details. |
| 5 | | * The first thing you have to do is download the full MG_ME package and untar it. Then, if your model contains new particles and interactions add them to the SM using the Software.UserModel, giving some generic values to the coupling constants. (If your model does not contain new particles and you only want to modify existing interactions, it is enough to make a copy of the {{{sm}}} directory to a new directory. ) |
| | 4 | The easiest way to implement momentum dependent form factors, without changing all the details in the {{{ |
| | 5 | matrix.f |
| | 6 | }}} files in a process is by adding them in the model files. In particular the {{{ |
| | 7 | couplings.f |
| | 8 | }}} can contain momentum dependent form factors. The following steps explain most of the details. |
| | 9 | * The first thing you have to do is download the full MG_ME package and untar it. Then, if your model contains new particles and interactions add them to the SM using the Software.UserModel, giving some generic values to the coupling constants. (If your model does not contain new particles and you only want to modify existing interactions, it is enough to make a copy of the {{{ |
| | 10 | sm |
| | 11 | }}} directory to a new directory. ) |
| 12 | | * As a final step you have to make sure that the {{{setpara}}} subroutine is called on an event-by-event basis, by adding to the {{{run_card.dat}}} the line {{{ T = fixed_couplings ! if .false. calc. coupl. for every event}}}just after the line where you can set the scale factor. For an example {{{run_card.dat}}} look [attachment:run_card.dat here]. |
| | 24 | couplings.f |
| | 25 | }}} file. These momenta can be used to calculate the anomalous (momentum dependent) couplings. The syntax is as follows. All the momenta are saved in an array called pp. The first element is running from 0 to 3, these are the energy, and the x, y and z components of the momentum of a particle (the beam direction is in the z direction) in the center of momentum frame of the event. The second element of the array labels the particles. Only momenta of '''external particles''' are in the array. The labeling is as follows. The first two are the incoming particles, and the others the outgoing numbered according to how the process is written down in the {{{ |
| | 26 | proc_card.dat |
| | 27 | }}}. For example, if you are studying {{{ |
| | 28 | e+e->Zh>bb~mu+mu- |
| | 29 | }}} then the first particle will be the positron, the second the electron. The final state particles: b quark, b anti-quark, muon+ and muon- , are 3, 4, 5 and 6 respectively. Hence momentum pp(2,4) is the y-component of the momentum of the b anti-quark in the center of momentum frame of the event. Using these components most anomalous couplings can be implemented by changing the SM values of the couplings in the {{{ |
| | 30 | couplings.f |
| | 31 | }}} file. |
| | 32 | * As a final step you have to make sure that the {{{ |
| | 33 | setpara |
| | 34 | }}} subroutine is called on an event-by-event basis, by adding to the {{{ |
| | 35 | run_card.dat |
| | 36 | }}} the line {{{ |
| | 37 | T = fixed_couplings ! if .false. calc. coupl. for every event |
| | 38 | }}}just after the line where you can set the scale factor. For an example {{{ |
| | 39 | run_card.dat |
| | 40 | }}} look [attachment:run_card.dat here]. |
| 15 | | Note that it might be interesting to make a new model for every process you want to study. In that case, instead of modifying the {{{couplings.f}}} file in the =./Source/MODEL/= directory, you could change the one in the =./Models/newmodel/= directory. Doing it this way has the clear advantage of being able to regenerate your process, without having to change the {{{couplings.f}}} file every time, which makes it less error prone. (Make sure that you also save a copy of the {{{proc_card.dat}}} in the model directory so that you won't forget for which process you created this model.) |
| | 43 | Note that it might be interesting to make a new model for every process you want to study. In that case, instead of modifying the {{{ |
| | 44 | couplings.f |
| | 45 | }}} file in the =./Source/MODEL/= directory, you could change the one in the =./Models/newmodel/= directory. Doing it this way has the clear advantage of being able to regenerate your process, without having to change the {{{ |
| | 46 | couplings.f |
| | 47 | }}} file every time, which makes it less error prone. (Make sure that you also save a copy of the {{{ |
| | 48 | proc_card.dat |
| | 49 | }}} in the model directory so that you won't forget for which process you created this model.) |
