Search results

• Run Meeting: August 20th, 2020
  {| class="wikitable" border="1" style="text-align:center;border-collapse:collapse" | [[Run Meeting: August 1st, 2020|1]], [[Run Meeting: August 2nd, 2020|2]], [[Run Meeting: August 3rd, 2020|3]]
  4 KB (528 words) - 22:40, 21 August 2020
• RC Meeting: September, 2020
  {| class="wikitable" border="1" style="text-align:center;border-collapse:collapse" | [[Run Meeting: August 1st, 2020|1]], [[Run Meeting: August 2nd, 2020|2]], [[Run Meeting: August 3rd, 2020|3]]
  4 KB (511 words) - 07:09, 4 September 2020
• RC Meeting: September 10th, 2020
  {| class="wikitable" border="1" style="text-align:center;border-collapse:collapse" | [[Run Meeting: August 1st, 2020|1]], [[Run Meeting: August 2nd, 2020|2]], [[Run Meeting: August 3rd, 2020|3]]
  4 KB (535 words) - 00:53, 13 September 2020
• RGM RC Meeting Dec15 Dec22
  ** Saturday owl shift DAQ data base issue (1.3 hours no data taking) ** Monday 1:00 to 10:30 no beam
  2 KB (289 words) - 18:26, 21 December 2021
• RC Meeting: August 25th, 2020
  {| class="wikitable" border="1" style="text-align:center;border-collapse:collapse" | [[Run Meeting: August 1st, 2020|1]], [[Run Meeting: August 2nd, 2020|2]], [[Run Meeting: August 3rd, 2020|3]]
  4 KB (535 words) - 20:57, 25 August 2020
• RGM RC Meeting Dec1 Dec7
  ** 2.0 GeV vs. 1.6 GeV for BAND calibrations ** 2.0 GeV vs. 1.6 GeV for BAND calibrations
  4 KB (612 words) - 14:18, 7 December 2021
• Run Meeting: March 21st, 2020
  ...ed with the question of how to proceed since, for instance, we need to run 1-pass for calibration purposes and it could imply some changes in the accele
  1 KB (170 words) - 09:31, 21 March 2020
• Run Meeting: August 5th, 2020
  Take 1-pass inbending torus B-field data.
  958 bytes (160 words) - 14:19, 5 August 2020
• Engineering Run
  * Note 1: Be very mindful of the background rates in the halo counters, rates in the ...un/images/e/e3/Estab_beam.pdf]. Compare harp scan to the ones performed on 1/25 swing shift (https://logbooks.jlab.org/entry/3520873 and https://logbook
  15 KB (2,409 words) - 14:36, 31 January 2019
• KPP Run
  ...set FSD trip time integration times for FSD channels (1 old and 3 new) to 1 ms. Un-mask one FSD channel, run collimator with slmall steps to left or ri ...osity. Move beam in vertical direction up (or down does not matter) with 0.1 mm steps untill rates on downstream counters will be ~5kHz</del>done. x10 l
  16 KB (2,480 words) - 09:18, 21 June 2017
• Run Group D
  ...ments/Backup%20Shifters.xlsx?d=wf18dc5909cf84424840d73cc9bd8ce8e&csf=1&web=1&e=QwY1fs here]. * Run the RC meetings at 1 PM in CH Room 200C and on ZOOM, except on Wednesdays.
  30 KB (4,683 words) - 12:39, 11 December 2023
• General How-to
  ** If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values, (run wiki tab "Short Te * Keep running until the polarization uncertainty is < 1.5%
  5 KB (754 words) - 12:29, 19 January 2024
• Run Group F
  ''' Part I (Spring 2020): Beam energy 2.18 GeV (1 pass) and10.38 GeV (5 pass) '''<br> ''' Part II (Summer 2020): Beam energy 2.18 GeV (1 pass) and10.38 GeV (5 pass) '''<br>
  36 KB (5,610 words) - 14:27, 9 May 2022
• Run Group E
  1. Double Target system alignment with all solid targets successively on beam :- Beam positions at 2C24A and 2H01 must be kept within ±0.1 mm at the nominal beam positions listed under "References" at the {{#switch
  37 KB (5,661 words) - 11:52, 17 May 2024
• Run Group A
  *2H01, X: +3.0 mm, Y: -1.0 mm <b> SVT acceptable currents: </b> 1 uA
  21 KB (3,461 words) - 14:04, 16 December 2021
• Run Group K
  ...of the SLM and FCUP '''charge asymmetry''' (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert. ** PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending
  35 KB (5,399 words) - 08:32, 8 March 2024
• Run Group B
  ** (1) When you collect the gui snapshots for the logbook (scalar gui, FTC Asym p * If the trigger-time distribution or region 1 DC occupancies get worse ( > 6.5%) call the RC. What we will likely do is r
  21 KB (3,361 words) - 22:53, 29 January 2020
• Nuclear Target Test
  ** (1) When you collect the gui snapshots for the logbook (scalar gui, FTC Asym p * If the trigger-time distribution or region 1 DC occupancies get worse ( > 6.5%) call the RC. What we will likely do is r
  22 KB (3,492 words) - 01:13, 6 February 2020
• Run Group C
  ...e Faraday Cup power limit''' for the continuous operation was lifted up to 1 kW. For the remainder of the RG-C the beam blocker should not be used http <!-- *2H01, X = -1.8 mm, Y = +0.9 mm -->
  38 KB (5,783 words) - 11:27, 19 March 2023
• Run Group M
  ''' Beam energies: 2.1, 4.0, 6.0 GeV (1.96 GeV/pass) '''<br> * '''BMT''' off: histogram occupancy Z, layer 3, sector 1, detetcor 7, S1L3 strip HV is off due to high leakage, https://logbooks.jla
  25 KB (3,769 words) - 17:01, 8 February 2022

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)