********************************************************************
UARS WEEKLY STATUS REPORT 07 MAY 1999
********************************************************************
***********
SOLSTICE
***********
Nothing received.
***********
SUSIM
***********
Nothing received.
***********
PEM
***********
PEM is active under PMON control. The FOT and the PEM team are
completing close-out documentation on this problem; however progress has
been hampered with the departure of Peter Thomas.
While under PMON control, the PEM instrument computes energy deposition
from the particle spectrometers.
***********
HALOE
***********
Nothing received.
***********
MLS
***********
The instrument is now off as scheduled. MLS is scheduled to begin south viewing
operations on May 11 and operate through May 28.
**********************************************************************
Announcement of UARS MLS Version 5 Data Availability
**********************************************************************
UARS MLS Version 5 data are now becoming available at the UARS CDHF. The
following UARS months are on the CDHF at time of writing this message
(29 April 1999):
92_07
93_03
94_02
96_02
The Version 5 processing status can be obtained from the MLS web site
(http://mls.jpl.nasa.gov) by clicking on "UARS MLS Data" and then on "Pointers
to Information on UARS MLS Version 5 Data" - or directly from
http://mls.jpl.nasa.gov/lucien/v5_status_proc_order.html.
Barring unforeseen circumstances, processing of MLS V5 data for the entire UARS
mission is expected to be completed by Oct-Nov 1999.
There are 9 atmospheric parameters produced by MLS Version 5 processing and put
in L3AT/L3AL files (however, no L3AL files are produced for UTH - see below).
These parameters, and the MLS scientist responsible for their validation, are:
* temperature (TEMP) - D.L. Wu, dwu@mls.jpl.nasa.gov
* O3 from 205 GHz (O3_205) - L. Froidevaux, lucien@mls.jpl.nasa.gov
* O3 from 183 GHz (O3_183) - L. Froidevaux, lucien@mls.jpl.nasa.gov
* stratospheric water vapor (H2O) - H.C. Pumphrey, hcp@met.ed.ac.uk
The H2O files also contain troposphere H2O mixing ratios at 147, 215, 316 and
464 hPa for which W.G. Read is responsible. However it should be emphasized
that the tropospheric H2O and the stratospheric H2O in these files are from
different radiometers, and that consistency between these two data sets in the
region of the tropopause has *not* been achieved. The 'Level 2' ASCII file
(described below) is recommended for upper trop H2O data because it contains
more information for screening bad data points.
* chlorine monoxide (ClO) - J.W. Waters, joe@mls.jpl.nasa.gov
* nitric acid (HNO3) - M.L. Santee, mls@mls.jpl.nasa.gov
* upper tropospheric humidity (UTH) - W.G. Read, bill@mls.jpl.nasa.gov
However, as mentioned above, the 'Level 2' ASCII file described below is
recommended for UTH since it contains additional info for screening bad data.
* methyl cyanide (CH3CN) - N.J. Livesey, livesey@mls.jpl.nasa.gov
* geopotential height (GPH) - D.L. Wu, dwu@mls.jpl.nasa.gov
In addition to the Level 3 files for UTH (which give upper tropospheric
humidity in terms of relative humidity with respect to ice at 147, 215, 315 and
464 hPa - using NCEP temperatures), a "Level 2" UTH ASCII file is available
which gives the corresponding water vapor mixing ratios, NCEP temperatures, and
other information useful for diagnosing the MLS UTH data. The header to the
ASCII file contains information that should be sufficient for understanding its
contents.
Besides CH3CN and GPH, which are new products still being validated, the
primary changes in MLS Version 5 data from earlier versions are:
(1) retrieved values are produced at the full resolution of the UARS surfaces,
six points per decade change in pressure, over most of the useful vertical
range for each parameter,
(2) improved treatment of coupled temperature and tangent point retrievals
(3) refinements in spectroscopy and estimated instrument sideband responses for
some bands,
(4) iterative retrievals in some bands (also done in the previously released
"V4.90" UTH data)
The main changes in retrieved geophysical parameters, from those in previous
MLS Data Versions, are:
(a) a generally wider range of pressures for reliable results
(b) useful temperature data now extend into the mesosphere, but with a gap
between ~0.46 and ~0.2 hPa where values are *not* reliable,
(c) O3_205 data have better accuracy, particularly in the lower stratosphere -
the biases in Version 4 have generally been removed,
(d) ClO data are generally improved in the lower stratosphere, although there
still may be some remaining biases at the ~0.1-0.2 ppbv abundance level,
(e) HNO3 data are improved, and now cover the range from 100 to 10 hPa,
(f) Stratospheric H2O data are now useful down to 68 hPa (100 hPa values
given in the files are *not* reliable),
(g) O3_183 data have more sensitivity in the lower stratosphere but the 68 hPa
and 100 hPa values are not considered reliable at low latitudes (mainly
20S-20N)
because of remaining systematic bias artifacts.
The major difference between the V5 UTH values and the previously-released
V4.90 data is that empirical parameters in the V5 H2O continuum emission
expressions are determined using coincident Vaisala sonde H2O profiles,
whereas V4.90 assumed 100% relative humidity for certain situations where
maximum radiances were used in deriving the empirical parameters.
This leads to the V5 relative humidities being, on the average, lower than
V4.90, by the follwoing amounts:
* 22% at 147 hPa
* 12% at 215 hPa
* 14% at 316 hPa
* 14% at 464 hPa
In addition to noting the caveats mentioned earlier in this message, and the
single-profile estimated precisions included in the data files, screeening for
bad data in the files should follow the same procedures as in previous MLS data
versions:
* only use data from records for which the corresponding MMAF_STAT (in the
appropriate L3PT/L3PL files) equals "G", "T", or "t",
* only use data where the estimated precision (in the L3AT/L3AL files) has
a positive value,
* only use data where the quality indicator (in the L3PT/L3PL files), e.g.
"QUALITY_CLO", has value "4".
The following additions apply to the new data products
* use "QUALITY_CLO" as the quality indicator for CH3CN as it is from the
same spectral band as ClO,
* use "QUALITY_TEMP" (quality indicator for temperature) as the quality
indicator for geopotential height. There may be additional screening for
geopotential height that will be needed due to spacecraft attitude effects, but
these have not been included in the data set and users of this product should
keep in close communication with the MLS team in regards to potential bad data
which are not indentified by our existing flags,
* for UTH:
--clip all data at ~120% relative humidity to reduce the effects of clouds
--reject 316 hPa and 464 hPa values when "single_layer_rh" (a quantity given in
the Level 2 ASCII file) minus the retrieved relative humidity value is
greater than 5.0.
More information on remaining known systematic artifacts and details for each
parameter will be discussed in a "Data Quality Document" to be prepared by the
MLS team, and expected to be available in summer 1999. A publication
describing the Version 5 data and its quality is also planned on a somewhat
longer time scale.
Sulfur dioxide is not produced in Version 5 due to complications of the CH3CN
retrieval, and Version 5 CH3CN values will be contaminated by Pinatubo SO2 for
the period of ~Sep-Nov 1991, and the Lascar volcano SO2 for a local region over
South America on 21 and 22 April 1993.
Temperature variances at gravity-wave scales have also been produced as a
special product, but are not being produced as part of routine reprocessing.
Contact Dr. Dong Wu (dwu@mls.jpl.nasa.gov) for information on these data.
***********
HRDI
***********
Nothing reecived.
***********
WINDII
***********
Nothing received.
***********
MPG
***********
Routine processing of instrument Daily Activity Plans continues
with no problems. The MPG continues to assist the Project
Scientist with the scheduling of instrument operations.
***********
CDHF
***********
The CDHF processed current day data through level 3 for all active
instruments. Additionally, CDHF personnel reprocessed: (R)= Requested
(C) = Complete, (F)= Failed (L) = Days remaining to reprocess.
2 days CLA (7.0) PROD (TEST) (L1-L3) (3R-3C=0L)
50 days PEM (3.32) PROD (OA-L2) (760R-628C-1F=131L)
1 day SEN (5.0) PROD (1R-1C=0L)
127 days WIN (5.11) PROD (LOG) (2014R-1430C=584L)
52 days WIN (5.11) PROD (L1-L3) (2014R-391-3F=1620L)
The CDHF participated in the Y2K end-to-end testing on 04/29/99.
Three level 0 day groups were received and ingested into the Development
System. The UARS days of the ingests were 3034, 3093 and 3399.
SOLSTICE Wall Clock time increase.
"Efforts diverted on the rehosting and Y2K areas."
CDHF pending software upgrades: DEC AXP Fortran 6.5, DEC AXP OPEN
VMS 6.2, OpenIngres.
***********
FOT
***********
REPORTING PERIOD
This report covers 24 April 1999 (Orbit 41620, GMT Day 114) through 30 April
(GMT Day 120).
The observatory is now in Forward Flight (Southern Hemisphere viewing)
performing nominally under two-battery operations. The instrument
operational changes were:
INSTRUMENT OPERATIONAL CHANGES
Instrument Time Orbit Comment
WINDII 115/0246 41636 On
WINDII 116/2042 41662 Off
HALOE 117/2343 41679 Off
WINDII 118/0155 41680 On
PEM 118/1541 41689 AXIS-1 Off
WINDII 119/2346 41709 Off
The beta angle ranged between the angles of 30.0 degrees to 2.1 degrees for
this report period. The beta angle is now increasing toward a maximum
angle of 77 degrees on 21 May 1999 (DOY 141).
A Reverse-to-Forward Yaw Around maneuver (number 78) was successfully
executed in Orbit 41719 beginning 120/14:41:20 and completing at
120/15:18:30 on 30 April 1999. The SSPP Instruments (ACRIM, SOLSTICE,
SUSIM) were enabled as well as HRDI and PEM in day only operations. Due to
the SA position at 269 degrees, the effective night length of the
spacecraft after the maneuver was approximately 54 minutes. Post maneuver
analysis of data indicate that during the Yaw Around, the end-of-night load
bus voltage was 24.5 volts and the average depths of discharge (DODs) on
Batteries 2 and 3 were approximately 22.5 and 22.0 percent respectively.
The next (forward-to-reverse) YAW is scheduled for 11 June 1999 (DOY 162).
Two manually generated Stellar offset maneuvers were performed on GMT days
118 and 119 at the request of SOLSTICE operations. The offsets are similar
to the normal weekly SOLSTICE offset which usually occurs during a Solar
tracking session.
Extra ( eleven) SOLSTICE Solar Offset experiments were performed this week
(spanning days 121 through 126) at the request of SUSIM.
Spacecraft battery 1, 2, and 3 performance monitoring continues. Battery 1
remains OFF the charge relay. Battery 2 and Battery 3 are currently
maintaining greater than 23.8 V end-of-night (EON) load bus voltage.
Battery temperatures are stable with a temperature delta between Battery 2
and Battery 3 of 1.0 to 1.3 degrees C. Additional battery performance data
for each battery on 23 April 1999 and 30 April 1999 are provided in
Appendix D.
The clock error ranged from -10.0 to 9.8 msec during this report period.
Clock rate adjustments are listed in Appendix C.
All instrument and subsystem engineers were advised on the initial
excursion of ALERTS or Out-Of-Limits conditions detected by the FOT for
this report. A summary is listed below and the details of ALERT and Out-
Of-Limits occurrences are listed in Appendix B.
% ALERTS = 00
% OUT-OF-LIMITS = 02
The following real-time command sheets were executed for the listed
operational element(s) during this report period (see Appendix A).
% FOT 03
% HRDI 01
% PEM 02
% WINDII 01
UARS Anomaly Reports initiated during this ined OPEN at the end of this reportNSPONDER FREQUENCIES:
Transponder A: 99/054 - 2287.496923
Transponder B: 99/055 - 2287.498750
GROUND SYSTEM OPERATION
Two (2) operational support problems occurred this period. Anomaly Reports
are included in Appendix E.
DATA LOSS FOR WEEK 17
The data loss calculations supplied by Data Capture Facility (DCF) from
mission start through UTC Day 99/112 show the observatory data loss to be
24 hours, 12 minutes, 17.396 seconds (an increase of 1 hour 24 minutes and
30.592 seconds since the last report period). This is a 0.0364 percent
data loss which equals a 99.9636 percent data capture for the mission.
The increase of 1 hour 24 minutes and 30.592 seconds occurred on Day 112
and was due to the unexpected spacecraft antenna slew reported in last
weekUs report.
DATA LOSS FOR WEEK 18
The data loss calculations supplied by Data Capture Facility (DCF) from
mission start through UTC Day 99/119 show the observatory data loss to be
24 hours, 12 minutes, 36.660 seconds (an increase of 19.264 seconds since
the last report period). This is a 0.0363 percent data loss which equals a
99.9637 percent data capture for the mission.
The increase of 19.264 seconds occurred over five (5) days:
7 0.544 seconds on Day 113 due to data hit,
7 3.008 seconds on Day 114 due to insufficient overlap,
7 6.720 seconds on Day 115 due to insufficient overlap
7 8.768 seconds on Day 116 due to insufficient overlap, and
7 0.224 seconds on Day 117 due to data hit.
The FOT is still awaiting the delivery of the 8-week Ground Track Y2K test
file from FDF. This file was expected to be delivered this week, but was
not received as of the end of this reporting period.
The FOT received several UPS processing errors that it had never seen
before while generating the Day 137-143 TDRS Forecast Schedule on 30 April.
Although the errors did not prevent the generation of the TDRS requests,
the FOT was concerned because the errors appeared to be indicating a
problem with the UPS. The FOT notified the UPS software development team,
who are currently investigating the error messages.
OTHER SIGNIFICANT EVENTS
UARS SATELLITE OPERATIONS
FOT personnel are supporting the IMOC (SCS-21) development effort. The
current work is a continuation of the SCS-21 UARS implementation effort
done last year which culminated in a level 1 demonstration.
The FOT continues to investigate the feasibility of a new PMON action to
change battery V/T curves based on loading to mitigate battery risks in sun
pointing safehold.
YEAR 2000 OPERABILITY SUPPORT - No change
UARS PROPULSION MODULE B/D THRUSTER LINE FILL - No change
MEETINGS
FOT supported the weekly IMOC meeting on 30 April 1999.
FUTURE SIGNIFICANT EVENTS
The next UARS Yaw Around Maneuver (forward-to-reverse) is scheduled for 11
June 1999 (DOY 162).
PERSONNEL CHANGES
None
Attachments: Appendix A, Real-time Commands Sheets
Appendix B, Out-Of-Limits & ALERT Occurrences
Appendix C, Clock & Solar Array Rate Corrections
Appendix D, UARS Battery Performance Data
Appendix E, UARS Anomaly Reports
APPENDIX A
REAL-TIME COMMAND SHEETS
Week ending 30 April 1999
ORBIT AOS NO. SUBSYS REASON
----- --- --- ------ -------
41620 114/0156 99-147 OBC Clk Adj 0.00 to 20.6 msec/day
41636 115/0246 99-148 WINDII Power ON
41638 115/0607 99-149 OBC Clk Adj 20.6 to 0.00 msec/day
41662 116/2042 99-150 WINDII Power OFF
41679 117/2343 99-151 HALOE Power OFF
41680 118/0155 99-152 WINDII Power ON
41689 118/1541 99-153 AXIS 1 Power OFF
41708 119/2201 99-154 HRDI Additional MPLs
41709 119/2346 99-155 WINDII Power OFF
41718 120/1407 99-156 MACS YAW REV to FWD
_______________________________________________________________
APPENDIX B
OUT-OF-LIMITS & ALERTS OCCURRENCES
Week ending 30 April 1999
MNEMONIC STATE DESCRIPTION ORBITS
--------- ----- ------------ ------
HRPTSPBIMON Y-HI PTS Pulse Bus Current Mon 41620-25
HRPTSPBIMON R-LO PTS Pulse Bus Current Mon 41649
The following ALERT occurrences were detected:
MNEMONIC DESCRIPTION ORBITS
--------- ------------ ------
None this report period
_______________________________________________________________
APPENDIX C
CLOCK & SOLAR ARRAY RATE CORRECTIONS
Week ending 30 April 1999
CLOCK DRIFT RATE ADJUSTMENTS
ORBIT TIME CLOCK RATE CHANGE
----- ---- -----------------
41620 114/02:01 (23 Apr 99) from 00.0 to 20.6 msec/day
41638 115/06:16 (25 Apr 99) from 20.6 to 00.0 msec/day
_______________________________________________________________
APPENDIX D
UARS BATTERY PERFORMANCE DATA
Week ending 30 April 1999
23 Apr 1999 - GMT Day 113 Beta = 30.0 deg, SA Pos = 269 deg
DIFF V (mV) TEMP (C) CURR (amp) EON V AVE C/D AVE
BAT MAX/MIN MAX/MIN MAX/MIN MIN RATIO DOD(%)
--- ------------ ---------- ----------- ------- ------- ------
1 -67.2/-89.6 -3.05/-4.31 +0.0/ +0.0 16.6 0.000 0.0
2 +56.0/-5.6 +6.11/+4.51 +30.4/-15.2 24.8 1.021 22.0
3 +44.8/-11.2 +5.15/+3.23 +29.6/-15.6 24.8 1.024 21.7
30 Apr 1999 - GMT Day 120 Beta = 2.1 deg, SA Pos = 269 deg
DIFF V (mV) TEMP (C) CURR (amp) EON V AVE C/D AVE
BAT MAX/MIN MAX/MIN MAX/MIN MIN RATIO DOD(%)
--- ------------ ---------- ----------- ------- ------- ------
1 -72.8/-95.2 -3.68/-4.62 +0.0/ +0.0 16.6 0.000 0.0
2 +44.8/-5.6 +5.47/+4.51 +31.6/-14.4 24.2 1.014 21.4
3 +33.6/-67.2 +4.51/+3.23 +31.2/-15.2 24.0 1.016 21.0
V/T LEVEL CHANGES
ORB# TIME LVL FR-TO
----- -------- ----------
no changes V/T 5
APPENDIX E
UARS ANOMALY REPORTS
Week ending 30 April 1999
NEW ANOMALY REPORTS GENERATED
AR NO. SUBSYS ORBIT TIME TTR PROBLEM/DATA LOSS
------ ------ ----- ---- --- -----------------
99-016 FOT 41683 118/0619 14170 Generic Late Acq.
ANOMALY CLOSURE INFORMATION RECEIVED
AR NO. SUBSYS ORBIT TIME TTR PROBLEM/DATA LOSS
------ ------ ----- ---- --- -----------------
99-019 FOT 41573 110/2154 20772 NASCOM PDP Failure
99-020 HRDI 41560 110/0051 N/A HRDI
99-021 HRDI 41589 112/0058 N/A HRDI IN PMON MODE
99-022 FOT 41603 112/2149 N/A Data Loss
ANOMALY INVESTIGATION REPORTS GENERATED
AIR NO. SUBSYS ORBIT TIME TTR PROBLEM/DATA LOSS
------- ------ ----- ---- --- -----------------
None this report period
OPEN ANOMALY REPORTS
AR NO. SUBSYS ORBIT TIME TTR PROBLEM/DATA LOSS
------ ------ ----- ---- --- -----------------
99-016 FOT see list Apr 99 14170 Generic Late Acq
SEVNTFW99/18