INSTALLATION

1. 
   

   • Executables

     The spider/bin directory should contain the following executable files (as well as others):

     SPIDER	Optimal processor	Optima byte order	"Makefile"
     spider_linux	AMD/Intel 32 (single processor)	Big endian	Makefile_linux
     spider_linux_mp_intel	AMD/Intel 32 (multiple processors)	Big endian	Makefile_linux_mp_intel
     spider_linux_mp_opt64	AMD Opteron 64 (multiple processors)	Big endian	Makefile_linux_mp_opt64
     spider_linux_mp_intel64	Intel xeon 64 (multiple processors)	Big endian	Makefile_linux_mp_intel64
     spider_linux_mpi_opt64	AMD Opteron 64 (for MPI use)	Big endian	Makefile_linux_mpi_opt64
     spider_osx_32_pgi	Intel Apple 32 bit (multiple processors)	Big endian	Makefile_osx_x32_pgi
     spider_osx_64_pgi	Intel Apple 64 bit (multiple processors)	Big endian	Makefile_osx_64_pgi

   • Setting "spider" Command and Environment variables

     You will need to tell your system the location of your executables, and other SPIDER system files. You should edit PARENT_DIR in the following lines to point to the location of the SPIDER installation on your system. Then place all of the following set of lines in your .cshrc or .bashrc startup file. (If you do not have such a startup file in your home directory you can create it with any text editor.)
     
     
     

     Using the 'C' shell:

     setenv SPIDER_DIR "PARENT_DIR/spider"
     setenv SPBIN_DIR  "$SPIDER_DIR/bin/"
     setenv SPMAN_DIR  "$SPIDER_DIR/man/"
     setenv SPPROC_DIR "$SPIDER_DIR/proc/"
     if ( $?path ) then
       set path=($path $SPBIN_DIR)
     else
       set path=($SPBIN_DIR)
     endif
     

     
     

     Using the 'bash' shell:

     export SPIDER_DIR= "PARENT_DIR/spider"
     export SPBIN_DIR=  "$SPIDER_DIR/bin/"
     export SPMAN_DIR=  "$SPIDER_DIR/man/"
     export SPPROC_DIR= "$SPIDER_DIR/proc/"
     export PATH=       "${SPIDER_DIR}/bin:${PATH}"
     

     Note: Do not use a ~username construct in the SPIDER_DIR path or SPIDER will be unable to find the Results file naming script.
     Finally rename the desired spider_linux executable in PARENT_DIR/spider/bin to: spider for easy access.

   • FFTW Libraries

     The Linux and OSX SPIDER executables are statically linked with necessary FFTW libraries. You no longer need to have shared run-time FFTW libraries on your system when using SPIDER's supplied binaries.

   • Compiling and Linking SPIDER.

     If you wish to modify SPIDER source code, link SPIDER with different libraries, or compile SPIDER with different compilation options (e.g. optimize speed for your processors) you will have to have a Fortran 95 compiler on your system. See SPIDER Compilation and Linking on Linux documentation for further information.