Summary 2/25/22

From Cuawiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

PARTICIPANTS: Brad Sawatzky, Carlos Munoz-Camacho, Carlos Yero, David Hamilton, Hamlet Mkrtchyan, Vladimir Berdnikov, Tanja Horn, Steve Wood, Paul King, Julie Roche, Rachel Montgomery


ANALYZER DISCUSSION

  • A simple Analyzer exists - getting fADC scaler data out shoul be straightforward for initial checkout
  • Decoding and getting Analyzer set up requires more work:
  • Brad can take care of the Analyzer setup and data written to disk
  • Software lead neded for the rest
  • Analyzer support for VTP payload
  • payload modifications should be straightforward
  • fADC --> VTP --> summing and triggers decisions
  • Task of the Fast Electronics Group - status: "done"
  • needs to get this going in the test setup
  • Event unblocking feature
  • lots of ideas, but not yet concrete
  • needs to be done by Hall C - B. Michaels had initially offered help - Brad will check in with him
  • SBS is not using event blocking
  • not needed when starting the NPS assembly
  • The team
  • Coordination: Brad Sawatzky
  • Software lead: David Hamilton
  • Contributors: Steve Wood, Paul King, ...


DAQ/ELECTRONICS TESTS IN SUMMER 2022

  • DAQ will be running and HV will be available
  • stack crystals - a few options
  • stack 1-2 rows, hook up, and check functionality on scope (diagui)
  • stack everything (as was done for DVCS/Hall A) since usually the electronics are bad not the crystal
  • Trigger tests
  • preload data into fADC to test how VTP is doing
  • use LEDs to simulate clusters and check if VTP is doing what it should be doing
  • cosmics to sanity check VTP
  • For cluster trigger tests a board will be provided by FEG
  • NPS readout: ~75% of full readout will be available (256 channels == 1 crate remains in HMS and is not available)
  • this only impacts signals
  • can still test all channels - just need to move cables from block to block


NPS DETECTOR CHECKOUT

  • Discussion of the list prepared by Julie
  • DAQ requirements for these tests is low
  • one question is the stacking strategy: stack everything and plut into DAQ vs. checking individually with scope
  • in DVCS/Hall A everything was stacked - smaller calorimeter, but should be ok for NPS too
  • Check gain variation with cosmics
  • better with LED as it is faster
  • can also check how LY varies with temperature as sanity check
  • Time estimate: a few months of debugging assuming all tools are available
  • Consider developing remote control features and displays
  • for HV remote control need to make sure TOSP in place and hard interlock for the box


OVERVIEW DIAGNOSTIC TOOLS AND HISTOGRAMS FROM COMCAL

  • Note: ComCAL has 12 x 12 channels
  • Diagnostic controls:
  • turn on/off LED, change frequency, change amplitude
  • HV GUI: turn on/off channels one-by-one
  • Histograms:
  • (ONLINE) rate vs. fADC channel (block)
  • (ONLINE) fADC count vs. paddle
  • (OFFLINE) cosmic event in matrix
  • (ONLINE) 2D heat map (density/occupancy plot) for scalers row vs. column
  • (ONLINE) EPICS to archive to monitor temperature
  • (ONLINE) HV adjustment - response from PMT, fit and plot
  • Note that scalers from fADC can run without decoding - other items will depend on decoding
  • Detector debugging - how to separate PMT from amplifier malfunction
  • in general, the approach (if a dead channel is observed) is the same - access to PMT and board and swap entire assembly
  • Cooling strategy on Day 0 and in the hall
  • need to watch for condensation - should not get into box
  • in ComCal assembly the AC failed for a period of time and resulted in humid conditions
  • if there is condensation one strategy could be absorbers, but these might saturate quickly
  • in the hall humidity will be controlled
  • Action items:
  • develop histograms and scaler/scaler displays (David H. and team)


DATA TAKING DURING EXPERIMENTS

  • waveform data from 5x5 grouping set around VTP determined cluster --> see page 4 in Brad's talk from 2022 Collaboration Meeting
  • HMS trigger is generated in NIM (as is done)
  • NPS trigger: VTP generates trigger based on internal logic and sends out NIM signal that will be combined with HMS (as in any third arm)
  • HMS also event blocked
  • ET
  • scaler events


NEXT MEETING: THURSDAY MARCH 10 AT 9AM ET AND EVERY TWO WEEKS AFTERWARDS