= Processing navigation data = This page describes the steps necessary to process navigation data, both for Eagle/Hawk data (Applanix) and for the ALS-II Lidar (IPAS). == IPAS processing == * [wiki:Processing/IPASPro] * [wiki:Processing/GrafNavProcessing] == Applanix processing == The processing of navigation data through the package of applanix programs has now been fully automated, what follows is a brief description of the new system. 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 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 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) to use the system simple place the project in the arsf workspace and add the flag 'status_applanix_batch_gen_ready' to the directory {{{ touch status_applanix_batch_gen_ready }}} == win dispatcher == 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 [][][