DQR ID | Subject | Data Streams Affected |
---|---|---|
D000127.1 | TWP/MWR/C2 - Uncertainty in clock time | twpmwrlosC2.b1, twpmwrtipC2.a1 |
D001004.1 | TWP/MWR/C2 - damaged teflon window | twpmwrtipC2.a1 |
D010227.4 | TWP/MWR/C2 - Excessive wet_window flags | twpmwrlosC2.b1, twpmwrtipC2.a1 |
D040211.4 | TWP/MWR/C2 - thermal instability | twpmwrlosC2.b1, twpmwrtipC2.a1 |
D040920.1 | TWP/MWR/C2 - Data collection problem | twpmwrC2.00, twpmwrlosC2.b1, twpmwrtipC2.a1 |
D050928.2 | TWP/MWR/C2 - New software version (4.15) installed | twpmwrlosC2.b1, twpmwrtipC2.a1 |
Start Date | Start Time | End Date | End Time |
---|---|---|---|
11/06/1998 | 0000 | 07/30/1999 | 2359 |
Subject: | TWP/MWR/C2 - Uncertainty in clock time |
DataStreams: | twpmwrlosC2.b1, twpmwrtipC2.a1 |
Description: | At ARCS2, the MWR computer clock was not being updated because no NTP time service software was installed on the computer. During Nauru99, on 6/24/99, the clock was found to be 3 minutes and 17 seconds fast. Assuming that the time was properly set at installation on 10/26/98 (which is not indicated in the installation report) and never reset until 6/24/99, the rate of time drift on the computer was about +0.8 seconds per day. However, if the time was not reset since integration at AIS on 1/14/98 (which is recorded in my integration notes), then the rate of drift is about +0.4 seconds per day. The computer was replaced and time service started on 7/30/99. |
Measurements: | twpmwrlosC2.b1:
twpmwrtipC2.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
04/10/2000 | 0300 | 06/27/2000 | 2200 |
Subject: | TWP/MWR/C2 - damaged teflon window |
DataStreams: | twpmwrtipC2.a1 |
Description: | From the RESET11N daily report for 11Apr00: At around 15:00 (4/10/00) it was noticed that the 50hz outside power breaker was tripped. When it was reset to get the WSI running the MWR heater smoked. The heater and cable burned out. The Teflon window sustained damage and needs replacing. From the RESET11N daily report for 27Jun00: 22:00GMT(26JUN) - Replaced the MWR window. DM |
Measurements: | twpmwrtipC2.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/16/1999 | 0900 | 03/08/1999 | 2100 |
11/16/1999 | 0900 | 02/09/2000 | 2100 |
12/07/2000 | 0000 | 12/17/2000 | 2359 |
Subject: | TWP/MWR/C2 - Excessive wet_window flags |
DataStreams: | twpmwrlosC2.b1, twpmwrtipC2.a1 |
Description: | The wet_window flag is set high more than expected from the measured value of liquid water path. This may be caused by dew or, if the heater sensivity is slightly misadjusted, by the diurnal variation in ambient temperature. The "wet_window" flag is an indicator of moisture on the MWR window which invalidates the measurements of precipitable water vapor and liquid water path. Sometimes this flag can be incorrectly set high or low if the heater sensivity is slightly misadjusted. The heater adjustment is a resistive device that is dependent on ambient temperature. Another indicator of moisture on the window is unreasonably high ( > 3*liquid_retrieval_rms_accuracy ) values of "liq". |
Measurements: | twpmwrlosC2.b1:
twpmwrtipC2.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
01/27/2004 | 1958 | 01/31/2004 | 2059 |
Subject: | TWP/MWR/C2 - thermal instability |
DataStreams: | twpmwrlosC2.b1, twpmwrtipC2.a1 |
Description: | The MWR required an unusually long time to reach thermal stability after a 4-day outage due to a power failure that damaged the blower/heater assembly. Also during this period, the heater, which had been replaced, appears to have been on continously, causing the data to be inappropriately flagged. |
Measurements: | twpmwrlosC2.b1:
twpmwrtipC2.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
08/27/2004 | 2000 | 09/24/2004 | 0219 |
Subject: | TWP/MWR/C2 - Data collection problem |
DataStreams: | twpmwrC2.00, twpmwrlosC2.b1, twpmwrtipC2.a1 |
Description: | Large, frequent data gaps occurred due to a failing laptop computer. The problem was corrected when a new computer was installed. |
Measurements: | twpmwrlosC2.b1:
twpmwrC2.00:
twpmwrtipC2.a1:
|
Start Date | Start Time | End Date | End Time |
---|---|---|---|
11/01/2002 | 2101 | 09/15/2005 | 1424 |
Subject: | TWP/MWR/C2 - New software version (4.15) installed |
DataStreams: | twpmwrlosC2.b1, twpmwrtipC2.a1 |
Description: | A problem began with the installation of MWR.EXE version 4.12 in November 2002. The software had been upgraded from a "DOS" to a "Windows"-compiled program to address an earlier problem. The software upgrade corrected the earlier problem but introduced a new one that caused line-of-sight observing cycles to be skipped, a 15% reduction in the number of tip curves, and saturation of CPU usage. Software versions 4.13 and 4.14 also produced these problems. The new MWR software version (4.15) was installed on 9/15/2005. As a consequence of this upgrade, the tip curve frequency increased. The tip cycle time decreased from ~60s to ~50s. |
Measurements: | twpmwrlosC2.b1:
twpmwrtipC2.a1:
|