EO-1/ Hyperion Science Data User's Guide

Add to my manuals
65 Pages

advertisement

EO-1/ Hyperion Science Data User's Guide | Manualzz

EO-1/Hyperion Science Data User’s Guide

MD11 - EO12000999_01CD01CC_r1.L1.qa

File name: EO12000147_01CD01CC_r1.L1

Frames assessed: 1-660

Source tape ID: EO1189

Sensors operational: [X] VNIR [X] SWIR

1.0 Image Quality Check

....... VNIR

1.1 Streaking

1.2 Banding

1.3 Shading across FOV

1.4 Saturation

1.5 Focus

1.6 Linedrops

SWIR Comments

[ ] [x] none

[ ] [ ]

[ ] [ ]

[ ] [ ]

[ ] [ ]

[ ] [ ]

2.0 Radiometric Calibration

2.1 Averaged dark file value: 523.6

3.0 Additional Comments

HYP.TO.01.077

Figure 12 : MD 11: Quality Assessment Form

3.5.3 Description of Sample Metadata Files - optional

This section describes the contents of sample metadata files. Once the user is familiar with the structure of the metadata file, the user should be able to gain information from all of the metadata files.

The first three lines of a log file identify the Level 1 processing command from which the log file was generated, the Hyperspectral Image Processing (HIP) software version number, and date and time file was processed. In this case, the command used to create the file is “cubeavg”, version 1.1 of HIP was used and the level 1 processing was performed on June 5, 2000.

The next set of information contains the command line arguments as well as file parameters associated with the input (source) and output files. The file parameters include the file name, file type, dimensions, data type, byte order (big-endian), and pixel order (BIL or BSQ)) are given for each input and output file. The file name includes the pathname in the level 1 processing system. When appropriate the metadata file will include command line options.

38

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this document.

EO-1/Hyperion Science Data User’s Guide HYP.TO.01.077

The end of a log file contains processing Results or Summary information. In this case, the file is reporting the average dark pixel value for the dark file used in the dark subtraction process. The subtracted dark file is 256 FOV pixels x 242 spectral pixels in size and averaged over ~220 frames.

The average dark file is supplied as MD3. The average dark pixel value reported in MD5 represents the average value over all FOV and spectral pixels and is used on the Quality Assurance form (MD11) to track instrument performance.

MD5 – EO12000147_01D101D0_r1.avg.log

***** cubeavg *****

HIP 1.1

Mon Jun 5 13:06:10 2000

----- Arguments -----

--source-file=/drb12/archive/level1/ground/EO12000147_01D101D0_r1.echo

--source-type=hyperion

--output-file=/drb12/archive/level1/ground/EO12000147_01D101D0_r1.avg

--output-type=generic

--verbose

----- Source file -----

File name: /drb12/archive/level1/ground/EO12000147_01D101D0_r1.echo

Type: .. Hyperion

Dimensions: 256 pixels x 242 bands x 206 frames

Data type: 16-bit unsigned integer

Byte order: big

Pixel order: BIL

----- Output file -----

File name: /drb12/archive/level1/ground/EO12000147_01D101D0_r1.avg

Type: .. Generic

Dimensions: 256 pixels x 242 bands x 1 frames

Data type: 16-bit unsigned integer

Byte order: big

Pixel order: BIL

Source: /drb12/archive/level1/ground/EO12000147_01D101D0_r1.echo

----- Summary -----

Average: 523.625

********************

Figure 13 : Example (MD5) - Average Log

39

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this document.

EO-1/Hyperion Science Data User’s Guide HYP.TO.01.077

Echo removal log (MD8) has the same general format as Average Log (MD5) but it reports that the echo correction process has been completed. At the end of this log file, the specific echo correction file used in the correction process is identified (ratio.txt), along with the number of the band at which echo correction began. The VNIR focal plane covers spectral bands 1-70, so it is expected that echo correction, which is required only in the SWIR, would start at band 71.

MD8 - EO12000147_01CA01C9_r1.echo.log

***** hypecho *****

HIP 1.1

Mon Jun 5 13:06:05 2000

----- Arguments -----

--source-file=/drb12/archive/level1/ground/EO12000147_01CA01C9_r1.smear

--source-type=hyperion

--output-file=/drb12/archive/level1/ground/EO12000147_01CA01C9_r1.echo

--output-type=hyperion

--start-band=71

--ratio-file=/dra2/calfiles/ratio.txt

--verbose

----- Source file -----

File name: /drb12/archive/level1/ground/EO12000147_01CA01C9_r1.smear

Type: .. Hyperion

Dimensions: 256 pixels x 242 bands x 206 frames

Data type: 16-bit unsigned integer

Byte order: big

Pixel order: BIL

----- Output file -----

File name: /drb12/archive/level1/ground/EO12000147_01CA01C9_r1.echo

Type: .. Hyperion

Dimensions: 256 pixels x 242 bands x 206 frames

Data type: 16-bit unsigned integer

Byte order: big

Pixel order: BIL

Source: /drb12/archive/level1/ground/EO12000147_01CA01C9_r1.smear

----- Ratio file -----

Ratio file: /dra2/calfiles/ratio.txt

Start band: 71

********************

Figure 14 : Example (MD 8) - Echo Removal Log

40

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this document.

EO-1/Hyperion Science Data User’s Guide HYP.TO.01.077

Smear Removal Log (MD9) has the same format as Echo Removal Log (MD8) but there is no file used in the smear correction process. Again, the band at which smear correction begins is reported.

The VNIR focal plane covers spectral bands 1-70, so it is expected that smear correction, which is also only required in the SWIR, would start at band 71.

MD9 - EO12000147_01CD01CC_r1.smear.log

***** hypsmear *****

HIP 1.1

