DVCS Trigger System: Difference between revisions
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
Coordinator: Sergey Boyarinov | Coordinator: Sergey Boyarinov | ||
Leading developer: | Leading developer: Benjamin Raydo | ||
Support: Stepan, Rustam | Support: Stepan, Rustam |
Revision as of 13:07, 26 October 2007
Current section contains DVCS Calorimeter Trigger System development materials.
Coordinator: Sergey Boyarinov
Leading developer: Benjamin Raydo
Support: Stepan, Rustam
Project in progress
First approach to System Requirements (September 2007) (PowerPoint, HTML).
Ben's presentation on CLON meeting 3-Oct-2007: preliminary design.
Ben's first approach to the DVCS Cluster finding 8-Oct-2007.
Sergey, Rustam (Oct-9-2007 through Oct-16-2007):
Calibration data: 10000 events ascii file generated from dvcs_047213.A00. Pedestals were used as for the run 46595 with the beam current=20 nA (presented on this plot).
Calibration data subset: About 3200 events ascii file contains pi0 events only. That file can be considered as a sample of 'good' events, trigger system should pass all of them.
Production data: 10000 events ascii file generated from clas_047210.A01 using pedestals for run 46595. ASCII file containing all 'good' events from the same datafile (actually all events from so-called skim file egg_47210_pass1_a01.bos).
Ben's presentation on CLON meeting 10-Oct-2007: Cluster Finding.
Ben's observations on DVCS data processing 10-Oct-2007.
Ben's preliminary results on DVCS Trigger efficiency studies 11-Oct-2007.
Ben's results on DVCS Trigger efficiency studies 17-Oct-2007.
Updated System Requirements on 19-Oct-2007 (PowerPoint, HTML, pdf).
Useful documentation
CAEN V895 Discriminator Manual Revision 2, September 2002, pdf.
CAEN V1495 Logic Unit Manual Revision 4, January 2007, pdf.
V1495-related software downloaded from CAEN site on September 25, 2007 (check CAEN for newer versions !):
Our materials:
- CLAS version of V1495 Firmware Upgrade Program - CAEN version slightly modified by Sergey Boyarinov, see usage example inside; runs from VxWorks prompt