Setting up a nddaq‐v4.3.0 software area - DUNE-DAQ/daqconf GitHub Wiki

20-Dec-2023 - Work in progress (the following steps have been verified to work)

Reference links:

• general development: software development workflow, DUNE DAQ Software Style Guide
• suggested Spack commands to learn about the characteristics of an existing software area are available here
• an introduction to the "assets" system, which we use to store files that are not code, is here
• testing: NP04 computer inventory
• other: Working Group task lists, List of DUNE-DAQ GitHub teams and repos
• Tag Collector

1. create a new software area based on the candidate release build (see step 1.iv for the exact dbt-create command to use)

   1. The steps for this are based on the latest instructions for daq-buildtools

   2. As always, you should verify that your computer has access to /cvmfs/dunedaq.opensciencegrid.org

   3. If you are using one of the np04daq computers, and need to clone packages, add the following lines to your .gitconfig file (once you do this, there will be no need to activate the web proxy each time you log in, and this means that you won't forget to disable it...):

      [http]
        proxy = http://np04-web-proxy.cern.ch:3128
        sslVerify = false
      

   4. Here are the steps for creating the new software area:

      cd <directory_above_where_you_want_the_new_software_area>
      source /cvmfs/dunedaq.opensciencegrid.org/setup_dunedaq.sh
      setup_dbt latest
      dbt-create -c nddaq-v4.3.0-a9 <work_dir>  # for AL9; use nddaq-v4.3.0-c8 for SL7/CS8
      cd <work_dir>
      

   5. Please note that if you are following these instructions on a computer on which the DUNE-DAQ software has never been run before, there are several system packages that may need to be installed on that computer. These are mentioned in this script. To check whether a particular one is already installed, you can use a command like yum list libzstd and check whether the package is listed under Installed Packages.

2. add any desired repositories to the /sourcecode area. An example is provided here.

   1. clone the repositories (the following block has some extra directory checking; it can all be copy/pasted into your shell window)

      # change directory to the "sourcecode" subdir, if possible and needed
      if [[ -d "sourcecode" ]]; then
          cd sourcecode
      fi
      # double-check that we're in the correct subdir
      current_subdir=`echo ${PWD} | xargs basename`
      if [[ "$current_subdir" != "sourcecode" ]]; then
          echo ""
          echo "*** Current working directory is not \"sourcecode\", skipping repo clones"
      else
          # finally, do the repo clone(s)
          git clone https://github.com/DUNE-DAQ/lbrulibs.git -b v1.6.0
          cd ..
      fi
      
      

3. setup the work area, and build the software

   dbt-workarea-env
   dbt-build -j 20
   dbt-workarea-env
   
   

4. run a sample automated integration test

   cd sourcecode/lbrulibs/integtest
   pytest -s test_mpd-raw.py --nanorc-option partition-number 2