- Quick Install
- Quick Trigger Development Install
DTC testing procedure in Rick's office¶
- with chants
- confirm that the DTC is synced with the CFO on the scope.
- check DTC lock with Polarfire demo board
- perform DCS reads
- with otsdaq
- single DCS reads stress test
- enable CFO emulation and run DCS reads stress test.
- program the DTC with the CRV firmware and connect to CRV ROC
- with chants
- confirm that the DTC is synced with the CFO on the scope
- configure with CFO emulator
- set up CRV ROC, and run the data request chant.
otsdaq quickstart instructions:¶
This code is an extension of the OTS-DAQ project and requires it to function. To setup OTS-DAQ use the instructions listed here for installing the core OTS-DAQ packages. This must be done first! Once the OTSDAQ core dependencies are set up, the mu2e otsdaq interface code can be included.
If you are one of the project managers and plan on making modifications to the code, you can checkout the repository doing the following assuming you have valid kerberos credentials,
cd $MRB_SOURCE # this is the 'srcs' directory that will be set in the course of setting up OTS-DAQ mrb gitCheckout -d otsdaq_mu2e ssh://firstname.lastname@example.org/cvs/projects/mu2e-otsdaq
Otherwise, you can just clone the directory using the http sever,
cd $MRB_SOURCE # this is the srcs directory that will be set in the course of setting up OTS-DAQ mrb gitCheckout -d otsdaq_mu2e http://cdcvs.fnal.gov/projects/mu2e-otsdaq
Alternatively, if you do not have mrb set up, you can check out the code using git directly,
git clone http://cdcvs.fnal.gov/projects/mu2e-otsdaq otsdaq_mu2e
If you don't checkout using ssh, you will not be able to push your changes to redmine.
Once the package is checked out or if you are starting a new session, source the environment,
source /path/to/products/area/setup # e.g. /data/ups/setup cd my/mrb/working/directory # this is where localProducts_otsdaq_* and srcs resides setup mrb setup git source local*/setup source mrbSetEnv
Ideally, everything that is needed for a user to run OTSDAQ will be contained in the otsdaq_mu2e directory and the code in otsdaq, otsdaq_utilities, and otsdaq_components will not need to be touched. If there is a situation where you wish to modify part of the core code, it is advised to put in a request with one of the maintainers (Lorenzo, Ryan, or Eric).
Below is a summary of some of the parts that will need to be modified in order to set up communication with the experimental device.
The FEInterface class tells OTSDAQ how to communicate with front end electronics and is found in
otsdaq_mu2e/otsdaq-mu2e/FEInterfaces/. All of the methods defined in the interface source can be called from the OTSDAQ web interface...
Configuration files are kept in
Wiki syntax Here
Instructions for setting up main version of OTSDAQ using MRB: Off-the-Shelf DAQ