HCAL Phase Scan

Run III phase scans

2023 HBHE phase scan

A QIE phase delay scan for HB and HE was taken May 1-2 2023.

Documentation

Phase scan procedure: https://github.com/gk199/QIE_PhaseScan/blob/main/QIE_Scan.md

Elogs:

Runs and fills

Fills:

  • 8695: May 1, 11:19:44 UTC - May 1, 19:19:17 UTC. Total recorded luminosity = 171.95/pb
    • Run 366873: 53.48/pb
    • Run 366874: 86.16/pb
    • Run 366876: 32.30/pb
  • 8696: May 1, 22:15:09 UTC - May 2, 09:43:23 UTC. Total recorded luminosity = 246.49/pb
    • Run 366891: 34.39/pb
    • Run 366895: 212.10/pb

Run I, Run II phase scans

Data-taking procedure

  • Step 1: Ask the cDAQ shifter to pause the run. If you do this by phone, try to keep him/her on the line.
  • Step 2: Change the phase scan delay settings.
    • Your choices are described relative to the current default (setting "0")
    • Your minimum choice is -3 ("M3", or a delay three nanoseconds shorter than the default delay settings)
    • Your maximum choice is +32 ("P32", or a delay 32 nanoseconds longer than the default delay settings)
    • You can chose any integer setting between (and including) your minimum and maximum choice
    • Once you have selected a delay setting (e.g. "P10"), enter the following commands to change the delay settings:
cd /nfshome0/eberry/PhaseScanDelays/
./change.sh P10

  • Step 3: Initialize and then configure the piggy-back RCMS configuration. The path of this configuration is:
/hcalpro/USC/HF/PhaseScanVME04

  • Step 4: Once the piggy-back RCMS configuration has configured, make sure that the RBX delays have been updated via the RBX manager hyperdaq page
  • Step 4a: Open a window to ssh to hcalutca01, where the reset script has to be run.
  • Step 4b: Run the reset script to force the uHTRs to lock to the new timing: ~hcalsw/bin/ResetAllLinkCDR.sh
  • Step 5: Only when you have confirmed that the RBX delays have been updated, ask the cDAQ shifter to resume the run
  • Step 6: Destroy the piggy-back RCMS configuration
  • Step 7: Take data in this setting (i.e. do nothing) for several minutes, watching the DQM to see if you can observe a change.

Your goal should be to minimize the time it takes to get from Step 1 to Step 6.

HF Phase Scan during 2016

Presentations

https://twiki.cern.ch/twiki/bin/view/CMS/HcalPromTaskList2016#Task_4_Study_of_2015_HF_Phase_Sc

https://twiki.cern.ch/twiki/bin/view/CMS/HcalPromTaskList2016#Task_5_2016_HF_Phase_Scan_Progra

HF Phase Scan during 2015

Phase scan of May 7, sort(s) = 900 GeV

  • collisions_timing2.pdf: analysis of run 243506-243679, HBHE and HF, V. Epshteyn, last updated, May 20, 2015</verbatim>

  • fraction of signal in HF vs phase, averaged over all HF towers, from V. Epshteyn's write-up:
    Screen_Shot_2015-05-20_at_12.59.45_PM.png</verbatim>

  • Link to main elog
  • Full collection of Lumi histograms from Olga are at
     /afs/cern.ch/user/o/odryha/public/for_Paolo/hflumi_plots/ 

