Changes between Version 11 and Version 12 of Procedures/AlsprocProcessing

Timestamp:

Sep 2, 2014, 10:28:02 AM (10 years ago)

Author:

stgo

Comment:

--

Procedures/AlsprocProcessing

@@ -72 +72 @@
 Note that you can only run one of pitch/roll/heading as incrementing at present, this is to stop confusing files but could be added in if it is felt it is needed.
 
-[[Be certain about your -inc value as this can result in very large numbers of files being produced.]]
+'''Be certain about your -inc value as this can result in very large numbers of files being produced.'''
 
 You will then see a section for each flightline. process_line should be set to true for each flightline unless there was some problem, in which case the maintainer for alsproc should be contacted.
@@ -96 +96 @@
 }}}
 
-Log files will be kept for each flightline in the directory specified by log_dir in the configuration file, for your use if alsproc should suffer from some processing error.
+To specify which flightline:
+
+
+{{{
+alsproc -f 140306_130407 2013144.cfg
+}}}
+
+or to run on-grid:
+
+{{{
+alsproc_submit.py 2014238.cfg
+}}}
+
+Log files will be kept for each flightline in the directory specified by log_dir in the configuration file, for your use if alsproc should suffer from some processing error. If you are running on the grid separate log files directly from the gridnodes will be outputted as well, these can be of use when checking pre-processing errors.
 
 == Pitch and Roll Errors ==
-First you will need to generate an initial dataset to base some observations off
+Follow the instructions above using the roll/pitch/heading correct values as these will be from the boresight for the current time period. Once you have set off generation wait for the files to create. This can take a while; 20 minutes to 20 hours depending on the size of the dataset and load on the network, it will be noticeably faster on the grid. 
 
-{{{
-airborne@pmpc1322:/users/rsg/arsf/arsf_data/2013/flight_data/uk/GB13_05-2013_144_Glenmore/processing/als50# generate_alsproc_config 
-Gathering details about project...
-Using calibration file (/users/rsg/arsf/calibration/lidar/20130219/als50.cfg)...
-Collating details for .cfg file...
-Writing .cfg file
-Scanning flightline 130524_130407... ok
-Scanning flightline 130524_130807... ok
-Scanning flightline 130524_131239... ok
-Scanning flightline 130524_131711... ok
-Scanning flightline 130524_132140... ok
-Scanning flightline 130524_132606... ok
-Scanning flightline 130524_133035... ok
-Scanning flightline 130524_133540... ok
-Scanning flightline 130524_134001... ok
-Scanning flightline 130524_134447... ok
-Scanning flightline 130524_134927... ok
-Scanning flightline 130524_135443... ok
-Scanning flightline 130524_135900... ok
-Scanning flightline 130524_140340... ok
-Scanning flightline 130524_140918... ok
-Scanning flightline 130524_141340... ok
-Scanning flightline 130524_141645... ok
-Scanning flightline 130524_142158... ok
-Scanning flightline 130524_142738... ok
-all done
-}}}
+After creation is complete inspect the initial files to check for pitch (along track shifts) and roll (across track shifts) errors, it is unlikely that the boresight parameters will get you a perfect solution first time. Once you have an idea of the error you are looking at start using start/end/inc values to correct.
 
-Then edit the resulting .cfg file and set the appropriate fields. Example:
+On early iterations, you may identify just a few flightlines and focus your efforts on those, but you '''must''' check flightlines from across the entire dataset, as pitch and roll has been known to change over the course of a flight in the most unfortunate cases.
 
-{{{
-output-projection = +init=epsg:27700 +nadgrids=/users/rsg/arsf/usr/share/proj/OSTN02_NTv2.gsb +geoidgrids=/users/rsg/arsf/usr/share/proj/osgm02_wgs.gtx
-sol-file = %(project_dir)s/posatt/ipas_honeywell/proc/20130524_103914.sol
-sup-file = %(project_dir)s/posatt/ipas_honeywell/proc/20130524_103914.sup
-}}}
-
-output-projection is set according to global position. This is a UK flight so I have selected the British National Grid.
-
-
-sol-file and sup-file have been set according to what was created during the navigation processing.
-
-
-Then process the dataset. This can take a while; 20 minutes to 20 hours depending on the size of the dataset and load on the network. On early iterations, you may identify just a few flightlines and focus your efforts on those, but you '''must''' check flightlines from across the entire dataset, as pitch and roll has been known to change over the course of a flight in the most unfortunate cases.
-
-{{{
-alsproc 2013144.cfg
-}}}
-
-Then go into the dataset and look for rooftops or other features both along and across areas of overlap. It should look like this:
+The best method is to search for rooftops or other recognisable features both along and across areas of overlap using lag. It should look like this:
 
 [[Image(pitch_error_249-2012.jpg, align=center)]]