CORRECT: Orbit Correction

The CORRECT statement makes a complete closed orbit or trajectory correction using the computed values at the monitors from the Twiss table.
The CORRECT command has the following format (not all possible options included, some options are valid only for special algorithms):
CORRECT, ORBIT=myorbit,MODEL=mymodel,TARGET=mytarget,
         FLAG=ring,MODE=lsq,  
         MONERROR=integer,MONON=real,MONSCALE=real,
         PLANE=x,COND=integer,RESOUT=integer,
         CLIST=file1,MLIST=file2; 
The command CORRECT is set up with defaults which should allow a reasonable correction for most cases with a minimum of required options (see Example 1 below).

The orbit correction must always be preceded by TWISS commands which generate Twiss tables. The most recent Twiss table is assumed to contain the optical parameters and the distorted orbits.

The options used in the CORRECT command are:
Two attributes affect the printing of tables and results:





Obsolete commands or options:
ITERATE, ITERMAX             /* Done with loop feature in MAD commands */
THREADER, THRTOL, WRORBIT    /* Not part of orbit correction module */
M1LIST, M2LIST               /* Replaced by MLIST */
C1LIST, C2LIST               /* Replaced by CLIST */
GETORBIT, PUTORBIT           /* Replaced by generic TFS access */
GETKICK, PUTKICK             /* Replaced by generic TFS access */

EXAMPLES (for complete MAD input files see section on examples):

Example 1 (correct orbit in horizontal plane, taken from most recent Twiss table, using default algorithm (MICADO)):
CORRECT,PLANE=x;

Example 2 (no correction, only output of Twiss summary):
CORRECT,TWISSUM=1;

Example 3 (correct orbit in horizontal plane, corrector and monitor output on table):
CORRECT,PLANE=x,MODE=lsq,CLIST=corr.out,MLIST=mon.out;

Example 4 (correct orbit in horizontal plane, use alignment and scaling errors, 15% of orbit correctors faulty): CORRECT,PLANE=x,MONERROR=1,MONSCALE=1,MONON=0.85;




Last updated: 22.10.2008
Werner Herr 14.06.2006