The namelist commands are processed by subroutines from object libraries made available publicly by M. Borland.
Below, the namelist commands in clinchor are listed and grouped according to their function:
|Basic ring parameter||ringParameters|
|Cavity HOM definitions||monopoleHOMs|
|Option setup commands||randomizeHOMFrequencies|
The following pages describe all the namelist commands. For each command, one will find:
The command definition listing is of the form
&<command-name> <variable-type> <variable-name> = <default-value> . . . &endThe component <variable-type> can be one of three types:
&<command-name> [<variable-name> = <default-value>] [<array-name[<index>] = <value>,[,<value> ...],] &endThe square brackets denotes an optional component. Not all variables need to be defined - the defaults may be sufficient. Those that do need to be defined are noted in the detailed explanations. The only variables that don't have default values in general are string variables.
Array variables take a list of values with the first one assigned to the array element index. If the index value isn't given, then the namelist processor assumes the first array element is number zero. The case of the letters in all namelist and variable names is important.
One will note that quantities which aren't traditionally described in MKS units have their units appearing explicitly in their names. This convention is used to avoid confusion about which non-MKS units to use.
Whenever a namelist is read, it is written back to the standard output file, which is the screen device unless the output is redirected.
In general, the namelist commands can be repeated as many times as one wishes. The reason for repeating may be to change a variable value between calculation commands, to add more HOM definitions, or to construct a more complex bunch pattern.