From Hall A Wiki
Jump to: navigation, search

General Resources and Setup Instructions


  • APV User's Guide
  • APV25-S0-guide.pdf
  • NIM paper about APV25 chip (design & results)
    • Abstract: The APV25 is a 128-channel analogue pipeline chip for the readout of silicon microstrip detectors in the CMS tracker at the LHC. Each channel comprises a low noise amplifier, a 192-cell analogue pipeline and a deconvolution readout circuit. Output data are transmitted on a single differential current output via an analogue multiplexer. The chip is fabricated in a standard 0.25μm CMOS process to take advantage of the radiation tolerance, lower noise and power, and high circuit density. experimental characterisation of this circuit shows full functionality and good performance both in pre- and post-irradiation (20Mrad) conditions. The measured noise is significantly reduced compared to earlier APV versions.
  • APV25 vs DREAM by Jixie: DREAM study, RTPC12 Simulation (2014), RTPC12 Sim (2015) (Spectator Tagging Workshop, ODU)
  • APV25 test results,
  • APV DAQ (with VME) reference manual


SRS Slow Control:




Various Modules




User Notes

Other related materials

Some DAQ related generic materials

Some Important Contacts

Kondo Gnanvo, Research Scientist (UVa). Ph.D., 2001, ENST de Bretagne & Universite de Bretagne, Occidentale, France

kg6cq@Virginia.EDU or kgnanvo At 434-924-6796 151 JBL Office

Martin Purschke: Data Acquisition Coordinator of PHOENIX experiment @ BNL

GEM documentation

SRS-CODA Some tidbits

Computer info: hostname is hcvme12 and user-name is daq (For password, contact Mark, Krishna or Xinzhan)

Location of the CODA readout lists:

  • Single ROC (SRS-GEM only) mode: /home/coda/SrsDaq/linuxvme/pciti/src/rol/pciti_listSRS.crl

(GEM-SRS ROC# is 10)

  • Multi-ROC mode: /home/coda/KrishnaStuff/AdaqBackUp/linuxvmeNw2FinalWorkingCopy/pciti/src/rol/pciti_listSRS_TS.crl (GEM-SRS ROC# is 7)

Both uses some SRS-related functions from the /home/coda/SrsDaq/linuxvme/SRS/ which is prepared from the code listenSRS4CODA_funcs4lib.c sitting in the same directory.

In addition, both uses the PCI-TI related functions from /home/coda/SrsDaq/linuxvme/pciti/src/ (compiled in the same place) and make sure the pciti-driver is installed already (run ./ from /home/coda/SrsDaq/linuxvme/pciti/linux_driver as a superuser)

CODA output and how to look at it

The output from the single ROC (# 10) mode of CODA run is saved in /home/coda/SRScoda/data

The output from the multi-ROC (GEM ROC # is 7) is in another computer (ask Alex about it).

To look at the single ROC GEM data:

  • Go to /home/coda/KrishnaStuff/AdaqBackUp/Krishna/SRS/RdSRSonlyOp
  • Run codadump4Hist to make a plot of each event (compile the program as make codadum4Hist' if you need to). This program will make plots SRS data from each event (one plot from each APV data). If there is GEM signal in the event, the plots will look somewhat like these ones. Otherwise, you will see NO-GEM-signal plots like these. The output is saved in the Output directory (both in .gif, txt and ROOT format). The program also displays the .gif file at the end of it.
    • Run it as follows: ./codadump4Hist 1 ~/SRScoda/data/test_98.dat 24, where the arguments are as follows:
      • First parameter takes value of 1 if the GEM is ON, otherwise, it's 0
      • Second parameter is the name of the CODA output file (with full path) that we are looking at
      • Third input argument is the event # that we want to look at. This number should be equal to 3 or more in case of the Single-ROC coda output, because there is no SRS data in the first 2 events. For the multi-ROC coda output, this number should be 53 or more, if I remember correctly. But, for that you'll have to go to a different directory /home/coda/KrishnaStuff/AdaqBackUp/Krishna/SRS/RdMultiRocOp and run it's corresponding program codadump4Hist just as I described above. Things are different here because, the GEM ROC has been given a different number/ID (of 7) instead of 10 and also due to other differences such as the fact that the actual detector data are stored only after the 52nd event.

Krishna's Documents