-
Notifications
You must be signed in to change notification settings - Fork 4
SL7 Instructions for Developers
rrivera747 edited this page Aug 21, 2024
·
1 revision
Note: we use MRB.
MRB is very useful as it allows users to update the entire dependency tree and only rebuild as needed (instead of having to rebuild the changes and then all dependent products). However, MRB does not support installing to a UPS product area, so it is most useful for development and testing, not for creating release packages and tarballs.
The quick start install script is here: https://github.com/art-daq/otsdaq/repository/demo/revisions/develop/raw/tools/quick-mrb-start.sh (https://goo.gl/rm1Ir1)
MRB: mrb:
Troubleshooting your otsdaq Installation
Making an otsdaq Release
Updating web source code documentation
yum install -y git libuuid-devel openssl-devel curl-devel #as root for basic tools
yum install -y gcc kernel-devel make #as root for compiling
yum install -y lsb #as root for lsb_release
yum install -y kde-baseapps #as root for kdialog
yum install -y python2-devel elfutils-devel
yum install -y epel-release #repository to find libzstd and xxhash
yum install -y libzstd xxhash xxhash-devel
yum install -y mesa-lib*
You should use the products saved in the fermilab cvmfs (need to be root or have sudo powers):
yum install -y https://ecsft.cern.ch/dist/cvmfs/cvmfs-release/cvmfs-release-latest.noarch.rpm
yum clean all
yum install -y cvmfs cvmfs-config-default
create the file /etc/cvmfs/default.d/70-artdaq.conf and add the lines
CVMFS_REPOSITORIES=fermilab.opensciencegrid.org
CVMFS_HTTP_PROXY=DIRECT
Then you can refresh the cvmfs configuration:
cvmfs_config setup
#Check if CernVM-FS mounts the specified repositories by:
cvmfs_config probe
If the probe fails, try to restart autofs with sudo service autofs restart.
If cvmfs is installed correctly, now you can export the PRODUCTS directory:
export PRODUCTS=/cvmfs/fermilab.opensciencegrid.org/products/artdaq/
If you can’t install the CernVM-FS, you may try to install manually the products:
mkdir
mkdir /path/to/products/area # Should be DIFFERENT than where you intend to install otsdaq (for example: otsdaqPrj/otsdaq-mrb-base for otsdaq and otsdaqPrj/products for the products)
cd /path/to/products/area # e.g. /data/ups
export PRODUCTS=$PWD
wget https://github.com/art-daq/otsdaq/repository/utilities/revisions/develop/raw/tools/ProductsUpdate.py
python ProductsUpdate.py
Otherwise… (here is the link to artdaq bundles and to ups packages )
mkdir /path/to/products/area # Should be DIFFERENT than where you intend to install otsdaq (for example: otsdaqPrj/otsdaq-mrb-base for otsdaq and otsdaqPrj/products for the products)
cd /path/to/products/area # e.g. /data/ups
export PRODUCTS=$PWD
# Match the UPS version to your machine's architecture, SLF6 or SLF7 should work. See http://scisoft.fnal.gov/scisoft/packages/ups for latest versions and architectures in the manifest subfolder.
wget http://scisoft.fnal.gov/scisoft/bundles/tools/pullProducts
chmod +x pullProducts
#go here to determine latest artdaq_demo version v#_##_##: scisoft.fnal.gov/scisoft/bundles/artdaq_demo/
#check your local products folder name for the qualifiers (e.g. ots/localProducts_otsdaq_demo_v2_01_00_e15_s64_prof ==> implies s64-e15)
./pullProducts . slf6 artdaq_demo-v#_##_## s41-e10 prof
#for example, ./pullProducts . slf7 artdaq_demo-v3_03_00 s64-e15 prof
curl http://scisoft.fnal.gov/scisoft/packages/mrb/v1_09_00/mrb-1.09.00-noarch.tar.bz2|tar -jx
#curl http://scisoft.fnal.gov/scisoft/packages/xerces_c/v3_1_4a/xerces_c-3.1.4a-sl7-x86_64-e10-prof.tar.bz2|tar -jx
curl http://scisoft.fnal.gov/scisoft/packages/xerces_c/v3_1_4a/xerces_c-3.1.4a-slf6-x86_64-e10-prof.tar.bz2|tar -jx
#curl http://scisoft.fnal.gov/scisoft/packages/cetbuildtools/v5_06_03/cetbuildtools-5.06.03-noarch.tar.bz2|tar -jx
rm -f *.bz2 *.txt
cd my/mrb/working/directory (or mkdir my/mrb/working/directory if it doesn't exist)# change to the path to your specific mrb project dir
bash
source $PRODUCTS/setup # e.g. /data/ups/setup, Products set in previous step
Base=$PWD
setup git
setup gitflow
setup mrb
#
# NOTE: You must have a UPS area that you have run ./pullProducts . slf6 artdaq-v1_13_00 s35-e10 prof (slf6 artdaq-v1_13_00 s35-e10 prof) in!
# You must also have extracted the XDAQ UPS product found in the otsdaq-demo repo to this UPS area!
# This has already been done if you are developing on rulinux03!
#
export MRB_PROJECT=otsdaq
mrb newDev -f -q s118:e26:prof #gets latest version (still have to know qualifiers)
# mrb newDev -v v2_05_02 -q s96:e19:prof #target a version
. $Base/local*/setup
cd $MRB_SOURCE
If you have write access to the repositories:
mrb gitCheckout https://github.com/art-daq/otsdaq.git
mrb gitCheckout -d otsdaq_utilities https://github.com/art-daq/otsdaq_utilities.git
mrb gitCheckout -d otsdaq_components https://github.com/art-daq/otsdaq_components.git
mrb gitCheckout -d otsdaq_demo https://github.com/art-daq/otsdaq_demo.git
Otherwise for read-only access to the repositories:
mrb gitCheckout -b develop https://github.com/art-daq/otsdaq.git
mrb gitCheckout -b develop -d otsdaq_utilities https://github.com/art-daq/otsdaq_utilities.git
mrb gitCheckout -b develop -d otsdaq_components https://github.com/art-daq/otsdaq_components.git
mrb gitCheckout -b develop -d otsdaq_demo https://github.com/art-daq/otsdaq_demo.git
# For building TRACE alongside...
#mrb svnCheckout svn+ssh://p-trace@cdcvs.fnal.gov/cvs/projects/trace-svn/trunk
#mv trunk TRACE
#sed -i 's/trunk/TRACE/g' CMakeLists.txt
#echo 'include_directories( ${CMAKE_CURRENT_SOURCE_DIR}/TRACE/include )' >>CMakeLists.txt
If you’re setting up your own products area:
# Extract the XDAQ product shipped with OTSDAQ, as well as the special version of ARTDAQ
cd $PRODUCTS
for file in $MRB_SOURCE/otsdaq_demo/tarballs/*.bz2;do tar -xf $file;done
Then:
cd $MRB_BUILDDIR
# A template setup script can be copied from the repo;
# it should work, untouched, if you installed to ~/ots/
# cp srcs/otsdaq/tools/setup_mrb.sh .
# . setup_mrb.sh
#
# If you installed somewhere different from ~/ots/ you can edit the file
# or proceed with commands manually...
source mrbSetEnv
setup nodejs v4_5_0
export CETPKG_J=8
mrb build # VERBOSE=1 <hit enter>
(Note: you can cd to any source directory)
. $Base/local*/setup
source mrbSetEnv
setup nodejs v4_5_0
mrb b
. $Base/local*/setup
source mrbSetEnv
setup nodejs v4_5_0
mrb z;source mrbSetEnv;mrb b
. $Base/local*/setup
mrb updateSource
setup nodejs v4_5_0
mrb z;source mrbSetEnv;mrb b
If you are using your own Data directory, and not the one provided
through MRB to avoid git conflicts, you must set the USER_DATA
environment variable before running.
For example, first copy the configuration provided through MRB:
cp -r /my/mrb/working/directory/srcs/otsdaq_demo/Data /my/new/config/directory/NoGitData
export USER_DATA=/full/path/to/new/config/directory/NoGitData
cd my/mrb/working/directory # change to the path to your specific mrb project dir
Base=$PWD
setup mrb # $MRB_DIR used in next setup script
. $Base/local*/setup # "base" variable used by this script and is unset; MRB_BUILDDIR, etc set.
source mrbSetEnv # add (most) BUILDDIR dirs to PATHs
# Repeat the above steps after opening a new terminal to resume development
setup nodejs v4_5_0
StartOTS.sh
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
setup nodejs v4_5_0
source local*/setup
mrb updateSource
source mrbSetEnv
export USER_DATA=/full/path/to/new/config/directory/NoGitData
#from any path
. my/mrb/working/directory/srcs/otsdaq_utilities/otsdaq-utilities/checkinAll.sh "<your comment for check-in>"
#verify push
more checkinAll.log
# Supported qualifiers: e10:s44:prof, e10:s44:debug, e10:s43:prof, e10:s43:debug, e10:s41:prof, e10:s41:debug
#setup your current/previous local products
mrb newDev -v v1_00_05 -q e10:s41:prof -f
unsetup_all
setup mrb
source localProducts_<New qualifier set>/setup
mrb z;mrbsetenv;mrb b
| Respository Tag | Description |
| otsdaq | Main repository containing the code OTSDAQ uses to manage the flow of data |
| otsdaq-demo | Contains the “user-servicable” parts, specifically the classes used to communicate with hardware. Also contains useful scripts for controlling the software. |
| otsdaq-web | The web interface used for generating project files |
| otsdaq-firmware | Pre-built firmware blocks for use on FPGA-based experiment hardware |
| otsdaq-utilities | Software components not directly related to data-taking, such as the Logbook, Chat, and Configuration GUI |
git clone https://github.com/art-daq/otsdaq.git(,-firmware,-utilities,-web,-demo)
git clone https://github.com/art-daq/otsdaq.git(,-firmware,-utilities,-web,-demo)
To check out an individual repository (for example “firmware”):
git clone https://github.com/art-daq/otsdaq.git-firmware