Setup MIDAS experiment at TRIUMF

Prepare the user account

• Setup the user account for running this instance of midas. For machines part of the LADD cluster, follow these <a href="http://daq-plone.triumf.ca/SM/docs/local/NewLaddUser">instructions</a>
• check that the account is using the /bin/tcsh shell
• make $HOME/.cshrc look like this:

#!/bin/echo You must source

setenv LANG C
setenv SVN_EDITOR "emacs -nw"
setenv CVS_RSH ssh
setenv MIDASSYS $HOME/packages/midas
setenv ROOTSYS  $HOME/packages/root
setenv MIDAS_EXPTAB $HOME/online/exptab

# setup the MIDAS mserver

switch (`hostname`)
case ladd05*:
    unsetenv MIDAS_SERVER_HOST
    breaksw
default:
    setenv MIDAS_SERVER_HOST ladd05.triumf.ca:7071
endsw

# select 64-bit or 32-bit MIDAS and ROOT

switch (`uname -i`)
case i386:
    #export ROOTSYS=/triumfcs/trshare/olchansk/root/root_v5.20.00_SL45_32
    setenv ROOTSYS /triumfcs/trshare/olchansk/root/root_v5.28.00_SL55_32
    setenv PATH .:$MIDASSYS/linux-m32/bin:$PATH
    breaksw
default:
    #export ROOTSYS=/triumfcs/trshare/olchansk/root/root_v5.26.00b_SL54_64
    #setenv ROOTSYS /triumfcs/trshare/olchansk/root/root_v5.28.00_SL55_64
    setenv ROOTSYS $HOME/packages/root
    setenv PATH .:$MIDASSYS/linux/bin:$PATH
endsw

setenv PATH .:$HOME/online/bin:$HOME/packages/roody/bin:$ROOTSYS/bin:$PATH

#end

• mkdir $HOME/packages
• Logout and login again, for .cshrc changes to take effect

Install ROOT

• Identify the Linux version: RH9 (Red Hat Linux 9), FC3 (Fedora Core 3), RHEL4/SL4 (Red Hat Enterprise LInux 4/Scientific Linux 4), SL5, SL6: more /etc/redhat-release
• Decide to use 32-bit or 64-bit ROOT
• cd $HOME/packages
• ls -l /triumfcs/trshare/olchansk/root/ ### to see all available ROOT packages
• ln -s /triumfcs/trshare/olchansk/root/root_vNNN_VVV_BB root, where NNN is the latest available version of ROOT ("ls -l /triumfcs/trshare/olchansk/root"), VVV is the Linux version code (RH9, FC3, SL4, etc) and BB is "_32" or "_64" for 32-bit or 64-bit ROOT. For example: /triumfcs/trshare/olchansk/root/root_v5.10.00_SL40
• Check that ROOT works: "echo $ROOTSYS", "$ROOTSYS/bin/root"

Install MIDAS

• cd $HOME/packages
• svn co svn+ssh://svn@savannah.psi.ch/repos/meg/midas/trunk midas, password "svn". (password has to be entered twice)
• svn co svn+ssh://svn@savannah.psi.ch/repos/meg/mxml/trunk mxml
• cd midas
• make
• (only if needed) make linux32 ### build the 32-bit MIDAS libraries
• ls -l linux/bin/odbedit ### check that odbedit has been created (do not run it yet)

Install ROOTANA

• cd $HOME/packages
• svn checkout https://ladd00.triumf.ca/svn/rootana/trunk rootana (say "p" to accept the ladd00 ssl certificate, use username "svn", password "svn")
• cd rootana
• make

Install ROODY

• cd $HOME/packages
• svn checkout https://ladd00.triumf.ca/svn/roody/trunk roody
  
• cd roody
• make
• $HOME/packages/roody/bin/roody, run the program

Install VMIC VME driver (universe-II pci/vme bridge)

• login as root (ssh root@localhost)
• get latest version of vmic driver from ladd00: scp username@ladd00:/home/olchansk/daq/vmisft-7433-NNN-KOMMM.tar.gz .
• tar xzvf vmisft-7433-3.5-KO2.tar.gz
• chown -R root.root vmisft-7433-3.5-KO2
• cd vmisft-7433-3.5-KO2
• cd vme_universe
• make
• make install
• cd ..
• make
• edit /etc/rc.local, add these lines:

  modprobe vme_universe
  mkdir -p /dev/bus/vme
  mknod /dev/bus/vme/ctl c 221 8
  chmod a+wr /dev/bus/vme/ctl

• run "modprobe vme_universe", run "lsmod" to check that the vme_universe module was loaded
• run "ls -l /dev/bus/vme/ctl" to check that the VME device file exists, it should be "crw-rw-rw- 1 root root 221, 8 Feb 17 15:47 /dev/bus/vme/ctl"

 

Install GEF VME driver (tsi148 pci/vme bridge)

• login as root (ssh root@localhost)
• yum install kernel-devel
  
• get latest version of the driver from ladd00: scp username@ladd00:/home/olchansk/daq/v7865/v7865-sdk-linux-R01.00-KONNN.tar.gz
  
• tar xzvf v7865-sdk-linux-R01.00-KO6.tar.gz
  
• chown -R root.root v7865-sdk-linux-R01.00-KO6
  
• cd v7865-sdk-linux-R01.00-KO6/gefvme/module
• make
• make install
• cd $HOME
• edit /etc/rc.local, verify that it has these 2 lines:
  

  modprobe gefvme
  sh /root/gefvme-makedevs

• run "modprobe gefvme", run "lsmod" to check that the gefvme module was loaded
• run "/home/olchansk/daq/vme/vmescan_gef.exe" to check that vme access works.