CalcHEP reference - Revision history

Hepmdb: /* nCalls_1/2 */

2014-07-10T12:34:18Z

‎nCalls_1/2

2014-07-10T12:33:16Z

‎nSess_1/2

2014-07-10T11:55:45Z

‎Parallelization

2014-07-10T11:54:52Z

‎Parallelization method

2014-07-10T11:29:19Z

‎Events

2014-07-10T11:21:58Z

‎Filename

2014-07-10T11:21:17Z

‎Number of events (per run step)

2014-07-10T11:17:20Z

‎Regularization momentum

2014-07-10T09:00:12Z

‎Kinematics

2014-07-09T16:35:43Z

‎Cuts

← Older revision		Revision as of 12:34, 10 July 2014
Line 207:		Line 207:
	=== nCalls_1/2 ===		=== nCalls_1/2 ===

−	A typical value would be 100,000.	+	This gives the number of calls in each session. A typical value would be 100,000.

@@ Line 203: / Line 203: @@
 === nSess_1/2 ===
-Normally, 5 should suffice.
+This defines the number of Vegas sessions the batch will run. Normally, 5 should suffice.
 === nCalls_1/2 ===
 A typical value would be 100,000.

@@ Line 186: / Line 186: @@
 <center><tt>sleep time: 3</tt></center>
 <center><tt>nice level :   19</tt></center>
 === Max number of cpus ===
 The maximum number of cpus depends on the computer/cluster you are about to run this batch file on. Typically, this value is 4, 8 or 12.
 === sleep time ===
 === nice level ===
 == Vegas session ==

@@ Line 169: / Line 169: @@
 == Parallelization ==
 === Parallelization method ===
 === Max number of cpus ===

← Older revision		Revision as of 11:29, 10 July 2014
Line 156:		Line 156:

	This is self-explanatory. All files produced will be given the name specified.		This is self-explanatory. All files produced will be given the name specified.
		+
		+	=== NTuple ===
		+
		+	This only works when the nt_maker has been installed in the bin directory. <tt>NTuple</tt> determines whether PAW ntuples have been created. The default is <tt>False</tt>, we recommend keeping it in this setting.
		+
		+	=== Cleanup ===
		+
		+	This determines whether the individual files will be deleted once the final event file has been created, in order to save space on the hard drive. The default setting is <tt>True</tt>. If you would like to keep the individual event files, set:
		+
		+	<center><tt>Cleanup: False</tt></center>

	== Parallelization ==		== Parallelization ==

@@ Line 155: / Line 155: @@
 === Filename ===
-This is self-explanatory.
+This is self-explanatory. All files produced will be given the name specified.
 == Parallelization ==

@@ Line 151: / Line 151: @@
 === Number of events (per run step) ===
-This is totally up to the user and what he/she wishes to calculate. Please not that this number of events are being created for each run step. If events are not needed at all, please set this to 0.
+This is totally up to the user and what they wish to calculate. Please note that this number of events are being created for each run step. The number of events can be set to zero, in which case the cross sections and distributions are determined, but no events are produced. If events are not needed, set this to 0.
 === Filename ===

@@ Line 143: / Line 143: @@
 <center><tt>Regularization width:    </tt></center>
 <center><tt>Regularization power:    </tt></center>
 == Events ==

@@ Line 131: / Line 131: @@
 <center><tt>Kinematics :      34 -> 3 , 4</tt></center>
 <center><tt>Kinematics :      56 -> 5 , 6</tt></center>
 === Regularization momentum ===

@@ Line 113: / Line 113: @@
 == Cuts ==
-=== Cut parameter ===
-=== Cut invert ===
+Cuts can be implemented on the final state particles to avoid unwanted values appearing in the calculation. In order to specify the cut of a certain value, there are four parameters that must always be present.
-=== Cut min/max ===
 == Kinematics and regularization ==