Setup MIDAS experiment: Difference between revisions

From DaqWiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
<h2>Prepare the user account</h2>
=== Prepare the user account ===
<ul>
 
        <li>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></li>
* 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></li>
        <li>Add following text to .cshrc
* check that the account is using the /bin/tcsh shell
<pre>#!/bin/echo You must source
* make $HOME/.cshrc look like this:
<pre>
#!/bin/echo You must source


setenv LANG C
setenv LANG C
Line 12: Line 14:
setenv MIDAS_EXPTAB $HOME/online/exptab
setenv MIDAS_EXPTAB $HOME/online/exptab


setenv PATH .:$HOME/online/bin:$MIDASSYS/linux/bin:$HOME/packages/roody/bin:$ROOTSYS/bin:$PATH
# 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</pre>
#end
</pre>
</li><li>
</li><li>
<br /></li>
<br /></li>

Revision as of 10:11, 10 April 2012

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): more /etc/redhat-release
    • cd $HOME/packages
    • ln -s /triumfcs/trshare/olchansk/root/root_vNNN_VVV root, where NNN is the latest available version of ROOT ("ls -l /triumfcs/trshare/olchansk/root") and VVV is the Linux version code (RH9, FC3, SL4, etc). For example: /triumfcs/trshare/olchansk/root/root_v5.10.00_SL40
    • Check that ROOT works: "echo $ROOTSYS", "$ROOTSYS/bin/root"

    Install MIDAS

    Install ROOTANA

    Install ROODY


    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.