Changes between Version 24 and Version 25 of Procedures/OwlProcessing
- Timestamp:
- Apr 15, 2016, 10:55:46 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/OwlProcessing
v24 v25 17 17 grep -rnw thermal/owl/*/capture/*.hdr -e "GPS" 18 18 19 If there are no GPS times in the data header, the data cannot be geocorrected. 19 If there are no GPS times in the data header, the data cannot be geocorrected. Add timestamps from corresponding Fenix flightlines or estimate from the logsheet or file creation time. 20 20 21 21 3) Check for calibration data: … … 38 38 The radiometric calibration will fail if the dark frames are saved in a separate file to the data (Ops sometimes do this). Check the capture directory for any extra files labelled like they might be dark frames and append them to the end of the data file. Remember to add the autodarkstartline key to the header file. Alternatively use the script stitchOwl.py. 39 39 40 e.g. stitchOwl.py -c .../thermal/owl/OWL241a-15-8 41 40 42 Specim's calibration tool actually only uses dark frames to detect blinkers; it does not use them to radiometrically calibrate the data. Therefore, if dark frames are completely missing a calibration file (e.g. T1) may be used instead. 41 43 42 44 == Radiometric Calibration == 43 44 First check that detector response is stable across the entire flight by examining the calibration (.rad) files. If there are dramatic changes in the calibration curves for a particular flight line, make sure that it is not used to calibrate a different flight line. You will also need to double check that the data processed for that flight line look correctly calibrated.45 45 46 46 Specim have provided a tool to process the Owl raw data into calibrated data. Details on using this tool are located [https://arsf-dan.nerc.ac.uk/trac/wiki/Procedures/OwlProcessing/OwlTool here] if required. … … 70 70 == Dropped Frames == 71 71 72 If there are dropped frames they should be recorded in a .log file in the capture directory. These dropped frames need to be inserted intothe level 1b data file as empty lines before geocorrection to map the flight line correctly.72 If there are dropped frames they should be recorded in a .log file in the capture directory. Make sure they appear in the level 1b data file as empty lines before geocorrection to map the flight line correctly. 73 73 74 74 == Geocorrection == … … 84 84 == Create mask files == 85 85 86 Specim's tool produces a blinker file locating each of the blinking pixels. This can be converted to an apl-like mask using the script blinker2mask.py. Do this before making a delivery so the files aremoved into the delivery directory.86 Specim's tool produces a blinker file locating each of the blinking pixels. This are auomatically converted to mask files by APL, but can also be converted using the script blinker2mask.py. Make sure mask files are present before making a delivery so the files can be correctly moved into the delivery directory. 87 87 88 88 == Making a delivery == … … 91 91 92 92 make_arsf_delivery.py --projectlocation <project directory> --deliverytype owl --final 93 94 95 == Readme === 96 97 There is no separate owl option for make a readme. Generate a config file for the Fenix and manually edit it for the Owl. If you just edit the tex file you will have to run autoqc on the command line, but if there are no overflows and underflows just remove the table from the readme and state it in a sentence instead. 98 99 == Checking == 100 101 Follow the Fenix delivery checking procedure. 102 103 Also check that detector response is stable across the entire flight by examining the calibration (.rad) files (These are also bil files). If there are dramatic changes in the calibration curves for a particular flight line, make sure that it is not used to calibrate a different flight line. You will also need to double check that the data processed for that flight line look correctly calibrated. 93 104 94 105