Changes between Version 43 and Version 44 of Procedures/EagleHawkProcessing

Timestamp:

Jul 4, 2011, 1:12:12 PM (13 years ago)

Author:

knpa

Comment:

--

Procedures/EagleHawkProcessing

@@ -6 +6 @@
 
 Before starting, make sure the [wiki:Procedures/ProcessingChainInstructions/NavigationProcessing navigation is processed] and all raw data is present and correct.
+
+Projects are located ~arsf/arsf_data/<year>/flight_data/<area>/<project>. Processing files and deliveries will be generated under <project>/processing. You should be logged in as the airborne user when doing processing.
 
 === DEM ===
@@ -47 +49 @@
 === Individual processing stages ===
 
-You shouldn't have to worry about this unless something goes wrong. However something often does! Detailed explanation of each step is explained [wiki:Procedures/AplSuiteDetails here]
+You shouldn't have to worry about this unless something goes wrong. However something often does! Detailed explanations of each step is explained [wiki:Procedures/AplSuiteDetails here]
 
 === Problems ===
@@ -60 +62 @@
 === SCTs ===
 
-The script will have produced 21 iterations of each flightline, with a range of sct values. SCT is a timing offset which affects the position and geometry of the image. Currently they range from -0.1 to 0.1 seconds. A tiff will have been produced for each version, you will need to go through these using gtviewer and find the image that looks correct, and note down the sct value. You usually determine the correct image by the amount of wobble in the image. Lines with an incorrect offset will cause kinks in straight lines such as roads where the plane trajectory wobbles. Selecting the image with the straight road is usually what is required.
+The script will have produced 21 iterations of each flightline, with a range of sct values. SCT is a timing offset which affects the position and geometry of the image. Currently they range from -0.1 to 0.1 seconds. A tiff will have been produced for each version, which will be put in <project>/processing/hyperspectral/flightlines/georeferencing/mapped. You will need to go through these using gtviewer and find the image that looks correct, and note down the sct value. You usually determine the correct image by the amount of wobble in the image. Lines with an incorrect offset will cause kinks in straight lines such as roads where the plane trajectory wobbles. Selecting the image with the straight road is usually what is required.
 
 === Create final files ===
 
-The stage that creates the geolocated tiff's that you use to find SCTs, deletes the original level 1 files after it's finished. You therefore need to use the config one more time to generate the full set of files for each flightline, using the correct SCT value. To do this, change the sctstart and sctend values so they are both the correct figure, then run again in the global section set `slow_mode = true`. Running this with specim_qsub.py will once again submit your lines to the gridnode and you should soon have all the files you require to make a delivery.
+The stage that creates the geolocated tiff's that you use to find SCTs deletes the original level 1 files after it's finished. You therefore need to use the config one more time to generate the full set of files for each flightline, using the correct SCT value. To do this, change the sctstart and sctend values so they are both the correct figure, then run again in the global section set `slow_mode = true`. Running this with specim_qsub.py will once again submit your lines to the gridnode and you should soon have all the files you require to make a delivery.
 
 === Making a delivery ===