SPIDER: Testing
In the following tests, use the SPIDER
Manual,
User Guide, &
Tutorial to check on
the proper usage of commands and the expected performance of the operations.
- Start SPIDER
cd SPIDER_DIR/bin
spider
.ENTER PROJECT/DATA CODE: PRJ/DAT
.OPERATION:
-
Test arithmetic operations by
entering the following sequence:
.OPERATION: ((3-0.26)/4)**2.
SPIDER should respond: 0.46922499
- Test the use of
registers and
document files by
entering the following sequence:
.
[val]=2
[cols]=5
SD 1,[val],[cols]
DOC001
UD 1,[newval],[newcols]
DOC001
[newval]
[newcols]
The values 2 and 5 stored in the register variables [val] and [cols] should have
been saved in DOC001.PRJ under the key 1 and subsequently retrieved
into the register variables [newval] and [newcols]. Upon entering '[newval]',
SPIDER should
respond with '2.0000', and upon entering '[newcols]', it should respond with
'5.0000'.
- Test image file creation.by entering the following sequence:
MO
JNK001
16,16
T
FS
JNK001
The operation 'MO' creates a test
pattern (a diagonal sine wave) image, and
'FS' gives some info about this image.
- Test a simple procedure by
invoking a pre-existing SPIDER procedure:
@M01
'M01' refers to a procedure file
M01.spi that is part of the SPIDER distribution, which
contains the sequence previously entered in the interactive mode,
with the addition of 'MD' with 'TR ON'
added which causes all commands used within M01.PRJ to be
shown on the terminal as they are executed and
'GR' added which causes a graph of line 12 in
the output image to be printed in the RESULTS file. The RESULTS
file: results.PRJ.0, can be printed on a line printer.
In the event that you have questions
about methodologies 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.
Source: testing.html
Last update: 20 July 2020
ArDean Leith