Versions Compared

Old Version 42

changes.mady.by.user Luca Latronico

Saved on

compared with

New Version 43

changes.mady.by.user Luca Latronico

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

T9/PS run Daily Briefings - 3PM

 
Daily briefing minutes

August 16 - 13-3-005

 Communications

- Lat-btserver crashed last night when opening a pdf file from confluence (Luca L). Lat-btserver has problems with windows manager, so please do not use it for open files that are not strictly connected to the DAQ. THe Monitor PCs now have a firefox link on the desktop that you can use to connect to the web (Johan).
Restart of btserver was fast,  but 2 mistakes affeted data until this morning:
- housekeeping was not turned ON, and only restarted this morning; data logger shows anyway normal values for T and rH
- ACD HV was not turned ON and only re-enabled today at 2PM; please alway look at ACD histograms in the online (even if they were supposed to be empty with a 90 degress beam....)
- Socket Gleam is alive (Leon, Johan, Michael)! actually helped immediately with the issue of ACD HV because we saw reconstructed tracks pointing to the ACD tiles and saw not hits in the ACD distributions, so went to the HV control and found it to be off

Online&DAQ Report


 OfflineReport


 Program

- p program completed: 10M p at 10GeV through MMS at 30 degrees on twr3; 10M p at 6GeV through MMS at 30 degrees (2.5M evts taken with ACD OFF, see above)

 Notes 


August 15 - 13-3-005

 Communications

- 1st positron annihilation program completed overnight; shooted 1M  e+ and 1M e- through MMS placed in front of ACD tiles; CU oriented at small angle to increase path length in tracker and benefit from good tracking to point tracks to MMS target. Analysis will rely on ACD efficiency to reject e+. Target placement done using a pb brick to shadow the beam and then replacing the brick with the MMS target
- switched to p this morning; MMS target placed between the beam and the CU, shooting beam in 2 positions: small angle through twr3 towards twr2, 90 degrees entering twr3; will collect 10M p for each position at 10 and 6 gev; program will go on until tomorrow

...

 Program

see above

 Notes 

new shift list until the end available on confluence; reduced to 2 people/shift to better support analysis now that running is stable 
meet at 6PM in this meeting room for VRVS together

...

 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="1b487724a3ce6112-017e9166-4dc54750-94ee8874-f494f0169163d5fec488c387"><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>