The numbers appearing in fields 32 -35 of the raw data files
have the following definitions. Note that a zero in any of
these fields implies no comment was specified.
These data have been checked for encoder
ambiguities register misassignments, and satellite
velocity correction problems. There appear to be no
reduction anomalies, unless other comments
have been applied to this observation.
These scans were reduced with a stellar velocity other than the
velocity appearing in the catprint header. For a more complete
list, see the stellar radial velocities used in data reduction;
located in the OAO room.
The slit was pulsed from 24 microns to 96 microns in a glitch.
In orbit 131 times 11h 21m 39s to 11h 45m 15s are affected. In
orbit 1877 times 02h 59m 23s to 03h 03m 19s are affected. The
time of glitch before orbits 3981 and 3982 is unknown and both
orbits are affected. See operations reports and data reduction
printouts for further details.
A star tracker was gimbled during this orbit, moving the star off
the slit. See the data reduction printout, calcomps and
operations reports, or the stack 'data' printout for the positions
of the count reduction.
These data were reduced with a stellar radial velocity other than
the velocity that appears in the catprint header. Check the chart
entitled 'RADIAL VELOCITIES USED IN DATA REDUCTION' located in
the OAO room.
Either the first few or the last few points of this scan are
invalid due to glitches.
The positions of the carriages were known to be incorrect (not
ambiguous) for these scans.
Note - 2.1 km/sec was used as the 'STELLAR VELOCITY' for all
Jupiter observations.
Unlike HD 75821 and HD 72108 a stellar velocity of 0.0km/sec was
used to reduce HD 74455.
A single set of coordinates was used to reduce all of the Lyman
Alpha data so that the wavelengths are not consistent through the
various observations.
Kohoutek observations were reduced to geocentric wavelengths.
These data were reduced to heliocentric wavelengths.
These line scans were made during a rapid data acquisition test.
At the beginning or end of this orbit, several points are
substantially lower than the others - presumably because
observations were begun before settling was complete.
A glitch occurred during this orbit in which the registers were
scrambled. It was also reported that the slit was pulsed, but
the U1 signal did not seem to increase markedly. The first 2
scans are 'NORMAL', with V1 off. The register assignments were
as follows - U2,blank,V3,V1,U3,V2, and U1. after the glitch, the
pattern was - U2,U1,V3(?),V1(?),U1,U2,U1. Erratic signal is
present in the register previously assigned to V1. The entire
orbit was reduced with the 'NORMAL' register assignments, so that
the counts designated as U3, and V2, were really U1 and U2
respectively, (After the glitch).
The particle backgrounds have been entered before writing to the
disk, at the same time the GSFC tapes were reduced. Some points
in the scan are near the anomaly, and therefore the background
values are not reliable. U.JENKINS.FULL.TABLE.NU03 was used.
The particle backgrounds have been entered before writing to the
disk, at the same time the GSFC tapes were reduced.
U.JENKINS.FULL.TABLE.NU03 was used.
The particle backgrounds have been corrected using program
"NANCHK." Some points are near the anomaly, and therefore the
background values are not very reliable.
U.JENKINS.FULL.TABLE.NU03 was used.
The particle backgrounds have been corrected using program
"NANCHK." U.JENKINS.FULL.TABLE.NU03 was used. No backgrounds
should be in error due to being too close to the anomaly.
The particle backgrounds have been entered before writing to the
disk, at the same time the GSFC tapes were reduced. Some points
in the scan are near the anomaly, and therefore the background
values are not very reliable. U.JENKINS.FULL.TABLE.NU03 was used.
The U2 stray light and U2 scattered light have been corrected
where possible, using the algorithm described in the memo of
3/26/74 from D.G. York to users of Copernicus data.
The particle backgrounds have been entered before writing to the
disk, at the same time the GSFC tapes were reduced.
U.JENKINS.FULL.TABLE.NU03 was used. The U2 stray light and U2
scattered light have been corrected where possible, using the
algorithm described in the memo of 3/26/74 from D.G. York to
users of Copernicus data.
The particle backgrounds have been corrected using program
"NANCHK." Some points are near the anomaly, and therefore the
background values are not very reliable.
U.JENKINS.FULL.TABLE.NU03 was used. The U2 stray light and U2
scattered light have been corrected where possible, using the
algorithm described in the memo of 3/26/74 from D.G. York to
users of Copernicus data.
The particle backgrounds have been corrected using program
"NANCHK." The U2 stray light and U2 scattered light have been
corrected where possible, using the algorithm described in the
memo of 3/26/74 from D.G. York to users of Copernicus data.
The background for this scan, which was written by the basic
reduction program, may be in error by about 5% for one of several
reasons. (Some scans to which this comment is being applied have
had no background applied - so the comment can be ignored] These
are a few V1, V3, and U3 scans - check catprint status column).
The wavelength of this scan appears to be a substitution in the
astronomical sequence list as it exists in our files.
This scan appears to be an addition to the astronomical sequence
list as it exists in our files.
The beginning observation time of this scan differs from schedule
time by 5 to 30 minutes.
The beginning time of this scan differs from schedule time by
more than 30 minutes.
These calibration scans were not detected by the reduction program.
The carriage 2 encoders were ambiguous for these orbits - but
carriage was correctly positioned.
During the duration of this scan the satellite failed to keep the
star on the slit. USE THIS DATA AT YOUR OWN RISK.
This observation may be incomplete as the observing program may
not have been run to completion.
This observation may be incomplete as the observing program may
not have been run to completion. Also the velocity in the may be
different from the actual reduction velocity. Check the reduction
printout for the correct velocity.
Alpha Aur and Beta Tau are the same star, but have been given
different star numbers.
During these GMT times carriage one was out of position. Data no
good.
Scan may contain bad points - consult short frame printouts for
QFD176 - QFD187.
Follow Us
