Context Navigation

NavigationProcessing

Timestamp:: Sep 24, 2010, 11:03:17 AM (14 years ago)
Author:: knpa
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

Procedures/ProcessingChainInstructions/NavigationProcessing

-                      v4
+                      v5
 The old system was a manual system and is documented [wiki:Processing/Applanix here].  Reading this beforehand will help your understanding of how it has been automated.
 '''Warning:''' the automated system relies heavily on the standarized file system structure which means that inccorect file/folder names or locations cause undefined behaviour (although generally the system just exits if it fails to find smoething)
+'''Warning:''' the automated system relies heavily on the standardized file system structure which means that incorrect file/folder names or locations cause undefined behaviour (although generally the system just exits if it fails to find something)
 '''Warning2:''' the automated system can only read base station files in the .yyo format (ascii) you could try converting to this format if you need to process projects from outside the uk (generally have a binary base file)
 to use the automated system the project folder must be in the arsf workspace, it must contain the applanix/raw and rinex directorys as real directorys and the eagle and/or hawk directorys (can be sym linked)
 the 'win_dispatcher' script must be running on the windows box and the workspace mounted as drive W:\  (if this script is not running it must be started before continueing, see explanation further down page)
+to use the automated system the project folder must be in the arsf workspace, it must contain the applanix/raw and rinex directories as real directories and the eagle and/or hawk directories (can be sym linked)
+the 'win_dispatcher' script must be running on the windows box and the workspace mounted as drive W:\  (if this script is not running it must be started before continuing, see explanation further down page)
 …
 == win dispatcher ==
 This python script periodically checks the directorys in a specified directory for a status flag and if it finds one calls another script passing the name of the directory
+This python script periodically checks the directories in a specified directory for a status flag and if it finds one calls another script passing the name of the directory
 win_dispatcher [<search dir>][<status flag>][<script to call>]
 …
 . '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
 . 'auto.bat' just calls the other .bat files in the directory
 . '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.
+. 'combine_seperation_analyser.py' this compares the combined separation 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.
 . stage 3
 . 'gnuploter.py' this script takes the cmb files and uses them to draw graphs for the combined separation of the different versions. it also moves any files in the auto_applanix directory into the correct applanix directorys
+. 'gnuploter.py' this script takes the cmb files and uses them to draw graphs for the combined separation of the different versions. it also moves any files in the auto_applanix directory into the correct applanix directories
 …
 == checking ==
 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.
+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 POSGNSS 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.
 …
 || -kd2 [float]   ||  set KAR dual frequency distance km, default 30 km ||
 || -io ["OFF", "RELATIVE", "FREE"] || set the ionospheric model option, default "FREE" ||
 || -bn [int][int][int] ||  this applies a nudge to the xyz coordinates of the base station, this was introduced for the hyquapro tests and should not be used in normal operation as it is only suitable for the boresight little rissiginton project. if it is needed for another project see the comments in the 'cordinate_offsetter.py' script. NOTE. this is not in the python version, if you need this option you will need to use the old bash version ||
+|| -bn [int][int][int] ||  this applies a nudge to the xyz coordinates of the base station, this was introduced for the hyquapro tests and should not be used in normal operation as it is only suitable for the boresight little rissington project. if it is needed for another project see the comments in the 'cordinate_offsetter.py' script. NOTE. this is not in the python version, if you need this option you will need to use the old bash version ||
 || -blind     ||      this argument specifies that the batch file generated should preform the whole applanix chain from extraction to creation of the sbet file without user input. if absent the batch files will contain only commands up to the point where the pretty green lines are displayed. From this point the user can check the separation manually and reprocess and then produce an sbet manually. ||
 || -k [name]  ||      this specifies the kernel name used. the kernel is used in the naming of many of the output and results files produced by both the auto_applanix system and applanix itself. ||