IceCube DAQ code checkout and compilation

1
IceCube DAQ code checkout and compilation

• Mark KrasbergUniversity of Wisconsin
• DOM Final Acceptance Test Training Talk
• 26 July, 2004

2
IceCube DAQ Architecture
3
IceCube DAQ code repository

• Code stored at glacier.lbl.gov
• TestDAQ currently consists of 11 software
  projects
• Code can be checked out (or committed) using
  either
• Concurrent Versioning System (CVS)
• Appropriate for maintaining individual packages
• Baseline File Development (BFD)
• Keeps track of multiple package versions which
  form a release
• You must set the environment variable CVSROOT
  correctly if you want to use CVS/BFD
• Two methods for checking out code pserver
  and ext
• A generic account can be used to check out code
  (bfd_at_glacier.lbl.gov), a user account must be
  used to check in code

4
IceCube Software Setup

• A 2-step process to set up the environment
• (two install scripts can be found at bfd.lbl.gov)
• IceCube Tools setup
• This is performed by root
• The IceCube Tools consist of standard packages
  such as ant, log4j, jython, freehep,
  jboss (not specific to IceCube)
• At PSL the IceCube Tools can be found in
  /home/icecube/tools
• BFD workspace creation
• Users must set up a directory to prepare it for
  checking out and compiling IceCube software
• a bunch of soft links are installed which point
  to the standard IceCube Tools packages

5
Checking out software

• After workspace creation you can then cd to
  your workspace directory and enter commands like
• source setup.sh
• cvs co (from the head)
• cvs update (to update
  previously checked out code for a particluar
  package)
• cvs co r V02-01-00 (to
  checkout a particular package version)
• cvs co D yesterday (to
  checkout a dated version of the package)
• cvs status v (to interrogate the
  version number of a particular file in the
  workspace)

6
Which packages do you need?

• For TestDAQ you need
• domhub-common (currently V02-00-00)
• icebucket
• domub-app (currently V02-01-00)
• daq-db-common
• daq-db-stftest
• hal
• testdaq-io
• testdaq-lightsource
• testdaq-collector
• testdaq-control
• dom-cal
• For DOMTest you also need
• domtest (currently requires an additional jar
  file to allow things to compile)
• For STF you also need
• stf (currently az-prod-0)
• stfapp (currently az-prod-0)

7
Compiling the software

• From the workspace directory you can type ant
  to compile all packages in a workspace
• this is a time-consuming but thorough way to
  compile everything
• Alternatively, enter ant lib from the head of
  each package (ant clean lib if using any
  external code).

8
An easy way to check out and compile a workspace

• Alternatively, on our domhubs, enter the commands
• createworkspace
• updateworkspace
• then select option TD, or STF
• updateworkspace is updated as necessary

9
Setting the classpath

• To run a program
• java
• The CLASSPATH must already be pointing to the jar
  files you need to run the program. If not
• java cp
• If all packages have been set up correctly you
  should only need to point your CLASSPATH at ONE
  jar file
• Packages are almost never set up properly
• Typically a CLASSPATH is 5 or 6 jar files long
  very painful to add by hand

10
Setting long classpaths

• On our DOMHubs
• source setclasspath
• This command will pick up all jar files in your
  workspace often about 30 jar files total. Then
  you are ready to go