CERN

LPC meeting summary 26-02-2018 - final

Minutes overview      LPC home


Minutes and Summary

Main purpose of the meeting: Discuss plans for 90m run and VdM scan. Preview of LPC topics for the LHCC meeting.

13 TeV, ß*=90m run Plans

CMS and TOTEM plans (Silvia Goy Lopez)

The aim of this run is to increase the available statistics by roughly a factor 10 over 2015, i.e to collect 8-10pb-1. Despite the use of timing detectors, the luminosity is requested to stay below 5x1031cm-2s-1 and the pile-up between 0.3 and 0.5 in order to be able to use the diagonal coincidences which has background from elastic scatterings. To achieve this, the bunch intensity should be less than 1011 protons and the normalized emittance between 1 and 2 µrad. For ß*, good sensitivity to small momentum transfers require a high ß* (90m), while for the desired luminosity it would be better to be lower. The proposal is to try with flat optics with ßy*=90m and ßx*=54m for an effective ß*~70m. This is not expected to increase the commissioning time significantly as most of the time will anyway be spend on commissioning the desqueeze.

If the emittance is low enough, machine experts think that 50ns bunch spacing instead of 100ns would be possible despite the need to keep the crossing angle small (half crossing angle<50 µrad). The proposal is then to reduce the intensity and thus pile-up rather than doubling the luminosity. It was asked why not run at double luminosity and same pile-up which would allow the data to be collected much faster. This is not possible due to trigger/DAQ limits, but it should still be feasible to save some significant amount of time (>=1 day).

The CMS pixel detector is essential for the analysis of the data. Since there is a possibility that the problems seen in this detector during 2017 will reappear in 2018,  CMS and TOTEM prefer to have the run as early as possible in the year after the TOTEM timing detectors are fully commissioned. The best options for this run seem to be week 27 or week 28.

ATLAS plans (Masaya Ishino)

ATLAS expressed interest to take data with ß*=90m, but need to have 100ns separation between the bunches in order for the ALFA readout electronics to work properly. Two non-colliding bunches per beam would be needed for background estimates and the ALFA roman pots should be within 10 sigma of the beam. Stable beam would need to be declared. It is not clear yet if AFP will be inserted.

Two physics goal were presented. A diffractive programme similar to that of CMS and TOTEM, but with a request for 4pb-1 and pile-up of 0.5 or lower. The other half of the run would be dedicated to measure the "dip" in high momentum transfer elastic collisions. For this 1pb-1 and pile-up of 0.1-0.15 would be needed. The two requests should just fit inside the time requested for CMS and TOTEM.

Since ATLAS cannot do this run with 50ns bunch spacing, while CMS and TOTEM can, and the shorter spacing could reduce the length of the run, the LPC requested ATLAS to make this an official request otherwise the beam configuration will be mostly optimised for CMS and TOTEM. This will be discussed internally in ATLAS, but ATLAS is very interested in taking useful data during this period.

VdM scan Scheduling (Christoph Schwick)

ATLAS and CMS have made conflicting requests for their VdM scan as ATLAS prefers a period without high luminosity before the scan while CMS instead prefers a high intensity period right before the scan. This was discussed in a dedicated meeting, see http://lpc.web.cern.ch/lpc-minutes/2018-02-20.htm. A compromise promosal has been made where the VdM scan programme starts right after TS1 in the following order:

The VdM optics should be the same as in 2017, but with a crossing angle at injection. In order to maximize the signal, ATLAS requests the maximal number of colliding bunches possible, subject to the needs from ALICE and LHCb.

ALICE noted that they request not to have the VdM scan April 15-23 or May 12-20 due to expert availability, but these are all dates before TS1. For the ATLAS/CMS VdM scan, ALICE would like to have about 10 colliding bunches since these very well isolated bunches (>200ns) provide the best data for their diffractive physics and total cross section measurement programme. The data collected during the LHCb scan is not sufficient for this. ALICE would like to include the ZDC for this data which would require a reduced crossing angle. LPC will check if this is possible.

For the LHCb VdM scan, they noticed in 2017 that only 5 out of their 24 bunches were stable enough to be used. These were the five bunches which collided in IP1/5 and for 2018 they therefore requests more of these. About 4-6 colliding bunches, depending on intensity,  would be needed in LHCb during the ATLAS/CMS scan in order to close the VELO and measure the beam profile.

Topics for the LHCC (Christoph Schwick)

The LPC presentation to the LHCC is based on previous presentations at Evian and Chamonix. The topics covered will be:

The heavy ion run will not be covered as not all the parameters are settled yet.

AOB

ALICE presented their request for the initial beams. They do not need any beam splashes, though they will use them if the machine needs to do them at IP2. They would like to have 1 or 2 individual bunches in the early filling schemes if this can be accommodated with no overhead. For the 3-bunch stable beam fill they would like to have four hours of data taking with stable beams declared. There are no specific requirements on the ramp-up fills, but for some of them they may run at low field strength.

LHCb has considered the option of changing crossing angle between polarities. They realized that if external crossing angles of -150 and -440 µrad could be used for DOWN and UP polarities, respectively, the effective crossing-angle would the same for the two polarities, which would be favorable. However, this should only be done if there is little overhead in doing so.

For the low-energy run, LHCb would like to take Helium SMOG data for cosmic ray physics studies during the VdM scan where stable beam can be declared. For this, a run at 1.8 TeV would be preferred over 900 GeV as at the latter energy the VELO could not be closed completely. A few colliding bunches would be needed as well and in total 3-4 hours of data with 150 bunches is requested. It might still be useful to take data with a partially closed VELO.

Witold noted that at 900 GeV, the VdM scan can be done with injection optics, while at 1.8 TeV a new optics without large ß* would need to be developed, commissioned and validated.