Lumi Histogram Delay setting summary and notes Filename with date_time_Run(_LS) Info
zoom_cms1_integral_0507_013048_run243679_LS030.png DELAY of -3ns -- Run 243679. Pausing for LS: 21-26 and Resuming with delays set to -3ns starting with LS 26. The beam was lost at LS46. Therefore for DELAY of -3ns we have been running only for LS:26-46. zoom_cms1_integral_0507_013048_run243679_LS030.png
zoom_cms1_integral_0506_171644_run243639.png NO DELAY zoom_cms1_integral_0506_171644_run243639.png
zoom_cms1_integral_0506_223654_run243671_LS110.png DELAY of +3ns -- Run 243671, Pausing for LS: 99-105 and Resuming with delays set to +3 startin with LS 105 zoom_cms1_integral_0506_223654_run243671_LS110.png
zoom_cms1_integral_0506_210314_run243664_LS081.png DELAY of +7ns -- Run 243664, Paused for LS: 73 thru 79, Resumed starting LS 79 with the delay of +7ns zoom_cms1_integral_0506_210314_run243664_LS081.png
zoom_cms1_integral_0507_002532_run243677_LS064.png DELAY of +11ns -- Run 243677. Pausing for LS: 41-48 and Resuming with delays set to +11ns starting with LS 48. zoom_cms1_integral_0507_002532_run243677_LS064.png
zoom_cms1_integral_0506_204718_run243664_LS040.png DELAY of +15ns -- Run 243664, starting LS38 we have +15ns introduced zoom_cms1_integral_0506_204718_run243664_LS040.png
zoom_cms1_integral_0507_011318_run243677.png DELAY of +20ns -- Run 243677. Pausing for LS: 116-122 and Resuming with delays set to +20ns starting with LS 122. zoom_cms1_integral_0507_011318_run243677.png
zoom_cms1_integral_0506_213528_run243668_LS002.png DELAY of +24ns --Run 243668, ECAL had to change timing, therefore we stopped 243664!!! I've introduced the delays of +24ns and starting LS1 for 243668, we have +24ns zoom_cms1_integral_0506_213528_run243668_LS002.png
zoom_cms1_integral_0506_180943_run243639.png DELAY of +32ns( -- Edmund has set a delay of +32ns and we have taken data starting 243639, LS ~414-415 with these delays zoom_cms1_integral_0506_180943_run243639.png

Phase scan of May 21, sort(s) = 13 TeV

  • information on data taken on May 21, 2015 (r245914, 916, 920):
    Screen_Shot_2015-05-21_at_5.57.53_PM.png</verbatim>

  • Plots from online DQM showing phase shifts during R245914:

Q2TSQ23TSvsLS_HFM.png</verbatim>

HFPTimingVSls.png</verbatim>

  • HF_phase_scan.pdf: summary of May 21st HF phase scan data, V. Epshteyn, updated May 28, 2015</verbatim>

  • hf_phase_scan.xls: summary spreadsheet with channel-by-channel delay corrections by V. Epshteyn on May-21 HF Phase scan, last updated May 25, 2015</verbatim>

  • HF phase scan: 1D of delay corrections from V. Epshteyn, May 25, 2015:
    HF_phase_scan_may21_2015_1Dplot.png</verbatim>

The x-axis is the difference (in ns) between actual 50/50 position and nominal 50/50 position of the signals in HFP and HFM

  • HF phase scan: 2D plot of delay corrections from V. Epshteyn, May 25, 2015:
    HF_phase_scan_may21_2015_2Dplot.png</verbatim>

The z-axis is the difference (in ns) between actual 50/50 position and nominal 50/50 position of the signals in HFP and HFM

  • comparison between corrections extracted by Vladimir and Otman, 6ns shift is understood:
    comparison_Vladimir_Otman.png</verbatim>

more details on comparison, see write-up by vladimir

Phase scan of June 3, sort(s) = 13 TeV

  • HF_phase_scan_2.pdf: write-up from V. Epshteyn on HF Phase scan taken on June 3, 2015</verbatim>

  • comparison between HF scan on May21 (old) and on June 3(new), V. Epshteyn, June 5, 2015:
    HF_scan_june3_1D.png</verbatim>

  • comparison between HF scan on May21 (old) and on June 3(new), V. Epshteyn, June 5, 2015:
    HF_scan_June3_2D.png</verbatim>

Phase scan of July 5, sort(s) = 13 TeV

* analysis of Otman of July 5th HF phase scan:
HFTiming1D.png</verbatim>

  • analysis of Otman of July 5th HF phase scan:
    shift_depth1.png</verbatim>

  • analysis of Otman of July 5th HF phase scan:
    shift_depth2.png</verbatim>

  • V. Epshteyn, analysis of July 5 HF Phase scan:
    july5_20_30lin_ADC.png</verbatim>

  • V. Epshteyn, analysis of July 5 HF Phase scan:
    VE_july5_2Dplot.png</verbatim>

  • V. Epshteyn, analysis of July 5 HF Phase scan:
    jun14_vs_july5.png</verbatim>

Phase scan of July 11, sort(s) = 13 TeV

  • list of runs taken during July11 scan:
    runs_july11_scan.png</verbatim>

  • plots for July 11th scan, V. Epshteyn:
    July11_scan.png</verbatim>

Phase scan of July 13, sort(s) = 13 TeV

  • single run taken during July13 scan, r251638, with out best choice of 50/50:

  • HF_phase_scan_6.pdf: write-up and two critical figures from analysis of july11 and july13 scans, V. Epshteyn</verbatim>

  • write-up and two critical figures from analysis of july11 and july13 scans, V. Epshteyn:
    5050_july13_r251638.png</verbatim>

HF Phase Scan during 2010

-- Main.Pawel.de.Barbaro@cernNOSPAMPLEASE.ch - 2015-05-06

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2023-05-02 - JohnCharlesHakala
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback