Versions Compared

Old Version 13

changes.mady.by.user Francesco Longo

Saved on

compared with

New Version 14

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

July 31 - 32-1-A24

 Communications

UPS identified and ordered (3 UPS with 900W x 7min for DAQ PCs, 1 UPS with 450W x 7 min for 28V PS); should be delivered wednesday

 Online&DAQ Report

CU DAQ maximum readout rate with full error parsing in the code is 300Hz average, corresponding to 4KHz instantenous rate during the spill (our spill structure is 3 x 0.4s spills every 16 s). This value will be checked with a random trigger generator (low threshold scintillator) and with the beam as soon as it gets back.

Ric on TEM errors: come in a variety (TKR fifo full, phasing errors, parity errors ...); some are just fake errors connected to the so-called TEM-bug in the CU TEM (which are not flight). TKR fifo full errors probably connected to beam conditions producing showers in the last si det upstream the beam and before the CU (see also offline reports), in any case the almost full flags in the GTCC buffer was changed to 0X3E from 0x32 (from E Siskind) to allow for more hits in the tracker before back-pressure events and slow readout rate. Phasing errors found in 1 run only so far, so might be connected to wrong settings - a run with beam shooting across towers should be taken to check if phase errors appear in such conditions. In summary, if we keep trigger rate below 300Hz average we should run w/o errors and be limited by the AD DAQ deadtime (820 ns)

DAQ sync: tested with external veto set to 3ms, which was set to avoid CU errors in the wrong assumption that the CU DAQ readout rate is limited to 300Hz instantaneous and not average ; need to retest it w/o such limitation and with the only veto given by the AD DAQ
|

 Offline Report

 Benoit reported on an anomalous high number of hits in run 811, but also in another run for which the si det al frame was not in the beam
Philippe reported on a strange effect in the distribution of the transverse dimension of showers in the CAL for most e runs taken for CAL calibration (700-750), indicating 2 classes of events; he also reported on a raw energy distribution with 1% of the events exceeding the beam energy
Claudia spotted an anomalous high number of tracks in the runs (700-724)
Discussion: the above analysis and the online picture of the beam on the last si det indicate that the beam line is too congested and must be cleaned; the si det will be repositioned to remove the frame from the beam, and a subset of scintillators will be used for trigger (S3 will be removed, and after the beam is well understood we might rely on Sh in anticoincidence with S2 

 Program

- CU DAQ max readout rate test with random generated pulses
- DAQ sync w/o external 3ms veto
- no beam foreseen for the night, restart shifts from tomorrow morning 8AM 

Notes 

Action items
- Luca: provide shift task list 

July 30 10.30AM - T9 barrack

- List of runs ...(Eduardo)

- Updated shift list ....(luca)

- UPS ....for DAQ PCs and CU PS (luca and gloria)

July 29 8PM - T9 barrack

- Restart of activities

...

 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="3eff0393f859e1c2-a92300e1-41324e85-948bae6c-4b50793c2e2183dd789e2481"><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>