Mon Jun 5 13:07:31 2000

----- Arguments -----

--source-file=/drb12/archive/level0/ground/EO12000147_01CD01CC_r1.L0

--source-type=hyperion

--output-file=/drb12/archive/level1/ground/EO12000147_01CD01CC_r1.smear

--output-type=hyperion

--start-band=71

--verbose

----- Source file -----

File name: /drb12/archive/level0/ground/EO12000147_01CD01CC_r1.L0

Type: .. Hyperion

Dimensions: 256 pixels x 242 bands x 660 frames

Data type: 16-bit unsigned integer

Byte order: big

Pixel order: BIL

----- Output file -----

File name: /drb12/archive/level1/ground/EO12000147_01CD01CC_r1.smear

Type: .. Hyperion

Dimensions: 256 pixels x 242 bands x 660 frames

Data type: 16-bit unsigned integer

Byte order: big

Pixel order: BIL

Source: /drb12/archive/level0/ground/EO12000147_01CD01CC_r1.L0

----- Options -----

Start band: 71

********************

Figure 15 : Example (MD 9) - Smear Removal Log

Pixel Repair Log (MD10) has the same initial format as the preceding metadata files but it reports on the repair of known bad pixels. The specific file used to identify the known bad pixels is identified

(badpix.txt). The results summary in this metadata file is in two parts. The first part identifies the known bad pixels, by band or spectral pixel number and sample or FOV pixel number, and is essentially a printout of badpix.txt. This file will be updated over the course of the mission. The second results section indicates how the values of these known bad pixels are replaced. For FOV locations other than 1 or 256, the value is replaced by an average of the value in the neighboring FOV pixels (e.g., 50% of (61, 92) and 50% of (61,94) for bad pixel (61, 93)). FOV pixels 1 and 256 are replaced by the value of the neighbor pixel, 2 or 255.

41

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this document.

EO-1/Hyperion Science Data User’s Guide

MD10 - EO12000147_01CD01CC_r1.fix.log

***** cubefix *****

HIP 1.1

Mon Jun 5 13:08:29 2000

----- Arguments -----

--source-file=/drb12/archive/level1/ground/EO12000147_01CD01CC_r1.cal

--source-type=hyperion

--output-file=/drb12/archive/level1/ground/EO12000147_01CD01CC_r1.L1

--output-type=hyperion

--bad-file=/dra2/calfiles/badpix.txt

--verbose

----- Source file -----

File name: /drb12/archive/level1/ground/EO12000147_01CD01CC_r1.cal

Type: .. Hyperion

Dimensions: 256 pixels x 242 bands x 660 frames

Data type: 16-bit unsigned integer

Byte order: big

Pixel order: BIL

HYP.TO.01.077

----- Output file -----

File name: /drb12/archive/level1/ground/EO12000147_01CD01CC_r1.L1

Type: .. Hyperion

Dimensions: 256 pixels x 242 bands x 660 frames

Data type: 16-bit unsigned integer

Byte order: big

Pixel order: BIL

Source: /drb12/archive/level1/ground/EO12000147_01CD01CC_r1.cal

----- Bad pixels file -----

File name: /dra2/calfiles/badpix.txt

----- Bad pixels (band, sample)---

16, 1

17, 1

18, 1

19, 1

20, 1

21, 1

22, 1

23, 1

24, 1

25, 1

26, 1

27, 1

28, 1

29, 1

30, 1

31, 1

32, 1

33, 1

34, 1

35, 1

61, 93

1, 1

2, 1

3, 1

4, 1

5, 1

6, 1

7, 1

8, 1

9, 1

10, 1

11, 1

12, 1

13, 1

14, 1

15, 1

42

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this document.

EO-1/Hyperion Science Data User’s Guide

72, 95

94, 93

99, 92

116, 138

168, 256

169, 23

190, 113

200, 8

201, 8

203, 115

----- Result -----

(1, 1): 100% of 2

(2, 1): 100% of 2

(3, 1): 100% of 2

(4, 1): 100% of 2

(5, 1): 100% of 2

(6, 1): 100% of 2

(7, 1): 100% of 2

(8, 1): 100% of 2

(9, 1): 100% of 2

(10, 1): 100% of 2

(11, 1): 100% of 2

(12, 1): 100% of 2

(13, 1): 100% of 2

(14, 1): 100% of 2

(15, 1): 100% of 2

(16, 1): 100% of 2

(17, 1): 100% of 2

(18, 1): 100% of 2

(19, 1): 100% of 2

(20, 1): 100% of 2

(21, 1): 100% of 2

(22, 1): 100% of 2

(23, 1): 100% of 2

(24, 1): 100% of 2

(25, 1): 100% of 2

(26, 1): 100% of 2

(27, 1): 100% of 2

(28, 1): 100% of 2

(29, 1): 100% of 2

(30, 1): 100% of 2

(31, 1): 100% of 2

(32, 1): 100% of 2

(33, 1): 100% of 2

(34, 1): 100% of 2

(35, 1): 100% of 2

(61, 93): 50% of 92 and 94

(72, 95): 50% of 94 and 96

(94, 93): 50% of 92 and 94

(99, 92): 50% of 91 and 93

(116, 138): 50% of 137 and 139

(168, 256): 100% of 255

(169, 23): 50% of 22 and 24

(190, 113): 50% of 112 and 114

(200, 8): 50% of 7 and 9

(201, 8): 50% of 7 and 9

(203, 115): 50% of 114 and 116

HYP.TO.01.077

----- Summary -----

30360 pixels fixed out of 40888320 (0.074251%)

*******************

Figure 16 : Example (MD 10) – Pixel Repair Log

43

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this document.

advertisement

Was this manual useful for you? Yes No
Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Related manuals