Changes between Version 3 and Version 4 of Procedures/HyperspectralCalibrationCreation
- Timestamp:
- Sep 21, 2015, 2:30:39 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/HyperspectralCalibrationCreation
v3 v4 1 1 = Generating calibration files for Fenix = 2 2 3 Radiometric, wavelength and miscellaneous other calibration of the Fenix is undertaken at ARSF-Ops at least annually since 2014. This page describes how to use the calibration software written by ARSF-DAN to create the necessary calibration files from the raw calibration data. 3 Radiometric, wavelength and miscellaneous other calibration of the Fenix is undertaken at ARSF-Ops at least annually since 2014. This page describes how to use the calibration software written by ARSF-DAN to create the necessary calibration files from the raw calibration data. All progress should be recorded on a trac ticket (https://arsf-dan.nerc.ac.uk/trac/newticket) and added to the list below. 4 5 2015: https://arsf-dan.nerc.ac.uk/trac/ticket/594 4 6 5 7 == Setup == 6 8 7 Relevant scripts are held in the arsf -internalgit repository under tools/libarsfcal.9 Relevant scripts are held in the arsf git repository under tools/libarsfcal. 8 10 9 11 Note that the various calibration scripts written in Python expect to import a package called "libarsfcal". This means that you must have the directory above the libarsfcal directory in your PYTHONPATH environment variable for the scripts to run. So eg. … … 49 51 == Wavelength calibration == 50 52 51 This must be run first, since the radiometric calibration requires a wavelength calibration to tie the lamp data into. Note for Eagle you may need to re-run gen_bandsets.py (see "Other scripts", below) with different settings in order to obtain bandset files for different spectral binning settings.53 This must be run first, since the radiometric calibration requires a wavelength calibration to tie the lamp data into. Note for Eagle and Fenix you may need to re-run gen_bandsets.py (see "Other scripts", below) with different settings in order to obtain bandset files for different spectral binning settings. 52 54 53 55 '''Master script:''' cal_spectral.py … … 84 86 The generated wavelength scale may be checked against the lamp lines to determine the error in each matching band and it's FWHM. The output of this test is recorded in the data analysis report. Any unrealistic FWHMs and any failing bands should be removed from the calibration and the wavelength scale regenerated. 85 87 86 88 '''Master script:''' calc_peak_diffs.py 87 89 88 90 Basic usage of this requires the following arguments: … … 91 93 * -l: Spectral lines file. 92 94 95 When you have created the final wavelength scale that passes the lamp line test, record the parameters on the ticket, especially the data set (day), sample_hdr_file and linefile from the config file and any optional parameters used with cal_spectral.py. Also record the final anchors and check that the VNIR and SWIR starting wavelengths are realistic. These may not match up with the anchors, depending on which sample header is used, as the previous calibration wavelengths are not currently set in the raw data files. 96 93 97 == Radiometric calibration == 94 98 95 99 This can either be run after the wavelength calibration in order to obtain a cal using an up-to-date wavelength calibration, or it can be run using an old wavelength calibration. 96 100 97 101 '''Master script:''' cal_radiometric.py 98 102 99 103 Basic usage of this requires only the name of the config file as an argument. You may also want to use the following arguments: … … 119 123 120 124 There are scripts to generate analysis graphs and files under libarsfcal/analysis. These should be run on the calibration output, please add to them if you think of more tests. 125 126 == Data quality report == 127 128 The data quality report must be updated for each calibration using the outputs produced by calc_peak_diffs.py and comparison.py.