The following directories will be created:
- cd PARENT-DIR
- (where PARENT-DIR is parent for desired location of SPIDER)
- mkdir spider
- (creates a new sub-directory for SPIDER, hereafter referred to as SPIDER_DIR)
- For tape:
- tar xvf "your_tape_device" spider
- For CDROM:
- cp -r /CDROM/spider/* spider
- (assumes your CD_ROM is mounted at /CDROM)
SPIDER | processor | Irix | |
---|---|---|---|
---------- | ---------------------- | ---- | |
spider4mp | >1 R5000,R8000,R10000 | 6.2 | |
spider4 | R5000,R8000,R10000 | 6.2 | |
spider3 | R4*** | 6.2 | |
spider2 | R4*** up | 5.3 |
Sorry this is so complex but it is due to SGI's command set changes.
If you are confused which SPIDER to use I suggest you just start at the top
of the above list and use the first executable that successfully runs
on your machine. It should be optimal.
In the following commands substitute the desired SPIDER version (2, 3, 4, or 4mp) for
the "?".
Use the following commands to run SPIDER in a terminal window:
If the executable binary does not run, proceed with next step.
- cd SPIDER_DIR/bin
spider?
cd SPIDER_DIR/srcIf the executable from the above step does not run proceed with next step:
mv ../bin/spider? ../bin/spider?_orig
make -f Makefile?
cd SPIDER_DIR/srcIf the make operation fails or the new executable does not run, and you are on a SGI computer contact us at the address below.
mv spider?.a spider?_orig.a
make -f Makefile?
Notes: The archive ar command in the Makefile will
use a lot of space in your TMPDIR. If you get a message
about no space being left on your device I suggest you
redefine TMPDIR to a directory that has space (e.g.):
setenv TMPDIR /usr/tmp
We strongly advise against the use of the O3 level of
optimization on Irix 6.2+. We have encountered numerous
problems with erronous calculations!
The executables and Makefiles supplied with SPIDER use
run-time libraries. If you wish to use the static libraries
you will have to alter the Makefiles and relink.
alias spider SPIDER_DIR/bin/spider?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/binthen rename the spider? executable in SPIDER_DIR/bin to: spider.
setenv SPMAN_DIR "SPIDER_DIR/man/"You may need the following for run-time libraries if you use the spider3 or spider4:
setenv SPPROC_DIR "SPIDER_DIR/proc/"
setenv LD_LIBRARYN32_PATH=/usr/lib32:/usr/lib32/X11
cd SPIDER_DIR/binTEST #1 : Test operation 'ME'. This should give you the list of commands. (Note that all commands are listed, including those not contained in the distributed program set)
spider
.ENTER PROJECT/DATA CODE: PRJ/DAT
.OPERATION:
TEST #2 : Test arithmetic operations. These are the so-called pocket calculator functions which allow a wide range of arithmetic expressions to be computed. Expressions should be entered in the same way as FORTRAN arithmetic expressions appear in a FORTRAN source program, e.g. ((3-0.26)/4)**2. See USER.DOC for more details.
TEST#3 : Test the use of registers and document file. Execute the sequence:
X10=2The values 2 and 5 stored in the registers X10 and X20 should have been saved in DOC001.PRJ under the key 1 and subsequently unsaved into the registers X40, X50. Upon entering 'X40', the system should respond with '2.00000', and upon 'X50', it should respond with '5.00000'.
X20=5
SD 1,X10,X20
DOC001
UD 1,X40,X50
DOC001
X40
X50
TEST#4 : Test file creation. Execute the sequence:
MOThe operation 'MO' creates a test pattern (a diagonal sine wave), and 'FI' gives some info about this image.
JNK001
16,16
T
FI
JNK001
TEST#5 : Test online help. Execute thesequence:
MO ?This should give help on the "MO" command positioned at the top of the file for the first invocation and at the prompt for the type of image desired at the second invocation.
MO
JNK001
16,16
?
T
FI
JNK001
MD'MO1' refers to a file MO1.PRJ that is part of this package, containing exactly the sequence previously entered in the interactive mode, but with 'PR' added to print the image file out in the RESULTS file. The procedure sequence as well as the overprint display will be contained in results.PRJ.*, which can be printed on a line printer.
TR ON
MO1
'MD' with 'TR ON'causes all commands used within M01 to be shown on the terminal as they are executed, in this case MD, FI.
In the event that you have questions about an operation or wish
to report bugs please send us complete data on what you are trying
to do, including results files, batch files, error messages.
Send any bug reports to:
ArDean Leith
Wadsworth Labs, P.O. Box 509, Albany, New York 12201
phone: 518-486-5604
fax: 518-474-7992
email: spider@wadsworth.org