PYE/TSI/M1 - Misalignment

The TSI was not aligned with true north.

• JPG data stream - documentation not supported(JPEG data stream - documentation not yet available)

• Pixel count: number opaque in horizon area(region.horizon.count.opaque)
• Pixel count: number total in horizon area(region.horizon.count)
• Pixel count: number total in sun circle(region.sun.count)
• Pixel count: number opaque in sun circle(region.sun.count.opaque)
• Pixel count: camera and sun strip mask(count.mask)
• Pixel count: number total thin(count.thin)
• Pixel count: number thin in zenith circle(region.zenith.count.thin)
• Pixel count: number total between horizon and processed circle(count.sub.proczen)
• Pixel count: number opaque in zenith circle(region.zenith.count.opaque)
• Pixel count: number thin in horizon area(region.horizon.count.thin)
• Pixel count: number thin in sun circle(region.sun.count.thin)
• Pixel count: number total indeterminant(count.unknown)
• Percentage thin cloud(percent.thin)
• Pixel count: number total opaque(count.opaque)
• Pixel count: number below horizon in image(count.sub.horz)
• Pixel count: number total in zenith circle(region.zenith.count)
• Pixel count: box, outside mirror area(count.box)
• Pixel count: number total in processed circle(count.sky)
• Percent opaque cloud(percent.opaque)

• PNG data stream - documentation not supported(png)

• (MPEG data stream - documentation not yet available)

PYE/AERI/M1 - Incorrect reporting of the hatch open status

The polarity of the hatch controller was incorrect. The hatch was reported in an 
indeterminate position (red) when the controller was open and collecting data. Normally, when the 
hatch open metadata flag is red, the hatch is closed or partially closed and there is no 
sky data. However, because the polarity was reversed, the hatch flagged red when the 
hatch was open. The problem was resolved by reversing the polarity through software. The 
hatch flag now correctly reports the status of the hatch.

• Logical flag indicating whether hatch is open (true) or not open (false)(hatchOpen)

PYE/TSI/M1 - water in lens

The lower half of the TSI images were blurry due to water in the camera lens and/or 
filter. The problem was corrected when both were cleaned.

• Raw data stream - documentation not supported(raw)

• JPG data stream - documentation not supported(JPEG data stream - documentation not yet available)

• Pixel count: number opaque in horizon area(region.horizon.count.opaque)
• Pixel count: number total in horizon area(region.horizon.count)
• Pixel count: number total in sun circle(region.sun.count)
• Pixel count: number opaque in sun circle(region.sun.count.opaque)
• Pixel count: camera and sun strip mask(count.mask)
• Pixel count: number total thin(count.thin)
• Pixel count: number thin in zenith circle(region.zenith.count.thin)
• Pixel count: number total between horizon and processed circle(count.sub.proczen)
• Pixel count: number opaque in zenith circle(region.zenith.count.opaque)
• Pixel count: number thin in horizon area(region.horizon.count.thin)
• Pixel count: number thin in sun circle(region.sun.count.thin)
• Pixel count: number total indeterminant(count.unknown)
• Percentage thin cloud(percent.thin)
• Pixel count: number total opaque(count.opaque)
• Pixel count: number total in zenith circle(region.zenith.count)
• Pixel count: number below horizon in image(count.sub.horz)
• Pixel count: box, outside mirror area(count.box)
• Pixel count: number total in processed circle(count.sky)
• Relative \'strength\' of direct sun(sun.strength)
• Percent opaque cloud(percent.opaque)

• PNG data stream - documentation not supported(png)

• (MPEG data stream - documentation not yet available)

PYE/ECOR/M1 - Reprocessed: Wind direction offset corrected

The SMET wind direction was consistently 15 to 20 degrees larger than the wind direction 
determined by the ECOR. The ECOR was mistakenly aligned to magnetic north during this 
period.

The magnetic declination is 14 deg. 58 min., which explains most of the difference.

The ECOR data for this period were reprocessed in November 2006 to add 15 degrees to the 
wind direction.  No other changes were made to the data. The reprocessed data were 
archived in January 2007.

• vector averaged wind direction(wind_dir)

PYE/SONDE/M1 - Broken RH sensor

One of the RH sensors on this radiosonde was bad.  The RH oscillates rapidly between near 
0 and ambient up to approximately 11 km.  The near-zero values are incorrect.

• Relative humidity inside the instrument enclosure(rh)
• Surface dew point temperature(dp)

PYE/SONDE/M1 - Bad temperature and RH

The temperature appears to be approximately 10 degC too high during the entire sounding.  
This also causes the RH to be too low.  Most likely the problem was a bad temperature 
sensor.

• Relative humidity inside the instrument enclosure(rh)
• Surface dew point temperature(dp)
• Dry bulb temperature(tdry)

PYE/SONDE/M1 - Bad RH sensor

The RH sensor heating circuit failed on this sounding.  RH values during the first part of 
the sounding oscillate between a reasonable value and a very low value.  It appears that 
(a) the heating was out of phase, and (b) incorrect values were being reported during 
the first 10 minutes or so of flight.

• Relative humidity inside the instrument enclosure(rh)
• Surface dew point temperature(dp)

PYE/SONDE/M1 - Bad RH sensor

Two problems here - failure of the RH sensor heating circuit and a bad RH sensor.

• Relative humidity inside the instrument enclosure(rh)
• Surface dew point temperature(dp)

PYE/ECOR/M1 - Flux Data Suspect For Some Wind Directions

For some wind directions the horizontal fetch was not representative 
of the field in which the AMF was located.  Therefore, for the wind 
direction ranges 66-92 (buildings and trees) degrees, the fluxes are 
affected by insufficient fetch and  surfaces, buildings, or vegetation 
that are not similar to the local field conditions.

• CO2 flux(fc)
• latent heat flux(lv_e)
• Friction velocity(ustar)
• h(h)