Difference between revisions of "RGM RC Meeting Feb2 Feb9"
Jump to navigation
Jump to search
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | '''Tuesday, Feb 1, SWING''' | |
| − | + | * running on LAr until 8pm | |
| − | * | + | |
| + | * '''6 GeV 25 nA on LAr 0.56 B events, runs 15289 - 15802''' | ||
* empty LAr target | * empty LAr target | ||
| Line 12: | Line 13: | ||
* beam line expert (Eugene) to the rescue: positions target per expert mode | * beam line expert (Eugene) to the rescue: positions target per expert mode | ||
| − | * beam blocker calibration from 4 GeV run on Sn(x4) target is uploaded | + | * 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 | * start running on repositioned target Sn with 90 nA, beam blocker IN | ||
** tdcpcal3 histograms empty goes unnoticed | ** tdcpcal3 histograms empty goes unnoticed | ||
| − | + | '''Wednesday, Feb 2, OWL''' | |
| − | |||
* continue running on Sn target with 90 nA, beam blocker IN | * continue running on Sn target with 90 nA, beam blocker IN | ||
** some detector/DAQ issues, some beam issues | ** some detector/DAQ issues, some beam issues | ||
| Line 24: | Line 24: | ||
*** expert: most prominent with tin target and this might be due to electrical conductivity of the foil | *** 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 | * warming up LAr target to room temp while running | ||
| − | * continue running on | + | * continue running on Sn target with 90 nA, beam blocker IN |
** tdcpcal3 issuefixed | ** tdcpcal3 issuefixed | ||
** more issues: HV drop pcal and ftof in sector 3, ok after turning HVs back on | ** more issues: HV drop pcal and ftof in sector 3, ok after turning HVs back on | ||
| Line 36: | Line 35: | ||
* continue running on Sn target with 90 nA, beam blocker IN | * 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 beam line vacuum 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 | ||
Latest revision as of 14:12, 3 February 2022
Tuesday, Feb 1, SWING
* running on LAr until 8pm * 6 GeV 25 nA on LAr 0.56 B 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 beam line vacuum 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