CERN Accelerating science

This website is no longer maintained. Its content may be obsolete. Please visit http://home.cern for current CERN information.

Real Time RMS prototype

[for discussion!]

As has been established, there will be a number of real-time processes in action, including real-time feed-forward of corrections based on measurements coming from the reference magnets. Inter-system dependencies, settings management, common requirements for access to various parameters strongly suggest a common approach. Indeed central control for a given class of correctors to take care of: summing trims from different inputs, field to current calculation and hysteresis loop crossing would appear to mandatory. 

The logical architecture shown below is not aimed the feedback loops themselves, but at providing common facilities for changing beam and/or magnet parameters.

 

Assumptions & Questions

Power Converters

Magnets

Beam Measurements

Possible nominal sequence for handling b3

  1. Pre-injection: The off-line MF model produces prediction of persistent current and their decay. Predicted b3 behaviour written to database. If different enough from last fill, prediction converted into time dependant corrector functions and downloaded to power converters. Possibility to incorporate empirical trims to predicted corrections established from experience.
  2. Ramp to injection level
  3. Timing event to power converters which start driving correctors with pre-loaded functions.
  4. Enable reference magnets, which feed measurements to MF-RT feed- forward process.  The latter compares with respect to reference and produces correction if necessary.
  5. Inject pilot
  6. Measure chromaticity, correct with main sextupoles.
  7. Before ramp, assuming random length at injection: call MF model to make prediction about snapback depth/b3 behaviour (and other multipoles), produce corrector functions. Stop power converters executing injection plateau functions. Load power converters with ramp functions, start ramp. MF-RT feed-forward clearly has to be kept carefully informed about reference values during this phase (if it needs to be on).

Prototype

Within agreed framework:

Data Flow

Trim Controller (e.g. b3 and feedback)