Difference between revisions of "RGM RC Meeting Feb2 Feb9"
Jump to navigation
Jump to search
| Line 45: | Line 45: | ||
* 07:30 beam off for target change | * 07:30 beam off for target change | ||
| − | * '''6 GeV 90 nA on single foil Sn 0. | + | * '''6 GeV 90 nA on single foil Sn 0.37 B events, runs 15806 - 15827''' |
'''Thursday, Feb 3, DAY''' | '''Thursday, Feb 3, DAY''' | ||
| Line 56: | Line 56: | ||
* establish beam running conditions (when beamline vaccum is good) | * establish beam running conditions (when beamline vaccum is good) | ||
** scan on harp 2H01A (5nA) | ** scan on harp 2H01A (5nA) | ||
| − | ** luminosity scan, go for ~ | + | ** luminosity scan, go for ~100 nA beam current, check DC region occupancies, HV currents |
** do beam blocker calibration 6 GeV on Ca48 (later today?) | ** do beam blocker calibration 6 GeV on Ca48 (later today?) | ||
** low luminosity run (later) | ** low luminosity run (later) | ||
| − | * first and foremost: start running on 6GeV ~ | + | * first and foremost: start running on 6GeV ~100 nA on Ca48 target, beam blocker IN |
** run until SAD | ** run until SAD | ||
Revision as of 15:11, 3 February 2022
Tuesday, Feb 1, SWING
* running on LAr until 8pm * 6 GeV 25 nA on LAr 0.56 M events, runs 15289 - 15802 * empty LAr target * 1 hour empty target run, 150nA, beam blocker IN * beam blocker calibration
* insert single foil Sn (200 mg/cm2) target * beam blocker calibration for 6 GeV on single foil Sn target ** noticed that target cannot be in beam * beam line expert (Eugene) to the rescue: positions target per expert mode * from Run #15805 on: beam blocker calibration from 4 GeV run on Sn(x4) target is uploaded <-- * start running on repositioned target Sn with 90 nA, beam blocker IN ** tdcpcal3 histograms empty goes unnoticed
Wednesday, Feb 2, OWL
* continue running on Sn target with 90 nA, beam blocker IN ** some detector/DAQ issues, some beam issues ** tdcpcal3 histograms empty goes unnoticed ** BST has noisy strips with SN target and in beam *** expert: most prominent with tin target and this might be due to electrical conductivity of the foil
Wednesday Feb 2, DAY
* warming up LAr target to room temp while running * continue running on Sn target with 90 nA, beam blocker IN ** tdcpcal3 issuefixed ** more issues: HV drop pcal and ftof in sector 3, ok after turning HVs back on
* BST noisy strips: access hall to make a test with target motor off, no change
* performed beam blocker calibration with Sn target * continue running on Sn target with 90 nA, beam blocker IN
Wednesday, Feb 2, SWING
* continue running on Sn target with 90 nA, beam blocker IN * from Run#15819 on, beam blocker calibration from 6 GeV run on single foil Sn target is uploaded <-- * few issues with beam down, sector 3, RICH
Thursday, Feb 3, OWL
* continue running on Sn target with 90 nA, beam blocker IN * few issues with beam down, DC and BMT HV trips, FTOF minor HV alarms * 07:30 beam off for target change
* 6 GeV 90 nA on single foil Sn 0.37 B events, runs 15806 - 15827
Thursday, Feb 3, DAY
* Ca48 target installation, currently pumping down beam line * investigating occurrence of disabled sector trigger alarm, and other odd things
Thursday, Feb 3, SWING
* establish beam running conditions (when beamline vaccum is good) ** scan on harp 2H01A (5nA) ** luminosity scan, go for ~100 nA beam current, check DC region occupancies, HV currents ** do beam blocker calibration 6 GeV on Ca48 (later today?) ** low luminosity run (later) * first and foremost: start running on 6GeV ~100 nA on Ca48 target, beam blocker IN ** run until SAD