21
21
! =================================================================================
26
26
! IMODE=0, IBP reduction
27
27
! IMODE=1, PaVe reduction
28
28
! IMODE=2, PaVe reduction with stablility improved by IBP reduction
32
32
! Default :: .TRUE.
33
33
! Use RECYCLING OR NOT IN IREGI
37
37
! The parameters below set the stability checks of MadLoop at run time
38
38
! =================================================================================
40
! Decide in which mode to set CutTools at runtime.
41
! The possible modes are:
40
! Decide in which mode to run MadLoop
43
! imode:| actions performed by ctsxcut:
45
! 0 | (dp_dir,dp_inv)-> dp_Atest -> stable -> (only if stable=.false.) ->
46
! | (mp_dir,mp_inv)-> mp_Atest -> stable
47
! 1 | (dp_dir) -> dp_Ntest -> stable
48
! 2 | (dp_inv) -> dp_Ntest -> stable
49
! 3 | (dp_dir,dp_inv)-> dp_Atest -> stable
50
! 4 | (mp_dir) -> mp_Ntest -> stable
51
! 5 | (mp_inv) -> mp_Ntest -> stable
52
! 6 | (mp_dir,mp_inv)-> mp_Atest -> stable
53
! -1 | Special mode, see below for the negative ones.
43
! 1 | Double precision, loops reduced with propagator in original order
44
! 2 | Double precision, loops reduced with propagator with reversed order
45
! 4 | Quadruple precision, loops reduced with propagator in original order
46
! 5 | Quadruple precision, loops reduced with propagator with reversed order
47
! -1 | Exhaustive automated numerical stability checks. See below for details.
55
49
! Due to the architecture of the program, you are better off
56
50
! rerunning the full PS point in quadruple precision than just a single loop
57
51
! because the two things would almost take the same time. So '-1' is always
58
52
! very recommended.
62
56
! In the negative mode -1, MadLoop first evaluates each PS points in modes 1 and 2,
63
57
! yielding results Res1 and Res2, and then check if:
69
63
! not the case, MadLoop outputs a warning.
70
64
! Notice that MLStabThres is used only when CTModeRun is negative.
73
67
! Default :: 1.0d-3
74
68
! You can add other evaluation method to check for the stability in DP and QP.
75
69
! Below you can chose if you want to use zero, one or two rotations of the PS point
84
78
! By default, MadLoop is allowed to slightly deform the Phase-Space point in input
121
115
! Choose here the stability threshold used within CutTools to decide when to go to
122
116
! higher precision.
125
119
! Default :: 1.0d-2
127
121
! =================================================================================
128
122
! The parameters below set the general behavior of MadLoop for the initialization
129
123
! =================================================================================
131
! Decide in which mode to set CutTools when performing MadLoop's initialization of
125
! Decide in which mode to run when performing MadLoop's initialization of
132
126
! the helicity (and possibly loop) filter. The possible modes are:
134
! imode:| actions performed by ctsxcut:
136
! 0 | (dp_dir,dp_inv)-> dp_Atest -> stable -> (only if stable=.false.) ->
137
! | (mp_dir,mp_inv)-> mp_Atest -> stable
138
! 1 | (dp_dir) -> dp_Ntest -> stable
139
! 2 | (dp_inv) -> dp_Ntest -> stable
140
! 3 | (dp_dir,dp_inv)-> dp_Atest -> stable
141
! 4 | (mp_dir) -> mp_Ntest -> stable
142
! 5 | (mp_inv) -> mp_Ntest -> stable
143
! 6 | (mp_dir,mp_inv)-> mp_Atest -> stable
128
! Decide in which mode to run MadLoop
130
! imode:| description
131
! 1 | Double precision, loops reduced with propagator in original order
132
! 2 | Double precision, loops reduced with propagator with reversed order
133
! 4 | Quadruple precision, loops reduced with propagator in original order
134
! 5 | Quadruple precision, loops reduced with propagator with reversed order
149
140
! CheckCycle sets on how many PS points trials the initialization filters must be
150
141
! obtained. As long as MadLoop does not find that many consecutive PS points for
151
142
! which the filters are the same, it will start over but only a maximum of
152
143
! MaxAttempts times.
160
151
! Setting the threshold for deciding wether a numerical contribution is analytically
164
155
! Default :: 1.0d-9
166
157
! Setting the on-shell threshold for deciding whether the invariant variables
167
158
! of external momenta are on-shell or not. It will only be used in constructing
168
159
! s-matrix in Golem95.
171
162
! Default :: 1.0d-8
173
164
! The setting below is recommended to be on as it allows to systematically used the
175
166
! read from HelFilter.dat is consistent as it might be no longer up to date with
176
167
! certain changes of the paramaters by the user.
177
168
#DoubleCheckHelicityFilter
179
170
! Default :: .TRUE.
181
172
! This decides whether to write out the helicity and loop filters to the files
183
174
! preferable but sometimes not desired because of the need of threadlocks in the
184
175
! context of mpi parallelization. So it can be turned off here in such cases.
187
178
! Default :: .TRUE.
189
180
! Some loop contributions may be zero for some helicities which are however
190
181
! contributing. In order to save their computing time, you can chose here to try
191
182
! to filter them out. The gain is typically minimal, so it is turned off by default.
194
185
! Default :: .FALSE.
187
! The integer below set at which level the user wants to filter helicity configuration.
188
! Notice that this does not entail any approximation. It only offers the possibility of
189
! performing exact simplifications based on numerical checks. HelicityFilterLevel =
190
! 0 : No filtering at all. Not HelFilter.dat file will be written out and *all* helicity
191
! configurations will be computed.
192
! 1 : Analytically zero helicity configurations will be recognized as such by numerical
193
! comparisons (using the 'ZeroThres' param) and consistently skipped in further
195
! 2 : Filters both helicity configuration which are analytically zero *and* those
196
! consistently identical (typically because of CP symmetry).
197
! (Will only effectively do it if process was generated in 'optimized_mode')
196
202
! This decides whether consecutive consistency for the loop filtering setup is also
198
204
#LoopInitStartOver
200
206
! Default :: .FALSE.
202
208
! This decides wether consecutive consistency for the helicity filtering setup is also
203
209
! required. Better to set it to false as it can cause problems for unstable processes.
204
210
#HelInitStartOver
206
212
! Default :: .FALSE.
208
214
/* End of param file */
added
removed
Template/loop_material/StandAlone/Cards/MadLoopParams.dat
