]>>
startxref
126937
%%EOF
i25_obs_names.html 0100666 0001257 0000335 00000001110 10656642273 014235 0 ustar laspweb galileo ; file: /ansa4/uvs_p2/data/i25_obs_names.lis Apr 9, 2007 -kes
LASP File Name GLL Obs ID SCET Begin Time SCET End Time RIM Begin RIM End
i25a_urt_iueclips01.dat = 25IUECLIPS01 1999-331/03:47:04.981 1999-331/05:41:20.646 5274822:00:0 5274935:00:0
i25a_urt_tu25nans01.dat = 25tu25nans01 1999-331/01:45:44.986 1999-331/03:46:04.317 5274702:00:0 5274821:00:0
i25a_urt_tu25nans02.dat = 25tu25nans02 1999-331/05:42:20.977 1999-331/18:56:04.308 5274936:00:0 5275721:00:0
No useful UVS science data due to grating malfunction
i25a_urt_iueclips01.dat_1 0100666 0001257 0000335 00000032420 10606532160 015320 0 ustar laspweb galileo c K 2 c K / |P c K ! |P
* * c K / c K " 9 |P c K }P * ( c K 9 c K
}P c K ) 7 7}P * i25a_urt_iueclips01.lbl_1 0100666 0001257 0000335 00000021054 10606532161 015323 0 ustar laspweb galileo CCSD3ZF0000100000001NJPL3IF0PDSX00000001
/* FILE: I25A_URT_IUECLIPS01.LBL */
/* VERSION 1.4: 28-OCT-2005 MOSSER */
PDS_VERSION_ID = PDS3
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 4528 /*=1132*4 */
FILE_RECORDS = 3
PRODUCT_ID = "I25A_URT_IUECLIPS01.DAT"
PRODUCT_NAME = "25IUECLIPS01 EDR DATA"
DATA_SET_ID = "GO-J-UVS-2-EDR-JUP-V1.0"
OBSERVATION_ID = "25IUECLIPS01"
SPACECRAFT_NAME = "GALILEO ORBITER"
INSTRUMENT_NAME = "ULTRAVIOLET SPECTROMETER"
MISSION_PHASE_NAME = "JUPITER ORBIT OPERATIONS"
TARGET_NAME = "IO"
PRODUCT_CREATION_TIME = "1999-11-29"
START_TIME = 1999-331T03:47:04.981Z
STOP_TIME = 1999-331T05:41:20.646Z
SPACECRAFT_CLOCK_START_COUNT = "5274822:00:0"
SPACECRAFT_CLOCK_STOP_COUNT = "5274935:00:0"
^SPECTRUM = "I25A_URT_IUECLIPS01.DAT"
DESCRIPTION = "
This file was produced by the Galileo UVS/EUV team at the Laboratory
for Atmospheric and Space Physics (LASP) at the University of Colorado
at Boulder. Refer to the Galileo UVS/EUV instrument paper 'Galileo
Ultraviolet Spectrometer Experiment', Vol 60, Space Science Reviews,
pages 503-530, by C.W. Hord et al, for hardware and calibration
information.
The data contained in the file were obtained by the UVS instrument
during Jupiter operations mission phase.
The UVS data in this file were obtained using the UVS RTS mode. Check
the commanded configuration in the flight sequence for the most
accurate understanding of these data. Calibration to physical units
has not been made; the data are in units of 'raw counts per time'.
The command instrument integration time and grating positions are
given in the header portion of the record; no attempt has been made to
verify the raw data acquired these positions in the raw EDRs.
A diagram of the file and record structure is shown below:
|-----+---------------|
1 |time | S | RTS SUMMATION
|-----+---------------| .
2 |time | S | .
|-----+---------------| .
3 |time | S | .
|-----+---------------| .
. .
. repeats .
. .
|-----+---------------| .
ij |time | S | RTS SUMMATION
|-----+---------------|
|40 4-| /S= \
|byte | /1092 \
|time | /4-byte \
|tags | /spectral \
|& hdr| / values \
Records 1 to ij are data records. Each record begins with a 160-byte
header containing 40 4-byte integer numbers. The header values are
described below, the exact definition of the time values is further
described in the Galileo document 625-610. The time tags given in
the data records refer to the time of the first integration period
included in the packet summation period; the STOP time refers to the
time of the first integration of the last RIM included in the summation
period. The LABEL START and STOP time values refer to the first
and last integrations of the full data set.
The data start at byte 161, following the header information. Each
record contains one readout (termed FLUSH in the sequences) of the
UVS Real Time Buffer (RTB). The RTB contains UVS spectra summed
by the onboard (CDS) computer. The RTB, and thus the UVS raw data
record, is arranged as a skewed pair of spectra. The duration of
the time sum is given by the data label start and stop times, and
is generally one-half hour, one hour or 24 hours but may be a subset
of these.
A UVS spectra has 546 values, the first 18 values are fidutials and
engineering operation values. The remaining 528 values are the raw
output of the spectrometer. The fidutial contains seven values equal
to 255 each. The RTB consists of 1092 values or two 546-value spectra.
The spectra are arranged in the RTB as follows:
84 values 546 values 462 values
|----------|--|----------------------------|--|--------------------|
|final part|f1| one full spectral sum |f2| 1st part of 2nd sum|
| of 2nd | | | | |
|spect.sum | | | | |
where f1 is the fidutial of the first spectra and f2 is the fidutial
of the second spectra. Eighty-four UVS values are read out in one
SCLK minor frame, 1092 values are read out in thirteen minor frames.
There are 91 minor frames in one SCLK RIM. There will be seven UVS
RTS spectral pairs summed per RIM. The first minor frame of the RIM
contains 84 UVS values set to zero therefore the summation period in
the first 84 values of the RTB is technically different from the
remaining summed data.
All values in the RTB are summed, including the fidutials and
engineering values. The 2-byte RTB rolls over and begins counting
again from value zero.
The records contents as follows:
TORUS1:[GLL_RAW.INFO]UVS_Phase2_RTS_HDR.DOC
June 21,1996 - JEREMY GEBBEN
Updated February 27, 1997 - WENDY SWEET
Updated Jul 24, 97 - Simmons
HEADER:
Earth Receipt Time
0 = Year (last 2 digits eg. 96)
1 = day of year
2 = hours
3 = minutes
4 = seconds
5 = milliseconds
Spacecraft Event time for start of integration:
6 = Year (last 2 digits eg. 96)
7 = day of year
8 = hours
9 = minutes
10 = seconds
11 = milliseconds
SCLK time for start of integration:
12 = start RIM (all realtime data starts on mf 0)
Spacecraft Event time for end of integration:
13 = Year (last 2 digits eg. 96)
14 = day of year
15 = hours
16 = minutes
17 = seconds
18 = milliseconds
SCLK time for end of integration:
19 = end RIM (all realtime data ends on mf 0)
20 = # of RTS packets that went into this array(max = 8)
Data Presence Indicators (dpi)
21-28 = dpi flags,1 for each packet
Each is a 4 byte field:
Top byte:
00 = no data missing
FF = entire packet missing
01 = data missing at end of packet
02 = data missing in middle of packet
03 = data missing at end of packet
Lower 3 bytes are only used if top byte is 01,02, or 03
In these cases, the three lower bytes are used to report
the position of the gap:
second byte: # of data words(2 bytes)
at start(0 if gap is at start)
third byte : # of data words missing
bottom byte: # of data words at end of packet
(0 if gap is at end)
29 = packet sequence # of the first packet in this set
30,31 = spare (set to -1)
32 = software version number (of IPF_RT_PROC.PRO - both UVS and EUV)
33 = commanded summation period (in RIMS)
34 = commanded number of steps in the miniscan for the first spectrum
35 = commanded number of steps in the miniscan for the second spectrum
36 = commanded initial grating position
37 = commanded number of grating steps to move to the second spectrum
38,39 = spare (set to -1)
DATA:
40-123 = data (6 integrations/RIM)
124-141 = first fiducial
142-669 = data (7 integrations/RIM)
670-687 = second fiducial
688-1131 = data (7 integrations/RIM)
1132*4=4528 byte records
........................................................"
OBJECT = SPECTRUM
NAME = "1 UVS RTS SUMMATION BUFFER"
INTERCHANGE_FORMAT = BINARY
ROWS = 3
COLUMNS = 41
ROW_BYTES = 4528
^STRUCTURE = "RTS_SUMMATION.FMT"
DESCRIPTION = "
The summation data table consists of 40 4-byte integers of time tags
(RIM, yr, doy, hr, min, sec, etc), data quality flags and spares, and
1092 spectral values for one summed spectral pair. The
record structure is the same as the table. "
END_OBJECT = SPECTRUM
END
i25a_urt_iueclips01.xdr_1 0100666 0001257 0000335 00000016040 10606532161 015346 0 ustar laspweb galileo c K 2 c K / | P c K ! | P
* * c K / c K " 9 | P c K } P * ( c K 9 c K
} P c K ) 7 }7 P * i25a_urt_iueclips01.xlbl_2 0100666 0001257 0000335 00000021043 10606532162 015513 0 ustar laspweb galileo CCSD3ZF0000100000001NJPL3IF0PDSX00000001
/* FILE: I25A_URT_IUECLIPS01.LBL */
/* VERSION 1.4: 28-OCT-2005 MOSSER */
PDS_VERSION_ID = PDS3
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 4528 /*=1132*4 */
FILE_RECORDS = 3
PRODUCT_ID = "I25A_URT_IUECLIPS01.XDR"
PRODUCT_NAME = "25IUECLIPS01"
DATA_SET_ID = "GO-J-UVS-2-EDR-JUP-V1.0"
OBSERVATION_ID = "25iueclips01"
SPACECRAFT_NAME = "GALILEO ORBITER"
INSTRUMENT_NAME = "ULTRAVIOLET SPECTROMETER"
MISSION_PHASE_NAME = "JUPITER ORBIT OPERATIONS"
TARGET_NAME = "IO"
PRODUCT_CREATION_TIME = "1999-11-29"
START_TIME = 1999-331T03:47:04.981Z
STOP_TIME = 1999-331T05:41:20.646Z
SPACECRAFT_CLOCK_START_COUNT = "5274822:00:0"
SPACECRAFT_CLOCK_STOP_COUNT = "5274935:00:0"
^SPECTRUM = "I25A_URT_IUECLIPS01.XDR"
DESCRIPTION = "
This file was produced by the Galileo UVS/EUV team at the Laboratory
for Atmospheric and Space Physics (LASP) at the University of Colorado
at Boulder. Refer to the Galileo UVS/EUV instrument paper 'Galileo
Ultraviolet Spectrometer Experiment', Vol 60, Space Science Reviews,
pages 503-530, by C.W. Hord et al, for hardware and calibration
information.
The data contained in the file were obtained by the UVS instrument
during Jupiter operations mission phase.
The UVS data in this file were obtained using the UVS RTS mode. Check
the commanded configuration in the flight sequence for the most
accurate understanding of these data. Calibration to physical units
has not been made; the data are in units of 'raw counts per time'.
The command instrument integration time and grating positions are
given in the header portion of the record; no attempt has been made to
verify the raw data acquired these positions in the raw EDRs.
A diagram of the file and record structure is shown below:
|-----+---------------|
1 |time | S | RTS SUMMATION
|-----+---------------| .
2 |time | S | .
|-----+---------------| .
3 |time | S | .
|-----+---------------| .
. .
. repeats .
. .
|-----+---------------| .
ij |time | S | RTS SUMMATION
|-----+---------------|
|40 4-| /S= \
|byte | /1092 \
|time | /4-byte \
|tags | /spectral \
|& hdr| / values \
Records 1 to ij are data records. Each record begins with a 160-byte
header containing 40 4-byte integer numbers. The header values are
described below, the exact definition of the time values is further
described in the Galileo document 625-610. The time tags given in
the data records refer to the time of the first integration period
included in the packet summation period; the STOP time refers to the
time of the first integration of the last RIM included in the summation
period. The LABEL START and STOP time values refer to the first
and last integrations of the full data set.
The data start at byte 161, following the header information. Each
record contains one readout (termed FLUSH in the sequences) of the
UVS Real Time Buffer (RTB). The RTB contains UVS spectra summed
by the onboard (CDS) computer. The RTB, and thus the UVS raw data
record, is arranged as a skewed pair of spectra. The duration of
the time sum is given by the data label start and stop times, and
is generally one-half hour, one hour or 24 hours but may be a subset
of these.
A UVS spectra has 546 values, the first 18 values are fidutials and
engineering operation values. The remaining 528 values are the raw
output of the spectrometer. The fidutial contains seven values equal
to 255 each. The RTB consists of 1092 values or two 546-value spectra.
The spectra are arranged in the RTB as follows:
84 values 546 values 462 values
|----------|--|----------------------------|--|--------------------|
|final part|f1| one full spectral sum |f2| 1st part of 2nd sum|
| of 2nd | | | | |
|spect.sum | | | | |
where f1 is the fidutial of the first spectra and f2 is the fidutial
of the second spectra. Eighty-four UVS values are read out in one
SCLK minor frame, 1092 values are read out in thirteen minor frames.
There are 91 minor frames in one SCLK RIM. There will be seven UVS
RTS spectral pairs summed per RIM. The first minor frame of the RIM
contains 84 UVS values set to zero therefore the summation period in
the first 84 values of the RTB is technically different from the
remaining summed data.
All values in the RTB are summed, including the fidutials and
engineering values. The 2-byte RTB rolls over and begins counting
again from value zero.
The records contents as follows:
TORUS1:[GLL_RAW.INFO]UVS_Phase2_RTS_HDR.DOC
June 21,1996 - JEREMY GEBBEN
Updated February 27, 1997 - WENDY SWEET
Updated Jul 24, 97 - Simmons
HEADER:
Earth Receipt Time
0 = Year (last 2 digits eg. 96)
1 = day of year
2 = hours
3 = minutes
4 = seconds
5 = milliseconds
Spacecraft Event time for start of integration:
6 = Year (last 2 digits eg. 96)
7 = day of year
8 = hours
9 = minutes
10 = seconds
11 = milliseconds
SCLK time for start of integration:
12 = start RIM (all realtime data starts on mf 0)
Spacecraft Event time for end of integration:
13 = Year (last 2 digits eg. 96)
14 = day of year
15 = hours
16 = minutes
17 = seconds
18 = milliseconds
SCLK time for end of integration:
19 = end RIM (all realtime data ends on mf 0)
20 = # of RTS packets that went into this array(max = 8)
Data Presence Indicators (dpi)
21-28 = dpi flags,1 for each packet
Each is a 4 byte field:
Top byte:
00 = no data missing
FF = entire packet missing
01 = data missing at end of packet
02 = data missing in middle of packet
03 = data missing at end of packet
Lower 3 bytes are only used if top byte is 01,02, or 03
In these cases, the three lower bytes are used to report
the position of the gap:
second byte: # of data words(2 bytes)
at start(0 if gap is at start)
third byte : # of data words missing
bottom byte: # of data words at end of packet
(0 if gap is at end)
29 = packet sequence # of the first packet in this set
30,31 = spare (set to -1)
32 = software version number (of IPF_RT_PROC.PRO - both UVS and EUV)
33 = commanded summation period (in RIMS)
34 = commanded number of steps in the miniscan for the first spectrum
35 = commanded number of steps in the miniscan for the second spectrum
36 = commanded initial grating position
37 = commanded number of grating steps to move to the second spectrum
38,39 = spare (set to -1)
DATA:
40-123 = data (6 integrations/RIM)
124-141 = first fiducial
142-669 = data (7 integrations/RIM)
670-687 = second fiducial
688-1131 = data (7 integrations/RIM)
1132*4=4528 byte records
........................................................"
OBJECT = SPECTRUM
NAME = "1 UVS RTS SUMMATION BUFFER"
INTERCHANGE_FORMAT = BINARY
ROWS = 3
COLUMNS = 41
ROW_BYTES = 4528
^STRUCTURE = "RTS_SUMMATION.FMT"
DESCRIPTION = "
The summation data table consists of 40 4-byte integers of time tags
(RIM, yr, doy, hr, min, sec, etc), data quality flags and spares, and
1092 spectral values for one summed spectral pair. The
record structure is the same as the table. "
END_OBJECT = SPECTRUM
END
i25a_urt_tu25nans01.dat_1 0100666 0001257 0000335 00000021540 10606532163 015166 0 ustar laspweb galileo c K ' c K - , N|P c K - = |P z * ; c K 4 c K . |P c K . ; |P * 9 i25a_urt_tu25nans01.lbl_1 0100666 0001257 0000335 00000021062 10606532163 015166 0 ustar laspweb galileo CCSD3ZF0000100000001NJPL3IF0PDSX00000001
/* FILE: I25A_URT_TU25NANS01.LBL */
/* VERSION 1.4: 28-OCT-2005 MOSSER */
PDS_VERSION_ID = PDS3
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 4528 /*=1132*4 */
FILE_RECORDS = 2
PRODUCT_ID = "I25A_URT_TU25NANS01.DAT"
PRODUCT_NAME = "25TU25NANS01 EDR DATA"
DATA_SET_ID = "GO-J-UVS-2-EDR-JUP-V1.0"
OBSERVATION_ID = "25TU25NANS01"
SPACECRAFT_NAME = "GALILEO ORBITER"
INSTRUMENT_NAME = "ULTRAVIOLET SPECTROMETER"
MISSION_PHASE_NAME = "JUPITER ORBIT OPERATIONS"
TARGET_NAME = "IO-TORUS"
PRODUCT_CREATION_TIME = "1999-11-29"
START_TIME = 1999-331T01:45:44.986Z
STOP_TIME = 1999-331T03:46:04.317Z
SPACECRAFT_CLOCK_START_COUNT = "5274702:00:0"
SPACECRAFT_CLOCK_STOP_COUNT = "5274821:00:0"
^SPECTRUM = "I25A_URT_TU25NANS01.DAT"
DESCRIPTION = "
This file was produced by the Galileo UVS/EUV team at the Laboratory
for Atmospheric and Space Physics (LASP) at the University of Colorado
at Boulder. Refer to the Galileo UVS/EUV instrument paper 'Galileo
Ultraviolet Spectrometer Experiment', Vol 60, Space Science Reviews,
pages 503-530, by C.W. Hord et al, for hardware and calibration
information.
The data contained in the file were obtained by the UVS instrument
during Jupiter operations mission phase.
The UVS data in this file were obtained using the UVS RTS mode. Check
the commanded configuration in the flight sequence for the most
accurate understanding of these data. Calibration to physical units
has not been made; the data are in units of 'raw counts per time'.
The command instrument integration time and grating positions are
given in the header portion of the record; no attempt has been made to
verify the raw data acquired these positions in the raw EDRs.
A diagram of the file and record structure is shown below:
|-----+---------------|
1 |time | S | RTS SUMMATION
|-----+---------------| .
2 |time | S | .
|-----+---------------| .
3 |time | S | .
|-----+---------------| .
. .
. repeats .
. .
|-----+---------------| .
ij |time | S | RTS SUMMATION
|-----+---------------|
|40 4-| /S= \
|byte | /1092 \
|time | /4-byte \
|tags | /spectral \
|& hdr| / values \
Records 1 to ij are data records. Each record begins with a 160-byte
header containing 40 4-byte integer numbers. The header values are
described below, the exact definition of the time values is further
described in the Galileo document 625-610. The time tags given in
the data records refer to the time of the first integration period
included in the packet summation period; the STOP time refers to the
time of the first integration of the last RIM included in the summation
period. The LABEL START and STOP time values refer to the first
and last integrations of the full data set.
The data start at byte 161, following the header information. Each
record contains one readout (termed FLUSH in the sequences) of the
UVS Real Time Buffer (RTB). The RTB contains UVS spectra summed
by the onboard (CDS) computer. The RTB, and thus the UVS raw data
record, is arranged as a skewed pair of spectra. The duration of
the time sum is given by the data label start and stop times, and
is generally one-half hour, one hour or 24 hours but may be a subset
of these.
A UVS spectra has 546 values, the first 18 values are fidutials and
engineering operation values. The remaining 528 values are the raw
output of the spectrometer. The fidutial contains seven values equal
to 255 each. The RTB consists of 1092 values or two 546-value spectra.
The spectra are arranged in the RTB as follows:
84 values 546 values 462 values
|----------|--|----------------------------|--|--------------------|
|final part|f1| one full spectral sum |f2| 1st part of 2nd sum|
| of 2nd | | | | |
|spect.sum | | | | |
where f1 is the fidutial of the first spectra and f2 is the fidutial
of the second spectra. Eighty-four UVS values are read out in one
SCLK minor frame, 1092 values are read out in thirteen minor frames.
There are 91 minor frames in one SCLK RIM. There will be seven UVS
RTS spectral pairs summed per RIM. The first minor frame of the RIM
contains 84 UVS values set to zero therefore the summation period in
the first 84 values of the RTB is technically different from the
remaining summed data.
All values in the RTB are summed, including the fidutials and
engineering values. The 2-byte RTB rolls over and begins counting
again from value zero.
The records contents as follows:
TORUS1:[GLL_RAW.INFO]UVS_Phase2_RTS_HDR.DOC
June 21,1996 - JEREMY GEBBEN
Updated February 27, 1997 - WENDY SWEET
Updated Jul 24, 97 - Simmons
HEADER:
Earth Receipt Time
0 = Year (last 2 digits eg. 96)
1 = day of year
2 = hours
3 = minutes
4 = seconds
5 = milliseconds
Spacecraft Event time for start of integration:
6 = Year (last 2 digits eg. 96)
7 = day of year
8 = hours
9 = minutes
10 = seconds
11 = milliseconds
SCLK time for start of integration:
12 = start RIM (all realtime data starts on mf 0)
Spacecraft Event time for end of integration:
13 = Year (last 2 digits eg. 96)
14 = day of year
15 = hours
16 = minutes
17 = seconds
18 = milliseconds
SCLK time for end of integration:
19 = end RIM (all realtime data ends on mf 0)
20 = # of RTS packets that went into this array(max = 8)
Data Presence Indicators (dpi)
21-28 = dpi flags,1 for each packet
Each is a 4 byte field:
Top byte:
00 = no data missing
FF = entire packet missing
01 = data missing at end of packet
02 = data missing in middle of packet
03 = data missing at end of packet
Lower 3 bytes are only used if top byte is 01,02, or 03
In these cases, the three lower bytes are used to report
the position of the gap:
second byte: # of data words(2 bytes)
at start(0 if gap is at start)
third byte : # of data words missing
bottom byte: # of data words at end of packet
(0 if gap is at end)
29 = packet sequence # of the first packet in this set
30,31 = spare (set to -1)
32 = software version number (of IPF_RT_PROC.PRO - both UVS and EUV)
33 = commanded summation period (in RIMS)
34 = commanded number of steps in the miniscan for the first spectrum
35 = commanded number of steps in the miniscan for the second spectrum
36 = commanded initial grating position
37 = commanded number of grating steps to move to the second spectrum
38,39 = spare (set to -1)
DATA:
40-123 = data (6 integrations/RIM)
124-141 = first fiducial
142-669 = data (7 integrations/RIM)
670-687 = second fiducial
688-1131 = data (7 integrations/RIM)
1132*4=4528 byte records
........................................................"
OBJECT = SPECTRUM
NAME = "1 UVS RTS SUMMATION BUFFER"
INTERCHANGE_FORMAT = BINARY
ROWS = 2
COLUMNS = 41
ROW_BYTES = 4528
^STRUCTURE = "RTS_SUMMATION.FMT"
DESCRIPTION = "
The summation data table consists of 40 4-byte integers of time tags
(RIM, yr, doy, hr, min, sec, etc), data quality flags and spares, and
1092 spectral values for one summed spectral pair. The
record structure is the same as the table. "
END_OBJECT = SPECTRUM
END
i25a_urt_tu25nans01.xdr_1 0100666 0001257 0000335 00000011300 10606532164 015205 0 ustar laspweb galileo c K ' c K - , |N P c K - = | P z * ; c K 4 c K . | P c K . ; | P * 9 i25a_urt_tu25nans01.xlbl_2 0100666 0001257 0000335 00000021062 10606532164 015360 0 ustar laspweb galileo CCSD3ZF0000100000001NJPL3IF0PDSX00000001
/* FILE: I25A_URT_TU25NANS01.LBL */
/* VERSION 1.4: 28-OCT-2005 MOSSER */
PDS_VERSION_ID = PDS3
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 4528 /*=1132*4 */
FILE_RECORDS = 2
PRODUCT_ID = "I25A_URT_TU25NANS01.XDR"
PRODUCT_NAME = "25tu25nans01 EDR DATA"
DATA_SET_ID = "GO-J-UVS-2-EDR-JUP-V1.0"
OBSERVATION_ID = "25TU25NANS01"
SPACECRAFT_NAME = "GALILEO ORBITER"
INSTRUMENT_NAME = "ULTRAVIOLET SPECTROMETER"
MISSION_PHASE_NAME = "JUPITER ORBIT OPERATIONS"
TARGET_NAME = "IO-TORUS"
PRODUCT_CREATION_TIME = "1999-11-29"
START_TIME = 1999-331T01:45:44.986Z
STOP_TIME = 1999-331T03:46:04.317Z
SPACECRAFT_CLOCK_START_COUNT = "5274702:00:0"
SPACECRAFT_CLOCK_STOP_COUNT = "5274821:00:0"
^SPECTRUM = "I25A_URT_TU25NANS01.XDR"
DESCRIPTION = "
This file was produced by the Galileo UVS/EUV team at the Laboratory
for Atmospheric and Space Physics (LASP) at the University of Colorado
at Boulder. Refer to the Galileo UVS/EUV instrument paper 'Galileo
Ultraviolet Spectrometer Experiment', Vol 60, Space Science Reviews,
pages 503-530, by C.W. Hord et al, for hardware and calibration
information.
The data contained in the file were obtained by the UVS instrument
during Jupiter operations mission phase.
The UVS data in this file were obtained using the UVS RTS mode. Check
the commanded configuration in the flight sequence for the most
accurate understanding of these data. Calibration to physical units
has not been made; the data are in units of 'raw counts per time'.
The command instrument integration time and grating positions are
given in the header portion of the record; no attempt has been made to
verify the raw data acquired these positions in the raw EDRs.
A diagram of the file and record structure is shown below:
|-----+---------------|
1 |time | S | RTS SUMMATION
|-----+---------------| .
2 |time | S | .
|-----+---------------| .
3 |time | S | .
|-----+---------------| .
. .
. repeats .
. .
|-----+---------------| .
ij |time | S | RTS SUMMATION
|-----+---------------|
|40 4-| /S= \
|byte | /1092 \
|time | /4-byte \
|tags | /spectral \
|& hdr| / values \
Records 1 to ij are data records. Each record begins with a 160-byte
header containing 40 4-byte integer numbers. The header values are
described below, the exact definition of the time values is further
described in the Galileo document 625-610. The time tags given in
the data records refer to the time of the first integration period
included in the packet summation period; the STOP time refers to the
time of the first integration of the last RIM included in the summation
period. The LABEL START and STOP time values refer to the first
and last integrations of the full data set.
The data start at byte 161, following the header information. Each
record contains one readout (termed FLUSH in the sequences) of the
UVS Real Time Buffer (RTB). The RTB contains UVS spectra summed
by the onboard (CDS) computer. The RTB, and thus the UVS raw data
record, is arranged as a skewed pair of spectra. The duration of
the time sum is given by the data label start and stop times, and
is generally one-half hour, one hour or 24 hours but may be a subset
of these.
A UVS spectra has 546 values, the first 18 values are fidutials and
engineering operation values. The remaining 528 values are the raw
output of the spectrometer. The fidutial contains seven values equal
to 255 each. The RTB consists of 1092 values or two 546-value spectra.
The spectra are arranged in the RTB as follows:
84 values 546 values 462 values
|----------|--|----------------------------|--|--------------------|
|final part|f1| one full spectral sum |f2| 1st part of 2nd sum|
| of 2nd | | | | |
|spect.sum | | | | |
where f1 is the fidutial of the first spectra and f2 is the fidutial
of the second spectra. Eighty-four UVS values are read out in one
SCLK minor frame, 1092 values are read out in thirteen minor frames.
There are 91 minor frames in one SCLK RIM. There will be seven UVS
RTS spectral pairs summed per RIM. The first minor frame of the RIM
contains 84 UVS values set to zero therefore the summation period in
the first 84 values of the RTB is technically different from the
remaining summed data.
All values in the RTB are summed, including the fidutials and
engineering values. The 2-byte RTB rolls over and begins counting
again from value zero.
The records contents as follows:
TORUS1:[GLL_RAW.INFO]UVS_Phase2_RTS_HDR.DOC
June 21,1996 - JEREMY GEBBEN
Updated February 27, 1997 - WENDY SWEET
Updated Jul 24, 97 - Simmons
HEADER:
Earth Receipt Time
0 = Year (last 2 digits eg. 96)
1 = day of year
2 = hours
3 = minutes
4 = seconds
5 = milliseconds
Spacecraft Event time for start of integration:
6 = Year (last 2 digits eg. 96)
7 = day of year
8 = hours
9 = minutes
10 = seconds
11 = milliseconds
SCLK time for start of integration:
12 = start RIM (all realtime data starts on mf 0)
Spacecraft Event time for end of integration:
13 = Year (last 2 digits eg. 96)
14 = day of year
15 = hours
16 = minutes
17 = seconds
18 = milliseconds
SCLK time for end of integration:
19 = end RIM (all realtime data ends on mf 0)
20 = # of RTS packets that went into this array(max = 8)
Data Presence Indicators (dpi)
21-28 = dpi flags,1 for each packet
Each is a 4 byte field:
Top byte:
00 = no data missing
FF = entire packet missing
01 = data missing at end of packet
02 = data missing in middle of packet
03 = data missing at end of packet
Lower 3 bytes are only used if top byte is 01,02, or 03
In these cases, the three lower bytes are used to report
the position of the gap:
second byte: # of data words(2 bytes)
at start(0 if gap is at start)
third byte : # of data words missing
bottom byte: # of data words at end of packet
(0 if gap is at end)
29 = packet sequence # of the first packet in this set
30,31 = spare (set to -1)
32 = software version number (of IPF_RT_PROC.PRO - both UVS and EUV)
33 = commanded summation period (in RIMS)
34 = commanded number of steps in the miniscan for the first spectrum
35 = commanded number of steps in the miniscan for the second spectrum
36 = commanded initial grating position
37 = commanded number of grating steps to move to the second spectrum
38,39 = spare (set to -1)
DATA:
40-123 = data (6 integrations/RIM)
124-141 = first fiducial
142-669 = data (7 integrations/RIM)
670-687 = second fiducial
688-1131 = data (7 integrations/RIM)
1132*4=4528 byte records
........................................................"
OBJECT = SPECTRUM
NAME = "1 UVS RTS SUMMATION BUFFER"
INTERCHANGE_FORMAT = BINARY
ROWS = 2
COLUMNS = 41
ROW_BYTES = 4528
^STRUCTURE = "RTS_SUMMATION.FMT"
DESCRIPTION = "
The summation data table consists of 40 4-byte integers of time tags
(RIM, yr, doy, hr, min, sec, etc), data quality flags and spares, and
1092 spectral values for one summed spectral pair. The
record structure is the same as the table. "
END_OBJECT = SPECTRUM
END
i25a_urt_tu25nans02.dat_1 0100666 0001257 0000335 00000162760 10606532165 015203 0 ustar laspweb galileo c K . c K * 8}P c K 0 4 y}P " * : c K c K 1 z}P c K 0 , 2 }P * * ; c K c K 1 , }P c K 1 0 }P 2 * ; c K
- c K 2 }P c K 2 . -~P : * ; c K c K 3 .~P c K
2 , , i~P B * ; c K c K
3 , j~P c K 3 * ~P J * ; c K
c K 4 ~P c K 4 ( ~P R * ; c L 3 c K 5 ~P c K
4 , & P Z * ; c L c K
5 , P c K 5 # YP b * ; c L c K 6 ZP c K 6 ! P j * ; c L O c K 7 P c K 6 , P r * ; c L r c K 7 , P c K 7
P z * ; c L ) * c K 8 P c K 8 IP * ; i25a_urt_tu25nans02.lbl_1 0100666 0001257 0000335 00000021064 10606532165 015173 0 ustar laspweb galileo CCSD3ZF0000100000001NJPL3IF0PDSX00000001
/* FILE: I25A_URT_TU25NANS02.LBL */
/* VERSION 1.4: 28-OCT-2005 MOSSER */
PDS_VERSION_ID = PDS3
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 4528 /*=1132*4 */
FILE_RECORDS = 13
PRODUCT_ID = "I25A_URT_TU25NANS02.DAT"
PRODUCT_NAME = "25TU25NANS02 EDR DATA"
DATA_SET_ID = "GO-J-UVS-2-EDR-JUP-V1.0"
OBSERVATION_ID = "25TU25NANS02"
SPACECRAFT_NAME = "GALILEO ORBITER"
INSTRUMENT_NAME = "ULTRAVIOLET SPECTROMETER"
MISSION_PHASE_NAME = "JUPITER ORBIT OPERATIONS"
TARGET_NAME = "IO-TORUS"
PRODUCT_CREATION_TIME = "1999-11-29"
START_TIME = 1999-331T05:42:20.977Z
STOP_TIME = 1999-331T18:56:04.308Z
SPACECRAFT_CLOCK_START_COUNT = "5274936:00:0"
SPACECRAFT_CLOCK_STOP_COUNT = "5275721:00:0"
^SPECTRUM = "I25A_URT_TU25NANS02.DAT"
DESCRIPTION = "
This file was produced by the Galileo UVS/EUV team at the Laboratory
for Atmospheric and Space Physics (LASP) at the University of Colorado
at Boulder. Refer to the Galileo UVS/EUV instrument paper 'Galileo
Ultraviolet Spectrometer Experiment', Vol 60, Space Science Reviews,
pages 503-530, by C.W. Hord et al, for hardware and calibration
information.
The data contained in the file were obtained by the UVS instrument
during Jupiter operations mission phase.
The UVS data in this file were obtained using the UVS RTS mode. Check
the commanded configuration in the flight sequence for the most
accurate understanding of these data. Calibration to physical units
has not been made; the data are in units of 'raw counts per time'.
The command instrument integration time and grating positions are
given in the header portion of the record; no attempt has been made to
verify the raw data acquired these positions in the raw EDRs.
A diagram of the file and record structure is shown below:
|-----+---------------|
1 |time | S | RTS SUMMATION
|-----+---------------| .
2 |time | S | .
|-----+---------------| .
3 |time | S | .
|-----+---------------| .
. .
. repeats .
. .
|-----+---------------| .
ij |time | S | RTS SUMMATION
|-----+---------------|
|40 4-| /S= \
|byte | /1092 \
|time | /4-byte \
|tags | /spectral \
|& hdr| / values \
Records 1 to ij are data records. Each record begins with a 160-byte
header containing 40 4-byte integer numbers. The header values are
described below, the exact definition of the time values is further
described in the Galileo document 625-610. The time tags given in
the data records refer to the time of the first integration period
included in the packet summation period; the STOP time refers to the
time of the first integration of the last RIM included in the summation
period. The LABEL START and STOP time values refer to the first
and last integrations of the full data set.
The data start at byte 161, following the header information. Each
record contains one readout (termed FLUSH in the sequences) of the
UVS Real Time Buffer (RTB). The RTB contains UVS spectra summed
by the onboard (CDS) computer. The RTB, and thus the UVS raw data
record, is arranged as a skewed pair of spectra. The duration of
the time sum is given by the data label start and stop times, and
is generally one-half hour, one hour or 24 hours but may be a subset
of these.
A UVS spectra has 546 values, the first 18 values are fidutials and
engineering operation values. The remaining 528 values are the raw
output of the spectrometer. The fidutial contains seven values equal
to 255 each. The RTB consists of 1092 values or two 546-value spectra.
The spectra are arranged in the RTB as follows:
84 values 546 values 462 values
|----------|--|----------------------------|--|--------------------|
|final part|f1| one full spectral sum |f2| 1st part of 2nd sum|
| of 2nd | | | | |
|spect.sum | | | | |
where f1 is the fidutial of the first spectra and f2 is the fidutial
of the second spectra. Eighty-four UVS values are read out in one
SCLK minor frame, 1092 values are read out in thirteen minor frames.
There are 91 minor frames in one SCLK RIM. There will be seven UVS
RTS spectral pairs summed per RIM. The first minor frame of the RIM
contains 84 UVS values set to zero therefore the summation period in
the first 84 values of the RTB is technically different from the
remaining summed data.
All values in the RTB are summed, including the fidutials and
engineering values. The 2-byte RTB rolls over and begins counting
again from value zero.
The records contents as follows:
TORUS1:[GLL_RAW.INFO]UVS_Phase2_RTS_HDR.DOC
June 21,1996 - JEREMY GEBBEN
Updated February 27, 1997 - WENDY SWEET
Updated Jul 24, 97 - Simmons
HEADER:
Earth Receipt Time
0 = Year (last 2 digits eg. 96)
1 = day of year
2 = hours
3 = minutes
4 = seconds
5 = milliseconds
Spacecraft Event time for start of integration:
6 = Year (last 2 digits eg. 96)
7 = day of year
8 = hours
9 = minutes
10 = seconds
11 = milliseconds
SCLK time for start of integration:
12 = start RIM (all realtime data starts on mf 0)
Spacecraft Event time for end of integration:
13 = Year (last 2 digits eg. 96)
14 = day of year
15 = hours
16 = minutes
17 = seconds
18 = milliseconds
SCLK time for end of integration:
19 = end RIM (all realtime data ends on mf 0)
20 = # of RTS packets that went into this array(max = 8)
Data Presence Indicators (dpi)
21-28 = dpi flags,1 for each packet
Each is a 4 byte field:
Top byte:
00 = no data missing
FF = entire packet missing
01 = data missing at end of packet
02 = data missing in middle of packet
03 = data missing at end of packet
Lower 3 bytes are only used if top byte is 01,02, or 03
In these cases, the three lower bytes are used to report
the position of the gap:
second byte: # of data words(2 bytes)
at start(0 if gap is at start)
third byte : # of data words missing
bottom byte: # of data words at end of packet
(0 if gap is at end)
29 = packet sequence # of the first packet in this set
30,31 = spare (set to -1)
32 = software version number (of IPF_RT_PROC.PRO - both UVS and EUV)
33 = commanded summation period (in RIMS)
34 = commanded number of steps in the miniscan for the first spectrum
35 = commanded number of steps in the miniscan for the second spectrum
36 = commanded initial grating position
37 = commanded number of grating steps to move to the second spectrum
38,39 = spare (set to -1)
DATA:
40-123 = data (6 integrations/RIM)
124-141 = first fiducial
142-669 = data (7 integrations/RIM)
670-687 = second fiducial
688-1131 = data (7 integrations/RIM)
1132*4=4528 byte records
........................................................"
OBJECT = SPECTRUM
NAME = "1 UVS RTS SUMMATION BUFFER"
INTERCHANGE_FORMAT = BINARY
ROWS = 13
COLUMNS = 41
ROW_BYTES = 4528
^STRUCTURE = "RTS_SUMMATION.FMT"
DESCRIPTION = "
The summation data table consists of 40 4-byte integers of time tags
(RIM, yr, doy, hr, min, sec, etc), data quality flags and spares, and
1092 spectral values for one summed spectral pair. The
record structure is the same as the table. "
END_OBJECT = SPECTRUM
END
i25a_urt_tu25nans02.xdr_1 0100666 0001257 0000335 00000074740 10606532166 015231 0 ustar laspweb galileo c K . c K * }8 P c K 0 4 }y P " * : c K c K 1 }z P c K 0 , 2 } P * * ; c K c K 1 , } P c K 1 0 } P 2 * ; c K
- c K 2 } P c K 2 . ~- P : * ; c K c K 3 ~. P c K
2 , , ~i P B * ; c K c K
3 , ~j P c K 3 * ~ P J * ; c K
c K 4 ~ P c K 4 ( ~ P R * ; c L 3 c K 5 ~ P c K
4 , & P Z * ; c L c K
5 , P c K 5 # Y P b * ; c L c K 6 Z P c K 6 ! P j * ; c L O c K 7 P c K 6 , P r * ; c L r c K 7 , P c K 7
P z * ; c L ) * c K 8 P c K 8 I P * ; i25a_urt_tu25nans02.xlbl_3 0100666 0001257 0000335 00000021064 10606532166 015366 0 ustar laspweb galileo CCSD3ZF0000100000001NJPL3IF0PDSX00000001
/* FILE: I25A_URT_TU25NANS02.LBL */
/* VERSION 1.4: 28-OCT-2005 MOSSER */
PDS_VERSION_ID = PDS3
RECORD_TYPE = FIXED_LENGTH
RECORD_BYTES = 4528 /*=1132*4 */
FILE_RECORDS = 13
PRODUCT_ID = "I25A_URT_TU25NANS02.XDR"
PRODUCT_NAME = "25tu25nans02 EDR DATA"
DATA_SET_ID = "GO-J-UVS-2-EDR-JUP-V1.0"
OBSERVATION_ID = "25TU25NANS02"
SPACECRAFT_NAME = "GALILEO ORBITER"
INSTRUMENT_NAME = "ULTRAVIOLET SPECTROMETER"
MISSION_PHASE_NAME = "JUPITER ORBIT OPERATIONS"
TARGET_NAME = "IO-TORUS"
PRODUCT_CREATION_TIME = "1999-11-29"
START_TIME = 1999-331T05:42:20.977Z
STOP_TIME = 1999-331T18:56:04.308Z
SPACECRAFT_CLOCK_START_COUNT = "5274936:00:0"
SPACECRAFT_CLOCK_STOP_COUNT = "5275721:00:0"
^SPECTRUM = "I25A_URT_TU25NANS02.XDR"
DESCRIPTION = "
This file was produced by the Galileo UVS/EUV team at the Laboratory
for Atmospheric and Space Physics (LASP) at the University of Colorado
at Boulder. Refer to the Galileo UVS/EUV instrument paper 'Galileo
Ultraviolet Spectrometer Experiment', Vol 60, Space Science Reviews,
pages 503-530, by C.W. Hord et al, for hardware and calibration
information.
The data contained in the file were obtained by the UVS instrument
during Jupiter operations mission phase.
The UVS data in this file were obtained using the UVS RTS mode. Check
the commanded configuration in the flight sequence for the most
accurate understanding of these data. Calibration to physical units
has not been made; the data are in units of 'raw counts per time'.
The command instrument integration time and grating positions are
given in the header portion of the record; no attempt has been made to
verify the raw data acquired these positions in the raw EDRs.
A diagram of the file and record structure is shown below:
|-----+---------------|
1 |time | S | RTS SUMMATION
|-----+---------------| .
2 |time | S | .
|-----+---------------| .
3 |time | S | .
|-----+---------------| .
. .
. repeats .
. .
|-----+---------------| .
ij |time | S | RTS SUMMATION
|-----+---------------|
|40 4-| /S= \
|byte | /1092 \
|time | /4-byte \
|tags | /spectral \
|& hdr| / values \
Records 1 to ij are data records. Each record begins with a 160-byte
header containing 40 4-byte integer numbers. The header values are
described below, the exact definition of the time values is further
described in the Galileo document 625-610. The time tags given in
the data records refer to the time of the first integration period
included in the packet summation period; the STOP time refers to the
time of the first integration of the last RIM included in the summation
period. The LABEL START and STOP time values refer to the first
and last integrations of the full data set.
The data start at byte 161, following the header information. Each
record contains one readout (termed FLUSH in the sequences) of the
UVS Real Time Buffer (RTB). The RTB contains UVS spectra summed
by the onboard (CDS) computer. The RTB, and thus the UVS raw data
record, is arranged as a skewed pair of spectra. The duration of
the time sum is given by the data label start and stop times, and
is generally one-half hour, one hour or 24 hours but may be a subset
of these.
A UVS spectra has 546 values, the first 18 values are fidutials and
engineering operation values. The remaining 528 values are the raw
output of the spectrometer. The fidutial contains seven values equal
to 255 each. The RTB consists of 1092 values or two 546-value spectra.
The spectra are arranged in the RTB as follows:
84 values 546 values 462 values
|----------|--|----------------------------|--|--------------------|
|final part|f1| one full spectral sum |f2| 1st part of 2nd sum|
| of 2nd | | | | |
|spect.sum | | | | |
where f1 is the fidutial of the first spectra and f2 is the fidutial
of the second spectra. Eighty-four UVS values are read out in one
SCLK minor frame, 1092 values are read out in thirteen minor frames.
There are 91 minor frames in one SCLK RIM. There will be seven UVS
RTS spectral pairs summed per RIM. The first minor frame of the RIM
contains 84 UVS values set to zero therefore the summation period in
the first 84 values of the RTB is technically different from the
remaining summed data.
All values in the RTB are summed, including the fidutials and
engineering values. The 2-byte RTB rolls over and begins counting
again from value zero.
The records contents as follows:
TORUS1:[GLL_RAW.INFO]UVS_Phase2_RTS_HDR.DOC
June 21,1996 - JEREMY GEBBEN
Updated February 27, 1997 - WENDY SWEET
Updated Jul 24, 97 - Simmons
HEADER:
Earth Receipt Time
0 = Year (last 2 digits eg. 96)
1 = day of year
2 = hours
3 = minutes
4 = seconds
5 = milliseconds
Spacecraft Event time for start of integration:
6 = Year (last 2 digits eg. 96)
7 = day of year
8 = hours
9 = minutes
10 = seconds
11 = milliseconds
SCLK time for start of integration:
12 = start RIM (all realtime data starts on mf 0)
Spacecraft Event time for end of integration:
13 = Year (last 2 digits eg. 96)
14 = day of year
15 = hours
16 = minutes
17 = seconds
18 = milliseconds
SCLK time for end of integration:
19 = end RIM (all realtime data ends on mf 0)
20 = # of RTS packets that went into this array(max = 8)
Data Presence Indicators (dpi)
21-28 = dpi flags,1 for each packet
Each is a 4 byte field:
Top byte:
00 = no data missing
FF = entire packet missing
01 = data missing at end of packet
02 = data missing in middle of packet
03 = data missing at end of packet
Lower 3 bytes are only used if top byte is 01,02, or 03
In these cases, the three lower bytes are used to report
the position of the gap:
second byte: # of data words(2 bytes)
at start(0 if gap is at start)
third byte : # of data words missing
bottom byte: # of data words at end of packet
(0 if gap is at end)
29 = packet sequence # of the first packet in this set
30,31 = spare (set to -1)
32 = software version number (of IPF_RT_PROC.PRO - both UVS and EUV)
33 = commanded summation period (in RIMS)
34 = commanded number of steps in the miniscan for the first spectrum
35 = commanded number of steps in the miniscan for the second spectrum
36 = commanded initial grating position
37 = commanded number of grating steps to move to the second spectrum
38,39 = spare (set to -1)
DATA:
40-123 = data (6 integrations/RIM)
124-141 = first fiducial
142-669 = data (7 integrations/RIM)
670-687 = second fiducial
688-1131 = data (7 integrations/RIM)
1132*4=4528 byte records
........................................................"
OBJECT = SPECTRUM
NAME = "1 UVS RTS SUMMATION BUFFER"
INTERCHANGE_FORMAT = BINARY
ROWS = 13
COLUMNS = 41
ROW_BYTES = 4528
^STRUCTURE = "RTS_SUMMATION.FMT"
DESCRIPTION = "
The summation data table consists of 40 4-byte integers of time tags
(RIM, yr, doy, hr, min, sec, etc), data quality flags and spares, and
1092 spectral values for one summed spectral pair. The
record structure is the same as the table. "
END_OBJECT = SPECTRUM
END
index.php 0100666 0001257 0000335 00000000746 10613261605 012545 0 ustar laspweb galileo
GALILEO SPACECRAFT TO JUPITER
";
for($i=0; $i<=count($files); $i++)
{
$file=$files[$i];
if ($file != '.' && $file != '..' && $file[0] != '.' && !stristr($file, 'index'))
{
echo"$file";
}
}
?>