Project

General

Profile

Installing the lbne-artdaq code

JCF, Mar-8-2017: lbne-artdaq is now obsolete. Developers for protoDUNE should ignore the instructions below, and instead proceed to the instructions on how to build and install dune-artdaq, located at https://cdcvs.fnal.gov/redmine/projects/dune-artdaq/wiki/Installing_dune-artdaq

As of Jan-10-2015, the lbne-artdaq package as well as all the packages it depends on (downloaded during the installation) take up about 6 Gb of space, and the installation procedure on Fermilab hosts takes about 5-10 minutes (this may take longer outside of Fermilab). Installation can be done in just a few simple steps:

  • Log into your system, and cd into an empty directory where you wish to install the code; for example:
    cd $HOME ; mkdir lbne-artdaq-base ; cd lbne-artdaq-base
  • Get lbne-artdaq's quick-mrb-start.sh script off the web and make it executable:
    wget https://cdcvs.fnal.gov/redmine/projects/lbne-artdaq/repository/revisions/develop/raw/tools/quick-mrb-start.sh
    chmod +x quick-mrb-start.sh
    
  • Run it with none, some, or all of the five possible options. E.g., calling it with no options
    ./quick-mrb-start.sh
    

    ...will create a "profile" build (optimized but without some of the checking of a "debug" build) of lbne-artdaq from the head of its git repository develop branch; the assumption is that you have write access to the lbne-artdaq repository. lbne-raw-data, which lbne-artdaq depends on, will be checked out as the version which lbne-artdaq at the develop head depends on, and by default will not offer write access. This would be the way you would install and build lbne-artdaq if you wanted it to run quickly (profile vs. debug build) but didn't plan to make any alterations to lbne-raw-data. Also by default, during installation the artdaq-mfextensions package and the packages artdaq-mfextensions depends on will be downloaded; this means the msgviewer application will be available and auto-detectable by DAQInterface. msgviewer requires XWindows and provides a number of features which makes looking at the lbne-artdaq simpler in real time. On the other hand, if all five possible options are chosen:
    ./quick-mrb-start.sh --debug --noviewer --lbne-raw-data-develop-branch --lbne-raw-data-developer --not-lbne-artdaq-developer
    

    ...then a debug build of lbne-artdaq is performed, artdaq-mfextensions (and consequently msgviewer) isn't installed, lbne-raw-data is installed from the head of its develop branch rather than installed as the version lbne-artdaq expects, and the user is given write access to lbne-raw-data. On the other hand, the user isn't given write access to lbne-artdaq, normally the default. The above would be an example of installing lbne-artdaq on a host where windowing isn't available and the user plans to develop lbne-raw-data but not lbne-artdaq.

In order to run lbne-artdaq, you'll want to use DAQInterface; how to get your hands on it is described at https://cdcvs.fnal.gov/redmine/projects/lbne-daq/wiki/Running_DAQ_Interface . For developers of lbne-artdaq who worked on 35ton, an important point to note is that lbne-artdaq has been switched over to an mrb build system. The advantage of this is that it's possible to modify multiple packages (in this case, lbne-artdaq and lbne-raw-data) and rebuild both of them with a single command. This will, however, require learning how to build an mrb-based system, which is actually quite simple- see https://cdcvs.fnal.gov/redmine/projects/artdaq-demo/wiki/(Re)building_the_artdaq-demo_package for how to do this. The instructions for artdaq-demo apply in the same manner to lbne-artdaq.