Changes between Initial Version and Version 1 of Procedures/AlsprocProcessing

Timestamp:

Jun 10, 2013, 5:38:29 PM (11 years ago)

Author:

besm

Comment:

--

Procedures/AlsprocProcessing

@@ +1 @@
+== Configure ==
+The configuration file is made with the generate_alsproc_config.py program. It will examine your current working directory and derive a project directory, from which it will determine the best available calibration to base your configuration file on, and populate it with information derived from your flightlines. This can take a while, as it needs to perform a cursory check on all of the raw data.
+{{{
+generate_alsproc_config.py
+}}}
+
+Example:
+{{{
+airborne@pmpc1322:/users/rsg/arsf/arsf_data/2013/flight_data/uk/RG12_09-2013_121_Wessex# ~besm/local/alsproc/scripts/generate_alsproc_config.py 
+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 130501_093511... ok
+Scanning flightline 130501_094820... ok
+Scanning flightline 130501_100234... ok
+Scanning flightline 130501_101637... ok
+Scanning flightline 130501_102953... ok
+Scanning flightline 130501_104304... ok
+Scanning flightline 130501_105631... ok
+Scanning flightline 130501_113351... ok
+Scanning flightline 130501_114825... ok
+Scanning flightline 130501_120434... ok
+Scanning flightline 130501_121952... ok
+Scanning flightline 130501_123433... ok
+Scanning flightline 130501_125655... not ok, check failed on duration
+all done
+}}}
+
+Flightlines which alsproc thinks it might not be able to process based on this check will be flagged here, as in the case of the last flightline, and not be marked to be processed.
+
+Next, edit the .cfg file created as a result. If you did not specify, it will be under processing/als50/.
+
+Fields of particular interest to you as a data processor are:
+* output-format - can normally be left as the default
+* '''projection''' - will need to be set per-flight depending on where the flight is based (TODO: VERIFY)
+* output_dir - default is probably fine, but it can be useful to change, especially when working on the pitch and roll values later
+* '''sol-file''' - change this to the location of the sol file created during navigation processing
+* '''sup-file''' - as with the sol file
+
+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.
+{{{
+[110618_090736]
+output-file = %(output_dir)s/ldr110618_090736.las
+process_line = true
+
+# GMT 09:07:52 to 09:08:39, 47.3 seconds
+start-time = 1640,551272.000006
+end-time = 1640,551319.282274
+delta-avg-diff = 0.000006667852
+scanner-fov = 18.932618
+scan-rate = 58.214212
+multi-pulse = false
+}}}
+
+
+== Generate ==
+Alsproc is fed its arguments with the wrapper script alsproc_batch.py, which also handles certain LiDAR preformatting if using las12_las.
+{{{
+alsproc_batch.py processing/als50/2013121.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.
+
+== Pitch and Roll Errors ==
+<how to prh correct>