LD ORM

1
LDORM
Pulse width 30ns
P/V1.75
2
LED (99 base)ORB-III
P/V1.60
Pulse
HV-120V 8 PMT, AOM
FWHM
3
LED (99 base)ORB-III
P/V1.60
Pulse
HV-170V 8 PMT, AOM
FWHM
4
TWR Progress

• Now have
• SIS3300 prototype, VME RIO2 cpu, VME create, VME
  GSI trigger board (for MBS)
• On order
• 8 SIS3300, dual bank, 100 MSa/s, special
  sparsification procedure must be finalized
• Still waiting
• VME GPS interface, GPS clock, instructions

5
TWR success

• Readout of waveforms from LD and LEDs!
• Good P/V and charge resolution at 100 MSa/s gt
  no modification of front end
• Software exists for waveform averaging
• Multievent mode in both stop and start is working
  and understood
• Initialization and readout SIS3300 with shell
  script and c-program
• Readout of memory by block read is 1/30th sec
• Probably can get by with simple c-program in 02!

6
TWR Plan

• Acquire data through standalone system
• No integration with mu-DAQ readout
• Oct Develop sparsification procedure in
  collaboration with SIS, event format in memory
• Develop event building software for 8 TWR boards
• Oct Implement waveform storage in AMASIM (Hund.)
• Oct Begin MBS development (Karl-Heinz,
  Wuppertal)
• MBS system installed at UCI on both RIO2 and
  server
• MBS trigger module in house
• Crash course in sept., visit UCI in Oct.?
• Decide on event format for TRAMlinker, monitoring
  progams

7
TWR Plan (cont)

• Nov Develop synchronization options (Yuan)
• GPS stamp, but complication with multi-event
  we have no GPS clock at UCI
• GPS stamp, read out each trigger ( 1 Hz)
• Sys. Clock, but how to synch. to m-DAQ?
• GSI trigger board in both DAQ may provide
  synchronization
• Dec TRAMlinker software for merging F2000 files
• Jan Install hardware at pole (barwick)
• Attempt timing calibration, Qadc spectra for 48
  channels
• Jan merge data files into pole data management
• Dec/Jan modify monitoring software for TWR data