UVIS Image Cube (REVISED July 11, 2007)
Each observation is organized as a series of 2-d spatial image planes, spatial pixel
by readout. The cube is formed by creating an image plane for each spectral bin. Thus the
first 1024, 512, 341, or 256 (or other spectral binning that has yet to be used) image
layers will be UVIS data. Geometry data is calculated for the mid-point time of each
integration. The concept of the UVIS image cube is similar to that of standard
hyperspectral image cubes (see AVIRIS data, for example) but with the addition of
geometric information included as additional planes.
The image cubes are saved as binary files, with network byte order (Intel based).
The cube dimensions are arranged as follows.
Image_cube = fltarr(spatial dimension, readouts, spectral)
The UVIS data in the image planes have been flatfield calibrated using Andrew
Steffl’s routines, the time-variant Red Patch as derived by Holtzclaw and McClintock,
and had an empirically derived Radioisotopic Thermal Generator (RTG) noise
component subtracted at a constant rate of 4e-6 counts/second/pixel.
In addition to the image data planes, the geometric data is included in the last 49
planes. The order of the geometric data planes are as follows, with the Plane # being the
number of the plane after the image data (ie. 1024 + 1,2,3, etc.).
UVIS data cubes are also available as IDL save files. These save files restore a
structure that includes all the data as the image cube, ‘datastruct’, but with slightly
different naming conventions that take advantage of IDL structures. See the document,
UVISImageCube_descriptions.doc, included in the Cube Generator distribution for
further details about the structure formats.
Plane #
Quantity
Geometer Source
1
2
3
4
5
6
7
8
9
10
11
12
13
Pixel Center RA
Pixel Lower Left RA
Pixel Upper Left RA
Pixel Upper Right RA
Pixel Lower Right RA
Pixel Center Declination
Pixel Lower Left Declination
Pixel Upper Left Declination
Pixel Upper Right Declination
Pixel Lower Right Declination
Pixel Center Latitude
Pixel Lower Left Latitude
Pixel Upper Left Latitude
data.ra_full(0,*)
data.ra_full(1,*)
data.ra_full(2.*)
data.ra_full(3,*)
data.ra_full(4,*)
data.dec_full(0,*)
data.dec_full(1,*)
data.dec_full(2.*)
data.dec_full(3,*)
data.dec_full(4,*)
data.lat_full(0,*)
data.lat_full(1,*)
data.lat_full(2.*)
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
Pixel Upper Right Latitude
Pixel Lower Right Latitude
Pixel Center Longitude
Pixel Lower Left Longitude
Pixel Upper Left Longitude
Pixel Upper Right Longitude
Pixel Lower Right Longitude
Pixel Center Incidence Angle
Pixel Center Emission Angle
Pixel Center Phase Angle
Pixel Center Rayheight
Pixel Center Occultation Latitude
Pixel Center Occultation Longitude
Pixel Center Line of Sight Distance
Sub-Spacecraft Longitude
Sub-Spacecraft Latitude
Sub-Solar Longitude
Sub-Solar Latitude
Spacecraft Altitude
Target Right Ascension
Target Declination
Target Phase Angle
Target Incidence Angle
Target Emission Angle
Spacecraft Location, X
Spacecraft Location, Y
Spacecraft Location, Z
Spacecraft Velocity, X
Spacecraft Velocity, Y
Spacecraft Velocity, Z
ET
Center Ring Plane Radii
Lower Left Ring Plane Radii
Upper Left Plane Radii
Upper Right Plane Radii
Lower Right Plane Radii
data.lat_full(3,*)
data.lat_full(4,*)
data.lon_full(0,*)
data.lon_full(1,*)
data.lon_full(2.*)
data.lon_full(3,*)
data.lon_full(4,*)
data.incidence
data.emission
data.phase
data.rayheight
data.latocc
data.lonocc
data.losdist
data.subsclon
data.subsclat
data.subsolarlon
data.subsolarlat
data.alt
data.ratarg
data.dectarg
data.phasetarg
data.incidencetarg
data.emissiontarg
data.scloc(0)
data.scloc(1)
data.scloc(2)
data.scvel(0)
data.scvel(1)
data.scvel(2)
data.et
data.rrad_full(0)
data.rrad_full(1)
data.rrad_full(2)
data.rrad_full(3)
data.rrad_full(4)
The Following backplanes are only written when the image cube is output as an IDL save
file, in which case it is a string vector equal in length to the number of readouts.
50
51
kernels
UTC
kernels
time
Memory loaded SPICE