Block 4 - Autoregister V0
 copied from working--needs to be made generic copied from working--needs to be made generic
Description
This block batch autoregisters images contained in lsupport/PICTLIST.TXT.
Assumptions
- You have invoked a Bourne-Again Shell (bash) on ormacsrv1.lpl.arizona.edu
- You are a member of the group OREX\spc
- You have set up a skeleton directory in the following format:
 /SPC_Test/F3G-Nav/
                   ORex/
                            DATA/
                   base/
                            IMAGEFILES/
                            SHAPEFILES/
                   lsupport/
                   orig/
                   results/
                   test/- You have completed the processing steps in Block 1 - Setup Directory
- You have populated the orig/ directory with test-specific images following the steps in: - Block 2 - Ingest
- ??????
 
- You have populated lsupport/PICTLIST-forRegistering.TXT with the correct subset of images to register
- You have registered images listed in lsupport/PICTLIST.TXT-forRegistering.TXT following these steps in How to Register Images - Batch
User inputs
- testID - Name of the F3 test directory (for example, 'F3E-Limbs') 
- dirID - Name of sub-directory in which to work (e.g. 'orig', or 'test') 
- blockID - User-specified identifier for typescript textfile name (for example, 'Block-03-02-Autoregister-Images-01stInvocation-F3G-GenericImages') 
Procedure
1. Initial inputs
# User inputs: testID=F3G-Nav dirID=orig blockID=Block-03-02-Autoregister-Images-01stInvocation-F3G-GenericImages
2. Set-up
# Set-Up cd /SPC_Test/$testID/$dirID/ script date pwd ls -l
3. Set-up batch autoregister files
# set-up batch autoregister files cp lsupport/PICTLIST-forRegistering.TXT make_script.in cat make_script.in cp scripts/make_scriptA.seed . cat make_scriptA.seed make_scriptA ls -l
4. Batch autoregister images
# Batch autoregister images ls -l /usr/local/bin/autoregister nohup sh run_script.b &
5. Monitor progress
# Monitor progress ls -l *.INN *.OOT
6. Check results
 how to handle variance within? how to handle variance within?
# Check results # Since early iterations are not masked - logEval picks up NO CORRS which are later eliminated sh support/logEvalP.sh cat logResults.txt cat lowImg.txt cat redo.txt convert TESTFILES/*.pgm TESTFILES/*.jpg open TESTFILES/*.jpg ## [email protected]: cp TESTFILES/*.jpg ~/send # images inspected on home-machine ## END OF VARIANCE
7. Fix uncorrelated images
# Fix uncorrelated images .......
8. Clean directory
# Clean directory sh rem_script.b rm TESTFILES/* rm nohup.out
9. Complete procedure
# Block Complete
exit
# Save block log
if [ ! -d /SPC_Test/$testID/log ]; then
  mkdir /SPC_Test/$testID/log
fi
mv typescript /SPC_Test/$testID/log/log-typescript-${blockID}
(Compiled by DL)








 You should trust both wikis because the password could be read by the particular administrators.
 You should trust both wikis because the password could be read by the particular administrators.