A misalignment of the beam, implemented as a zero-order matrix.
Parallel capable? : yes
GPU capable? : yes
Back-tracking capable? : yes
| Parameter Name | Units | Type | Default | Description |
| DXP | double | 0.0 | delta x’ | |
| DYP | double | 0.0 | delta y’ |
|
| DX | M | double | 0.0 | delta x |
| DY | M | double | 0.0 | delta y |
| DZ | M | double | 0.0 | delta z |
| DT | S | double | 0.0 | delta t |
| DP | double | 0.0 | delta p/pCentral |
|
| DE | double | 0.0 | delta gamma/gammaCentral |
|
| ON_PASS | long | -1 | pass on which to apply |
|
| FORCE_MODIFY_MATRIX | long | 0 | modify the matrix even if on_pass>=0 |
|
| START_PID | long | -1 | starting particleID for particles to affect. By default, all particles are affected. |
|
| END_PID | long | -1 | ending particleID for particles to affect. By default, all particles are affected. |
|
| FLOOR | long | 0 | if non-zero, floor coordinates are changed, which is probably a bad idea |
|
| GROUP | string | NULL | Optionally used to assign an element to a group, with a user-defined name. Group names will appear in the parameter output file in the column ElementGroup |
|
The default value of the PASS parameter (-1) means that the misalignment is imposed on the beam every pass. This is appropriate for static misalignments. When using the MALIGN element to kick the beam for beam dynamics studies in rings, PASS>=0 is required. If PASS=0, closed orbit computation and correction will include the effect of the kick; however, matrix-based computations by default will not (set FORCE_MODIFY_MATRIX=1 to change this). If PASS>0, then closed orbit computation and correction do not include the kick, which is probably what is desired in beam dynamics studies in rings.
MAPSOLENOID