cms luminosity measurement s cornell journal club n.
Skip this Video
Loading SlideShow in 5 Seconds..
CMS Luminosity Measurement(s) Cornell Journal Club PowerPoint Presentation
Download Presentation
CMS Luminosity Measurement(s) Cornell Journal Club

CMS Luminosity Measurement(s) Cornell Journal Club

91 Views Download Presentation
Download Presentation

CMS Luminosity Measurement(s) Cornell Journal Club

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. CMS Luminosity Measurement(s)Cornell Journal Club Daniel Marlow Princeton University September 30, 2005

  2. Talk Outline • Goals & General Strategy • Real time Techniques • HF • Pixel Telescopes • TAN-region Fast Ionization Chamber • Offline Techniques • Total cross section measurement (TOTEM) • W & Z Counting • Bookkeeping • Other Issues

  3. Design Goals: General Desirables • Absolute calibration, based on a known cross section with a reliably calculated acceptance. • Temporal stability against gain changes and other drifts: “countable objects” or self calibrating signals (e.g., MIP peak). • Linearity over a large range of luminosities. • Real time operation independent of full DAQ. • Redundancy • There is no perfect method • Applies to both real time monitoring and to offline absolute normalization

  4. Design Goals: Specific Issues • Real time monitoring • Bunch by bunch (yes) • Update time: 0.1 s to 1.0 s or slower • Offline • Robust logging • Easy access to luminosity records • Dynamic range (1028 ~ 1034 cm–2s–1) • Absolute Calibration • Target from previous workshops 5% (or better)

  5. General Strategy • Use TOTEM* measurement of total cross section at low luminosity as a reference point. • Use real time techniques (HF, Pixel Telescopes, FIC) to extrapolate/interpolate to design luminosity • Renormalize at design luminosity using processes of ~known cross section (e.g., W’s and Z’s) *TOTEM is a forward detector that will measure the total p-p cross section, thus providing a normalization point.

  6. Lumi Basics • Apologies to the experts! • Basic equation • We are often interested in the mean number of interactions per bunch crossing: filled BX total BX

  7. Zero Counting • If μ<<1 measuring the luminosity is straightforward, since the probability of two events in a single BX is ~μ2 . It is enough just to count hits. • For μ~1, one must either be able to distinguish between single and double interactions (not generally possible in this context), or, one must “count zeroes”

  8. Zero Counting • For μ>>1, one starts to run out of zeroes to count. There is no hard limit, but requiring at least 1% zeroes seems reasonable. This corresponds to

  9. General Strategy High L TOTEM Extrapolation of the total cross section as measured by TOTEM involves six orders of magnitude,* over which the number of min bias interactions goes from ~10-5 to ~25 per BX. Zero famine Zero feast *The extrapolation is not quite so bad, since TOTEM running will be done with fewer filled bunches.

  10. Importance of Bunch-by-Bunch Measurements • Presumably bunch-by-bunch luminosity information is of interest to the machine people. • But it may also be relevant to physics simulations. In particular, if there are significant bunch-to-bunch variations in the luminosity, then the distribution of the number of underlying interactions will no longer be Poisson.

  11. Importance of Bunch-by-Bunch Measurements • To see the effect, we consider the case where the bunch-to-bunch variations in the mean number of expected interactions is Gaussian distributed. • The cases considered range from no smearing (all bunch luminosities the same) to 50% bunch-to-bunch variations.

  12. Importance of Bunch-by-Bunch Measurements pure Poisson 10% smearing 20% smearing 50% smearing

  13. The “HF” The simulation results to be presented here will deal exclusively with the HF.

  14. HF 5mm HAD (143 cm) EM (165 cm) HF is fast and transverse shower size is small To cope with high radiation levels (>1 Grad accumulated in 10 years) the active part is Quartz fibers: the energy measured through the Cherenkov light generated by shower particles. This is the cause of two of the peculiar features of this calorimeter: The visible energy is carried by relativistic particles, i.e. electrons: the calorimeter is sensitive to the EM component (p0) of the hadronic shower. Shower size depends on Moliere radius not li The light is generated preferentially at 45 degrees: light propagation is far from ‘usual’ meridian one. • Iron calorimeter • Covers 5 > h > 3 • Total of 1728 towers, i.e. • 2 x 432 towers for EM and HAD • h x fsegmentation (0.175 x 0.175) from Greg Snow Dec. 2002

  15. Signals From HF Iron fiber calorimeter. 3 < η < 5 HF • Minimal add’l hardware requirements • Mezzanine board to tap into HF data stream and forward bits to a PC via Ethernet • Autonomous (mini) DAQ system to provide “always on” operation T1 & T2 are elements of TOTEM

  16. HF Energy Depositions The energy depositions in single interactions are typically quite sparse. • Simulation details: • PYTHIA w. diffractive events added. • DC04 (GEANT) • Extract HF depositions to Rootuple.

  17. Energy Depositions At design luminosity, there are typically 25 interactions per BX.

  18. ET Depositions Diffractive interactions Total in one endcap. Single interaction BX’s only. An ET threshold of 1 GeV will detect most interactions.

  19. HF Methods & Simulation Methods: • Count minimum bias events at low luminosity • Count “zeroes” at design luminosity • Use also linear ET sum, which scales directly with luminosity. Simulation Information: • Recent work by Chris Rogan, Princeton undergrad. • Thanks to Monika Grothe & Wisconsin group for providing MC samples with diffractive events included. • MC details • Full GEANT & ORCA • 0.25 p.e./GeV • QIE FADC scale realistically included • Thermal noise included • Tested performance over a range of assumptions

  20. HF Zero Counting • Defeat the zero famine at high luminosity by counting zeroes in a much smaller solid angle. • There are 864 HF “physical” towers. • In effect these provide 864 quasi-independent measurements of the luminosity. • Average to arrive at final result.

  21. MC Results: Physical Tower Zero Counting Zero starvation 3 FADC count hit threshold Line is determined by value at 1034 , not a fit. <N>/BX Deviation from linearity <N>/Nexpected

  22. Physical Tower Zero Counting w. Increased Threshold Thresholds ~2X previous plot <N>/BX Superlinearity typical of high thresholds <N>/Nexpected

  23. MC Results: ET Sum Method Line is determined by value at 1034 , not a fit. <ET>/BX (GeV) This is the average ET summed over the HF for each BX. Nominal noise and threshold (ADC least count effects included). Effect of noise at low luminosity. <ET>/ETexpected Deviation from linearity

  24. MC Results: ET Sum Method <ET>/BX (GeV) Noise Subtracted <ET>/ETexpected Deviation from linearity

  25. HF Luminosity Readout Path H T R H T R Global Trigger HF- R O U T E R CPU 9 HTRs/VME crate H T R H T R HF+ • 9 HTRs for HF+ and HF- • Each HTR has 1 output with luminosity info • 100Mbps raw ethernet packets sent to router • Router to computer over Gigabit ethernet • Dead time, throttle, etc. info from GCT sent to CPU • This computer will feed LHC, luminosity DB, etc. Luminosity consumers Maryland/Princeton/Virginia

  26. HF Luminosity Card TOP • Initial prototype board built. Next version due back soon. • 32MBytes of SDRAM • Virtex2PRO/VP7 has 722kbits block ram • Embedded processor • Function: • Receive data @ 40MHz from each Xilinx • Keep running sum of tower occupancy per bucket • Keep ethernet blasts in memory for transmission BOT

  27. Pixel Luminosity Telescope (PLT) • The HF method is based on an existing detector, and thus has the advantage of being inexpensive and relatively easy to implement. • It does not, however, really fit the bill when it comes to providing a luminosity measurement based on “countable objects.” • Motivated by the CDF approach of counting MIPs using Cherenkov telescopes, we are proposing a charged-particle telescope system based on single crystal diamond detectors. • This system is not yet fully funded.

  28. Pixel Luminosity Telescope (PLT) Measure luminosity bunch-by-bunch • Small angle (~1o) pointing telescopes • Three planes of diamond sensors (8 mm x 8 mm) • Diamond pixels bump bonded to CMS pixel ROC • Form 3-fold coincidence from ROC fast out signal • Located at r = 4.5 cm, z = 175 cm • Total length 20 cm Rutgers/Princeton/UC Davis • Eight telescopes per side Count 3-fold coincidences on bunch-by-bunch basis. Simple, stand alone detector, operating independently of main CMS DAQ

  29. Single Crystal (SC) CVD Diamond • Radiation hard (few x 1015 cm-2) • No need for cooling • Full charge collection at 0.2 V / m • 18,000 e― for 500 m diamond • Landau 60% narrower than Si • Availability of 8 mm x 8mm pieces • 2 pieces end of last year • 8 pieces in May • ready for production by Fall • Test performance of irradiated • diamond pixel detectors • efficiency • spatial resolution Fall Fermilab test beam • radiation hardness

  30. Polycrystalline Diamond Single Crystal: • distribution well • separated from zero Polycrystalline: crystal boundaries • wide distribution • low pulse height tail • charge spreading • over several pixels very difficult to achieve 1% stability of efficiency using polycrystaline sensors

  31. CMS Pixel Readout Chip CMS pixel chip has “fast” multiplicity counting built in active area 80 x 52 pixels 100 m x 150 m 8 mm Fast output level (each bunch crossing) • 0, 1, 2, 3,  4 double column hits • individual pixel thresholds adjustable • individual pixels can be masked 8 mm Full pixel readout (every L1 trigger) • pixel address and pulse height of each hit • diagnostic of fast out signal IP*σxy~35 μm σz~700 μm Scattering Beam halo • determination of track origin • determination of IP location *statistical accuracy on relative position assuming 1033 for 1 s

  32. Location • End of Be section of beam pipe (~ 1.7 m from IP) • Just outside of beam pipe (~ 4 cm from beam line) IP Luminosity telescopes

  33. Rates for L = 1033 Pythia 6.227 -- CMS Min. Bias productiin • interactions per BC: 2.5 • number of buckets per orbit: 3564 • filled buckets per orbit: 2835 • tracks per telescope per BC: 0.053 • tracks per array per BC: 0.84 • tracks per telescope per 1 s: 1.7 x 106 • tracks per array per 1 s: 2.7 x 107 • tracks per array per bucket per 1 s: 9500 • 1.0% statistical luminosity accuracy per bucket per 1 s @ L = 1033 • ratio of coin./tracks for 18 int. per BC: 0.81

  34. Backgrounds increase when beam pipe and CMS detector material put in Coincidences: 11% almost all coming from photons from pi0’s interacting in beam pipe Singles rate: 77% sources mostly from beam pipe some from pixel detector accidental hits per plane per interaction: 0.02 24% fakes in 3-fold coincidences @ L =1034 (assuming accidentals not correlated)

  35. Sources of Hits hadron coincidences • hadrons from physics (IP) • electrons from physics (0 photon conversions in beam pipe) • singles from IP, beam pipe, pixel detector, telescope planes electron coincidences singles

  36. 8 telescopes per side φ=0Top and Bottom of the 3rd plane reduced by 0.5mm

  37. 8 telescopes per side φ=22.5Top and Bottom of the 3rd plane reduced by 0.5mm

  38. 4 telescopes per side φ=45Top and Bottom of the 3rd plane reduced by 1mm

  39. PLT Status • The PLT is an ideal real-time luminosity monitor. • A detailed design showing the PLT to be compatible with CMS has been worked out, simulation studies are well advanced, and work on verifying the single-crystal diamonds is in progress. • The required funding of ~$300K has not been secured, but we are pursuing various avenues and remain optimistic. • The BCM mechanical mount will accommodate the PLT.

  40. LHC Luminosity Monitor TAN TAN D1 triplet TAS TAS triplet D1 L R n IP 140 m 140 m • The LHC accelerator project* plans to incorporate fast ionization counters (FICs) in the TAN region, which is ±140m from the IP. *US LARP project in particular.

  41. LHC Luminosity Monitor Instrumented Cu bar absorber to IP FIC, which is integrated with the ZDC, is located at the position of the beam septum.

  42. LHC Luminosity Monitor • Target specifications: • <0.5% relative precision • Long term stability (~1 month) for calibration with detectors • High radiation environment (100 MGy/year) • Bunch-by-bunch capability • Solution • Segmented, multi-gap, pressurized ArN2 gas ionization chamber constructed of rad-hard materials Quadrant segmentation provides sensitivity to beam position.

  43. LHC Luminosity Monitor The drift speed in the FIC is such that resolving individual bunches is an issue. The strategy being pursued consists of analog pulse shaping combined with digital deconvolution.

  44. LHC Luminosity Monitor • Project is part of LARP, a consortium of US labs participating in LHC accelerator work. • This project is led by LBL. • The current plan is to provide information to the LHC machine group. • I am in contact with the LBL people and I am working toward getting the information for incorporation into the CMS real time luminosity database.

  45. TOTEM Luminosity Independent Method Measure elastic scattering in Roman Pots and inelastic in T1 and T2 (see next slide). Should give result good to ~1% or so.

  46. Normalization Using W’s and Z’s M. Dittmar et al. • Lots of rate • Well understood theoretically • Readily detectable Basic idea is to use LHC event rates at 'nominal luminosity' CMS Trigger TDR

  47. Normalization Using W’s and Z’s • For a typical process we have • If we take as a reference process, with • The ratio does not depend on the luminosity or the pp cross section.

  48. Bookkeeping and Normalization Consider a process j, whose cross section we wish to measure where is the event yield in the final sample (background removed by cuts and fitting), is the raw number of triggers, εjis the selection efficiency (trigger plus offline), and L0 is the luminosity, uncorrected for either deadtime or prescaling. A CMS Note on this is in preparation.

  49. . . .General Considerations Note that which is the fraction of all events that pass the analysis cuts, can be determined from any unbiased sample of triggers. Note that all one needs to know is the raw number of triggers. Dead times and prescale factors do not explicitly enter (of course, one would want to know these as cross checks). A similar analysis (too complicated for a short talk) shows that multiple overlapping triggers with arbitrary prescales can also be accommodated.

  50. Technical Requirements • A hardware scaler that counts L1A’s before any prescaling or deadtime losses are applied. • We need to know the fraction of events rejected by the HLT. • This information must be “coordinated” with the scaler and luminosity information.