Changes between Version 1 and Version 2 of Procedures/ProcessingChainInstructions/NavigationProcessing

Timestamp:

Jun 30, 2010, 12:39:34 PM (14 years ago)

Author:

chrfi

Comment:

--

Procedures/ProcessingChainInstructions/NavigationProcessing

@@ -50 +50 @@
 == files created (not created during manual processing) ==
  '''before processing'''
- 1. 4 applanix control batch scripts
- 1. 4 .gnv POSGNSS config files
+ 1. 5 applanix control batch scripts
+ 1. 5 .gnv POSGNSS config files
  1. 1 auto.bat file which runs all other batch files
 
  '''after processing'''
  1. 1 'combine_seperation_bestguess_values' file which contains the values the 'combine_seperation_analyser.py' script has given each attempt and the one chosen as best
- 1. 4 sets of POSGNSS output files 
- 1. 4 sets of gnuplot data and config files
- 1. 4 png files showing the separation graphs
+ 1. 5 sets of POSGNSS output files 
+ 1. 5 sets of gnuplot data and config files
+ 1. 5 png files showing the separation graphs
  1. 1 sbet file from the run with the best combine separation file
 
@@ -65 +65 @@
 
  1. stage 1
-   1. 'auto_applanix_driver.sh', this script calls 'auto_applanix_batch_config_generater.py' 4 times with different arguments and then calls 'control_batch_generator'
+   1. 'auto_applanix_driver.sh', this script calls 'auto_applanix_batch_config_generater.py' 5 times with different arguments and then calls 'control_batch_generator'
    1. 'auto_applanix_batch_config_generater.py', this script dynamically collects the information from file names and contents and uses it to create the applanix batch files and POSGNSS config file. uses several python scripts to perform conversions
    1. 'control_batch_generater.py'
  1. stage 2
    1. 'win_dispatch.py' a python script that should be constantly running on the windows machine. this script checks the specified directory for directorys containing a specific flag and then calls a linking script
-   1. 'auto_bob_dispatcher_link.py' this script performs all the copying to the windows box, then calls 'auto.bat' script, then copys everything except the RAW files (to preserve the timestamps) back to the arsf workspace
+   1. 'auto_applanix_dispatcher_link.py' this script performs all the copying to the windows box, then calls 'auto.bat' script, then copys everything except the RAW files (to preserve the timestamps) back to the arsf workspace
    1. 'auto.bat' just calls the other .bat files in the directory
    1. 'combine_seperation_analyser.py' this compares the combined seperation of each of the 4 versions and attempts to select the best one, the values used for this attempt are recorded in 'combine_seperation_bestguess_values'. the script then calls the relevant versions sbet creation script. this means that only one sbet is created.
@@ -98 +98 @@
 '''command line messages'''
 
-when the scripts fail they generally attempt to convey a meaningful message to indicate the cause or point at which the error occurred. additionally in all but the hardest crashes the linux side controller auto_applanix_driver.sh will print out in which script the error occurred.
+when the scripts fail they generally attempt to convey a meaningful message to indicate the cause or point at which the error occurred. additionally in all but the hardest crashes the linux side controller auto_applanix_driver.sh will print out in which script the error occurred. These messages are printed to the command line but because the scripts are run on the grid nodes the messages are piped into a file called dispatch_summary
 
 
@@ -120 +120 @@
 == checking ==
 
-if you wish to double check the results of the system you can view the separation graphs in the auto_bapplanix folder. If it is necessary the project folder can be manually copied to the windows machine and then the user need only double click on the .gnv file in the auto_applanix folder relating to the version they wish to check. This will open GNSSPOS with all the of settings that would have been used by the automated system, the user can then proceed to alter settings and manually process the flight data. 
+if you wish to double check the results of the system you can view the separation graphs in the auto_applanix folder. If it is necessary the project folder can be manually copied to the windows machine and then the user need only double click on the .gnv file in the auto_applanix folder relating to the version they wish to check. This will open GNSSPOS with all the of settings that would have been used by the automated system, the user can then proceed to alter settings and manually process the flight data. 
 
 NOTE: if you change settings and then save them this will alter the .gnv config file, this means that until the automatic system is run again from scratch the new settings will be used.