You are here: GSI Wiki>Epics Web>EpicsInstallationsAtGsi (revision 12)EditAttach

My PZ - step-by-step - EPICS installations at GSI

... on user account epics on linux sarge system

On the Linux system at GSI there are:
  • an user account epics to provide the space to store this installation, a login is practically '_never_' foreseen. (I meanwhile even forgot the password)
  • two groups:
    1. epicsadm for general installations
    2. epicsusr for user specific installations


  1. become a member of the group epicsadm in linux
    1. to check type groups on your prompt:
      yourgroup(s) ... epicsadm ...
  2. login to the group epics admin with newgrp - epicsadm (the minus is important):
    $> newgrp - epics
  3. change umask to ug+w to enable other members of epicsadm to edit all files you have created/modified:
    either each time
    1. $> umask 002 , or
    2. by adding the following lines to your ~/.profile or ~/.bashrc files.
      (The ' - ' in the newgrp command forces executing the loginscript)
      #if logged in as group epicsadm, change umask to ug+w
      if [ $(id -gn) = "epicsadm" ];
         umask 002;
  4. change to ~epics:
    $> cd ~epics
  5. Make the download directory, if not yet existing:
    $> mkdir download
-- PeterZumbruch - 27 Oct 2006

EPICS base

  1. Get the current Base of EPICS (currently, as of 22 Sep 2006, it is version from the EPICS home page an ANL and download it to the ~/download directory of the epics account.
  2. Following the corresponding README (3.14.*) (local copy) section Building EPICS base (Unix and Win32) provided in the download area, which is titled Installation Instruction, do the following:
    1. Check the supported compilers
    2. Check the software requirements
    3. unpack file to EPICS (maybe later extended to debian3.1/compilerVersion)
    4. $> cd ~epics
      $> mkdir EPICS
      $> cd EPICS
      $> tar -xvvzf ../download/<baseR*.tar.gz>
    5. Setting environment variables:
      There are at least 2 possiblities:
      1. At least EPICS_HOST_ARCH has to be defined, which can be done via:
        $> export EPICS_HOST_ARCH=_<your host's architecture>_
        where <your host's architecture> can be determined via the script EpicsHostArch (sh script) or (perl script) in the directory <epics base directory>/startup
        so that you could also write:
        $> export EPICS_HOST_ARCH=$(EpicsHostArch)
        Note in addition the other variables mentionend in the README file's section Set environment variables.
      2. The other way is to use this (bash script) which itself sources the script Site.profile
        Before downloading, make backup
        $> cd <epics base directory>/startup==
                $> cp Site.profile
                Then download to the directory ==<epics base directory>
        and then Site.profile to <epics base directory>/startup which was modified to run at GSI. And in addtion download this helper script fcn_addtopath.bash containing some functions used by the other scripts to the directory ~epics/bin (if not existent you have to create it before). has to be sourced as is, i.e. called with a leading dot
        • $> cd <epics base directory>
          $> . ./
        • with options/arguments: [-h|-v] [version=]
          • -h for help
          • -v for verbose mode
          • for another version of epics, default
          $> cd <epics base directory>
          $> . ./ -v

             EPICS_HOME               set to /u/epics/EPICS
             EPICS_BASE               set to /u/epics/EPICS/base-
             EPICS_EXTENSIONS         set to /u/epics/EPICS/extensions
             PSPRINTER                set to lp
             EPICS_DISPLAY_PATH       set to /u/epics/EPICS/extensions/medm/adl
             ORBITSCREENHOME          set to /u/epics/EPICS/extensions
             EPICS_AR_PORT            set to 7002
             added /u/epics/EPICS/extensions/javalib behind CLASSPATH
             EPICS_HOST_ARCH          set to linux-x86
             added /u/epics/EPICS/extensions/bin/linux-x86 in front of PATH
             added /u/epics/bin:/u/epics/EPICS/base- in front of PATH
             EPICS_CA_ADDR_LIST       set to lxdv18
             EPICS_CA_AUTO_ADDR_LIST  set to NO  

      3. additional variables PVT (see Site.profile):
        The following private variables ("PVTs") can be set and are if existent included in the search paths by the script Site.profile:
        • # Allow private versions of extensions with or without a bin subdir
            • optionally requieres existing: ${EPICS_EXTENSIONS_PVT}/bin/${EPICS_HOST_ARCH}
        • # Allow private versions of base
          • EPICS_BASE_PVT
            • requieres existing: ${EPICS_BASE_PVT}/bin/${EPICS_HOST_ARCH}
        Via those variables private/local versions can be supported
    6. Compilation of base
      following the instruction the README file, but using GSI make (which is GNU make) type:
      $> cd $EPICS_BASE
      $> make clean uninstall
      $> make

-- PeterZumbruch - 27 Oct 2006

Testing of base installation with

  • Section Example Application of Chapter 2, of IOC Application Developper's Guide and web docu
-- PeterZumbruch - 6 Oct 2006





  1. Download the latest dirstribution of VDCT here .
  2. Unzip the file and move the created directory to EPICS/extensions/src/ .
  3. Now you have to include the path of the VisualDCT.jar file into the CLASSPATH variable. You can also set a variable with the searchpath for .db and .dbd files, or for storing configuration data. For more information on environment variables see chapter 3 in the manual. It is brought with the distribution at vdct/2.5.1271/doc/MAN-VisualDCT_Users_Manual.html .
  4. Download here and move file to EPICS/extensions/bin/ .
  5. Installation is complete! Change directory to ??? and start VDCT with java -jar VisualDCT.jar .
-- MartinFeldmann - 30 Oct 2006






virtual Linac


  1. Download the latest Version here to the epics/download/extensions/caSnooper/ directory, which you may have to create yet.
  2. Extract epics/download/extensions/caSnooper/caSnooper2_1_1_0.tar.gz with tar -xvzf caSnooper2_1_1_0.tar.gz and move directory caSnooper/ to EPICS/extensions/src/ with the command mv.
  3. Change to directory EPICS/extensions/src/caSnooper/ and type make .
  4. Change to directory EPICS/bin/ and run caSnooper like described in the users guide at .
-- MartinFeldmann - 27 Oct 2006


  1. Download SDDS and SDDSepics under Epics/extensions/src/ in the Software Trees on to your epics/download/extensions/SDDS/ and epics/download/extensions/SDDSepics/ directorys.
  2. Extract the files with tar -xvzf FILENAME and move the corresponding directorys to EPICS/extensions/src/ .
  3. Change to EPICS/extensions/src/SDDS and type make . Do the same for SDDSepics.
  4. Change to EPICS/bin/ and run your new programs.
-- MartinFeldmann - 30 Oct 2006

Strip Tool

  1. You can download Strip Tool from here and extract it by using tar -xvzf StripToolVersion.tar .
  2. Move the resulting directory to EPICS/extensions/src/ .
  3. Before you can make Strip Tool you have to make SDDS.
  4. After making Strip Tool, you can change to EPICS/extensions/bin/ and run it by typing StripTool . For more information on configuration or environment variables, see the users guide at .
-- MartinFeldmann - 30 Oct 2006

CSS - control system suite

-- PeterZumbruch - 27 Oct 2006

Topic attachments
I Attachment Action Size Date Who CommentSorted ascending
Site.profileprofile Site.profile manage 4.1 K 2006-10-06 - 09:49 PeterZumbruch bash .profile script for setting epics environments
epicslogin.shsh manage 2.8 K 2006-10-09 - 08:50 PeterZumbruch bash script for setting epics environments
fcn_addtopath.bashbash fcn_addtopath.bash manage 1.1 K 2006-10-06 - 09:51 PeterZumbruch helper script file used in and Site.profile
Edit | Attach | Print version |  PDF | History: r191 | r13 < r12 < r11 < r10 | Backlinks | View wiki text | Edit WikiText | More topic actions...
Topic revision: r12 - 2006-10-30, MartinFeldmann
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding GSI Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)