DAQ: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
(2 intermediate revisions by one other user not shown) | |||
Line 16: | Line 16: | ||
To build all DAQ products | To build all DAQ products | ||
# define and install the art version | # define and install the art version | ||
# build and install TRACE | # build and install TRACE (depends on cetmodules) | ||
# build and install pcie_linux_kernel_module and artdaq_core (depends on art and TRACE) | # build and install pcie_linux_kernel_module and artdaq_core (depends on art and TRACE) | ||
# build and install artdaq_core_mu2e (depends on artdaq_core and pcie) | # build and install artdaq_core_mu2e (depends on artdaq_core and pcie) | ||
If installing TRACE and other products without a new art version, the cetmodules product may need updated from scisoft to build TRACE. | |||
===artdaq_core=== | ===artdaq_core=== | ||
Line 34: | Line 36: | ||
# Environment | # Environment | ||
mu2einit | |||
export CETPKG_INSTALL=~/products # where to install new products .upsfiles needs to be there | export CETPKG_INSTALL=~/products # where to install new products .upsfiles needs to be there | ||
export CETPKG_J=60 # max parallelism in build | export CETPKG_J=60 # max parallelism in build |
Latest revision as of 22:30, 19 July 2024
Introduction
Products artdaq_core (from SCD, in mu manifest), mu2e_artdaq_core (from mu2e DAQ group, added to scisoft and mu2e manifest by hand), and TRACE (a timing package, from SCD and in mu manifest) are needed to read raw data, so are part of offline on cvmfs.
creating DAQ products from Eric Flumerfelt.
How to use git flow to update the mu2e_artdaq_core build if you are only changing product_deps, Feb 2018, from Eric Flumerfelt:
DAQ wiki link
build recipes
build order
To build all DAQ products
- define and install the art version
- build and install TRACE (depends on cetmodules)
- build and install pcie_linux_kernel_module and artdaq_core (depends on art and TRACE)
- build and install artdaq_core_mu2e (depends on artdaq_core and pcie)
If installing TRACE and other products without a new art version, the cetmodules product may need updated from scisoft to build TRACE.
artdaq_core
artdaq_core build instructions from Rob:
Below is how I built artdaq-core. Similarly for mu2e_artdaq-core. Writing it all out I see that it is rather long. It also requires visual inspection of output for pass/fail - so maybe mrb is worth the investment. Rob # Environment mu2einit export CETPKG_INSTALL=~/products # where to install new products .upsfiles needs to be there export CETPKG_J=60 # max parallelism in build # Make top level working directory, clone source and checkout tag mkdir artdaq-core cd artdaq-core git clone http://cdcvs.fnal.gov/projects/artdaq-core cd artdaq-core git checkout -b v1_07_08_build v1_07_08 # Make working area and setup environment cd .. mkdir build_prof cd build_prof source ../artdaq-core/ups/setup_for_development -p # -p is for prof # buildtool -i 1) After setup_for_development there is a ton of output. There should be no errors between the lines: ----------- check this block for errors ----------------------- ———————————————————————————————— 2) A successful buildtool ends in: ------------------------------------ INFO: Stage install / package successful. ------------------------------------ 3) To make the debug build, log out, log in, follow the above but replace prof with debug in 3 places mkdir build_debug cd build_debug source ../artdaq-core/ups/setup_for_development -d # -d is for debug