Updating the Base Releases¶

We have two base releases that need to be updated after we make code changes, one is on the online DAQ cluster (novadaq-ctrl-master.fnal.gov) and the other one is on the NOvA virtual machines (novagpvm01.fnal.gov). Here is how you do it:

1. If you are updating the online DAQ cluster, make an entry in the logbook first.
2. Log into the cluster you want to update:
   

   ssh novaddt@novagpvm01.fnal.gov
   

   or
   

   ssh novadaq@novadaq-ctrl-master.fnal.gov
   

   Note: You will need to initialize a Kerberos ticket before you can connect to the repository on the DAQ cluster.
3. Set up the environment and go to the base release directory:
   

   setup_novaddt
   cd $SRT_PUBLIC_CONTEXT
   

4. Update the release:
   

   update-release 2>&1 | tee logs/update-release.log
   

   Take a look at the output and make sure everything went alright.
5. Now you are ready to build with the following command:
   

   novaddt_build 2>&1 | tee logs/debug_build.log
   

   Again, make sure to scan the build log for any errors or warning, you can also use grep for that.
6. As a final step, update the Doxygen page (virtual machines only):
   

   update_novaddt_doxygen
   

Checking Log Files¶

Here is my nifty grep command for checking the build log:

grep -i --color "arning:\|rror:" logs/debug_build.log

Prof Build¶

The above instructions are for building the base release with the "debug" flags (the standard version). However, we can also compile our code using the more optimized "prof" compilation using the setup incantations from Profile Compilation. After that, you can use this command to compile:

novaddt_build 2>&1 | tee logs/prof_build.log