SPIDER Installation on DEC UNIX

CONTENTS OF THIS DOCUMENT

1. LOADING THE DISTRIBUTION
2. INSTALLATION
3. DOCUMENTATION
4. RUNNING SPIDER
5. TESTING SPIDER
6. BUGS

1. LOADING THE DISTRIBUTION
   Code is distributed by ftp in tar format or on CD-ROM in ISO-9660 format. The distribution takes about 180 Mb of disk space but includes libraries and executables for several different systems. Only about 20Mb is necessary for a single operating system. To load SPIDER use the following commands:

   cd PARENT-DIR

   (where PARENT-DIR is parent of desired location of SPIDER)

   mkdir spider

   (creates a new sub-directory for SPIDER, hereafter referred to as SPIDER_DIR)

   From ftp delivery:

   tar xvf "ftp_filename" spider

   From CDROM:

   cp -r "your_cdrom_device"/spider/* spider

   The following directories will be created:

   Directory	Contents
   SPIDER-DIR/src	source code, SPIDER libraries
   SPIDER-DIR/bin	executables
   SPIDER-DIR/docs	documentation, html pages
   SPIDER-DIR/proc	Sample procedure files
   SPIDER-DIR/man	Operation manual pages, Nextresults
   SPIDER-DIR/pubsub	PubSub scripts & documentation

2. INSTALLATION OF SPIDER
   • Compiling and Linking the Executable.
     The SPIDER_DIR/bin directory no longer contains executable binary file. You will have to compile SPIDER on your system. SPIDER_DIR/src contains a Makefile called: Makefile_dec which compiles source code, places the object code in a library, links the object code, and creates an executable binary file. Use the following commands to compile, and link SPIDER:

     cd SPIDER_DIR/src
     make -f Makefile_dec ../bin/spider_dec
     

   • Other Installation Tasks.
     • Setting "spider" Command. You can define an alias for your SPIDER location. If you are using the 'C' shell, you would put a line similar to the following in your .cshrc startup file:

       alias spider SPIDER_DIR/bin/spider_dec
       

       Alternatively, you can modify your path so that your your system can locate the executable file when you type "spider". To alter your path add the following to the PATH environmental variable in your startup file:

       SPIDER_DIR/bin
       

       then rename the spider_dec executable in SPIDER_DIR/bin to: spider.
     • Setting environment variables.
       Set environment variables for the location of your *.sys, *.man,and "Nextresult" files. (Nextresult is a shell command file which increments the version number on the RESULTS file created by Unix SPIDER). If you are using the 'C' shell, you should put lines similar to the following in your .cshrc startup file:

       setenv SPMAN_DIR "SPIDER_DIR/man/"
       setenv SPPROC_DIR "SPIDER_DIR/proc/"
       

   • Starting SPIDER.
     

     If the executable binary does not start running and you get a error message about a missing library, then you are missing one or more run-time (shared) libraries. The current DEC SPIDER distribution requires the Fortran 90 run-time library /usr/shlib/libshpf.so@ -> /usr/lib/cmplrs/hpfrtl/libshpf.so This library is in the standard software distribution.

     If the make operation fails or the new executable does not run, contact us at the address below.

3. DOCUMENTATION
   There is an overview of SPIDER documentation in the file: documents.html in the SPIDER_DIR/docs sub-directory. All SPIDER documentation is included with the distribution and is easily accessible via your Web browser. Just point your browser at: SPIDER_DIR/docs/spider.html

   While running SPIDER you can get help on a particular operation using the online help feature of SPIDER by entering a "?" following entry of the operation code. For example, if you want help on the "MO 3" operation type: MO 3 ? at the .OPERATION prompt. Alternatively, you can look at the ASCII text file SPMAN_DIR/mo3.man.

4. RUNNING SPIDER
   
   • All SPIDER files must have a three letter extension (or datacode). This extension is automatically added by SPIDER.
   • The SPIDER "results" files are named results.ext.? where "?" is incremented for existing results file in that directory.
   • SPIDER can be run in the background or submitted as a batch using the UNIX "at" command.
5. TESTING SPIDER
   Some simple tests are available to see if SPIDER is installed correctly.
6. BUGS, SUGGESTIONS
   
   In the event that you have questions about an operation or wish to report bugs please send us complete info on what you are trying to do, including relevant results files, procedure files, and error messages.

   Send this info to:

   ArDean Leith
   Wadsworth Labs, P.O. Box 509, Albany, New York 12201
   Phone: 518-486-5604
   Fax: 518-486-2191
   Email: spider@wadsworth.org