1,870
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + + + + + +
Operation of CODA Run Control - Fall 2015 (view source)
Revision as of 20:46, 3 November 2015
, 20:46, 3 November 2015no edit summary
A new VME crate has been loaned to us by JLab. This is a non-VXI crate, and it came with a single CAEN V792 integrating ADC module instead of the fADC250 that we were using for tests in 2013-2014. These changes have required us to go back to the start and reconfigure a CODA daq runtime that works with the fall 2015 setup. Some things have not changed relative to what is described in [[Procedure for Operation of CODA Run Control - Fall 2013]].
A new VME crate has been loaned to us by JLab. This is a non-VXI crate, and it came with a single CAEN V792 integrating ADC module instead of the fADC250 that we were using for tests in 2013-2014. These changes have required us to go back to the start and reconfigure a CODA daq runtime that works with the fall 2015 setup. Some things have not changed relative to what is described in [[Procedure for Operation of CODA Run Control - Fall 2013]].
# the ROC is still at 137.99.19.12 (halldtrg5.phys.uconn.edu, also called guest2.phys.uconn.edu)
# the ROC is still at 137.99.19.12 (halldtrg5.phys.uconn.edu, also called guest2.phys.uconn.edu)
# the userid for running CODA is still halld (see R. Jones for pw)
# we are still running CODA version 2.6.1 (see /usr/local/coda/* for version info)
# we are still running the "micro_test" configuration in the msql database
#* one readout controller called TROC5
#* one event builder called EB5
#* one event recorder called ER5
# we are still configured to write output data to /home/halld/data which is mounted on /nfs/direct/annex2/TAGM-tests on the cluster