CONVERSION OF THE PS COMPLEX AS LHC PROTON PRE-INJECTOR
Bibliographic record
Abstract
CERN’s Large Hadron Collider (LHC) [1][2] will be supplied with protons from the injector chain Linac2-PS Booster (PSB)-PS-SPS (Fig. 1). The required transverse beam brilliance (intensity/emittance) is almost twice that of current PS beams and the LHC bunch spacing of 25 ns must be impressed on the beam before its transfer to the SPS. The scheme involves new RF harmonics in the PSB and the PS, an increase of the PSB energy, and two-batch filling of the PS. After a successful test of the main ingredients, a project for converting the PS complex was launched in 1994. Major additions are (i) h=1 RF systems in the PSB, (ii) upgrading of the PSB main magnet supply from 1 to 1.4 GeV operation, (iii) new magnets, septa, power supplies, kicker pulsers for the PSB-PS beam transfer, (iv) 40 and 80 MHz systems in the PS, (v) beam profile measurement devices with improved resolution. A significant part of the effort is being provided by TRIUMF under the Canada-CERN co-operation agreement on the LHC. Fig. 1: The LHC injector complex. 1 LHC REQUIREMENTS Supplying the LHC with protons from the existing chain of injectors may appear straightforward at first sight. However, the beam has to fit into the tiny LHC dynamic aperture, and must also have the brilliance required for LHC’s desired luminosity. While the intensity is well within the capabilities of the PS complex (Linac2, PSB, PS), the beam brilliance requested (here defined as intensity per bunch/normalised rms emittance) needs to be up to twice that of current beams. LHC proton beam parameters at collision (7 TeV per beam) at various stages of operation are summarised in Table 1. Commis-sioning
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.032 | 0.019 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".