T9/PS run Daily Briefings - 3PM
Daily briefing minutes
August 14 - 32-1-A24
Communications | -Photon runs: completed position 1(0degree),2(30degree),3(50degree) both full brem and tagged with primary beam at 0.5,1,2.5GeV. currently taking events for position 2 in tagged mode with 1.75 gev primary beam to fully populate spectrum.
- position 4 for albedo (145 degree): tile 4 moved from top to side of cal 3; full-brem taken, 1gev primary beam tagged mode as well, 0.5 gev was too slow this morning (only 3 spills); will need to move tile 4 back to its original location prior to positron runs
|
- discussion for following photon runs: philippe request tagged mode, more configurations; energy spectrum can be sampled in a coarse way to the benefit of more configurations, as e recon studies are more sensitive to gemoetry (see bias from bill methos reported yesterday for example)
- positron setup: 1gev beam to have reasonably small beam spot and high annihilation prob; will need to build pb brick wall with a hole for the MMS target |
OfflineReport
| -philippe (CAL)
|
-berrie: photons conversion efficiency in the TKR
-claudia (TKR)
-eric (ACD) |
August 13 - 32-1-A24
Communications | beam conditions very stable over the weekend, with 4th spill available; data taken with good efficiency
|
OfflineReport | - philippe: taggged photon spectrum has a whole around 650 MeV, would be nice to fill it with 1.5 or 1.75 gev primary beam tagged photons; compared different energy recon algo for available data (not bruel methos as starts at 1gev): bill's method show a bias ranging from few to 10%; Pol method has a smaller bias but has a hard-coded limitation to 50 degress, therefore when this was realized some data were taken at 49 degrees (quicker than recompiling the code) so we have limited statistics (in the long run we just have to recompile the code and allow angle over 50).
- philippe: simulations going on to determine best impact point for position 4 (albedo): simulated 100,250,500,1000 mev photons and shooted in position 4 at each log: lower logs have more events (around 0.5%) that pass DC2 cuts for all energies, although behaviour is different for different energies; a position at around log 7 would be the best trade-off |
Program | proceed with photons at least until tomorrow afternoon, then consider proton runs for the swing and owl shift; make sure the positron setup is defined before tomorrow and be ready to prepare it on tuesday to run tuesday night
|
Notes |
|
August 12 - 32-1-A24
Communications | - running smoothly since yesterday, 2 CU positions completed at 2.5Gev, both tagged and full bream photons, 2 position completed at 1GeV tagged, currently running tagged photons at 0.5GeV with CU at 0 angle; 3rd position tagged photon by tonight, 3rd position full-brem at 2.5GeV for the owl shift. Running with 4 spills per supercycle since 1.3PM
- dump position: last night understood that 1GeV beam and 0.5GeV beam have larger divergence and some photons hit the dump; larger statistics for the 1Gev tagged photons was requested to compensate; the same was observed today with straight e in the CU, displaying a clear cut in the beam spot. The effect is larger with photons as the brem - induced divergence (scales as m/p) adds to the larger e beam divergenve. We removed the last pb brick wall from the dump, increasing the dump-beam distance to 11cm still keeping the unradiated beam within 23cm Pb (>6 moliere radii) when the magnet is ON. Online monitor with full AD + CU data proved critical to get this info in real time
- discussion for definition of 4th CU position: current agreement is to simulate albedo gammas by shooting gammas at 145 degrees in the tower 3 CAL; the impact point would be half way in the CAL, as having gammas too close to the TKR would give too poor an energy resolution, while shooting from the bottom of the CAL side would result in very few events making their way to the TKR. Philippe is concerned that we also get some tagged gammas in such configuration to cross-check the energy as the CU energy measurement would be very poor; suggestions were made to evaluate the possibility of placing the ACD tile currently on top on the side of tower 3, to be able to run background rejection cuts similar to the LAT ones. Luca to evaluate time to move ACD tile and contact Bill and Steve to check if this position is ok, or they feel other configurations should come before.
|
...
Communications | - Magnet failure: MNP17 colling system failure at 1AM stopped data taking for several hours but no damage on hardware. Physics restarted after 2 hours w/o silicon tagger for CAL calibrations. Magnet repaired in the morning
- CU cooling system changes: CU/ISC cooling coil in the ISC base plate leaked: it was emptied and is now non available, we will rely on top cooling coil as no intervention is possible; the chiller was moved closer to the ISC to minimize thermalization of coolant with ambient through thermal exchange with the zone air, now chiller more efficient; fan added to cool XY table motors. Please look at the temperature during your shift |
Online Report
| - DAQ sync studies going on
- CU: Ric investigating phasing errors |
Offline Report
| Francesco:
- pipeline nicely running
- 1st 1000 evetns in SVAC ntuple duplicated
Claudia:
- offline monitor requires script to parse rcReport info and link to MC files (Navid working on that)
- MC and CU cooprdinate systems mismatch (check with Philippe)
Dave:
- no CAL-HI triggers in last night data as fhe values were saturated
|
Program | - Complete DAQ sync studies
- perform CU timing studies to optimize TACK (timing/script vs ext trigger manual delay)
- explore beam conditions
- ACD calibrations (ideally 5gev p, if NA 5gev e)
- CAL runs with e (Benoit)
- Tagger calibration start on 29 morning |
Notes | - Fill elogbook
- Take your shifts and launch runs yourself
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="13d98c0fbf78d1cf-215d78b3-4f7a4e6c-a3fcbaa4-3b97cb353494e2f3b39f5cd7"><ac:plain-text-body><![CDATA[- rcReport has wrong table positions for runs [701-736]; the right correlation table between position and run will be circulated. Please reset runcontrol before starting a new run when you change conditions (table position, beam configuration, trigger, CU conf) | ]]></ac:plain-text-body></ac:structured-macro> |