MAG/TSI/M1 - Water on lens

After a rain episode, drops of water collected on the lens window causing the cloud 
fraction values to be suspect.

To prevent this, a drip edge was formed around the bottom of the enclosure with thick 
electrical or splicing tape.

• region_zenith_count_thin
• region_zenith_count_opaque
• Cloud amount, opaque (percent)(percent_opaque)
• count_thin
• count_sky
• Cloud amount, thin (percent)(percent_thin)
• region_zenith_count
• count_opaque

MAG/TSI/M1 - Shadowband misalignment

The mirror was not being controlled correctly so the shadowband did not block the sun 
because the encoder failed. Also, the shadowband was not correctly positioned in the 
processed image while at port because the INS system failed.

On 10/19 while at Long Beach port, the encoder was replaced and software was installed to 
get the mirror control board to receive the SeaNav data and correctly position the 
shadowband to mask the sun in the visible image. However, the position of the shadowband in the 
processed image was not correct because the imaging software needed to be configured to 
independently read the SeaNav information.

On 11/8 while at Honolulu port, the TSI software was upgraded at 17:10 and the position of 
the shadowband in the processed image was corrected. However, because SeaNav failed and 
course-over-ground was being used as a surrogate for heading, the heading is 0 deg when 
the ship speed is < 1 m/s. So the platform heading was changed manually at 17:45 to 
correct the position of the shadowband in the visible image while the ship was in port. 

This method was used by the site technicians to configure the TSI upon arrival and 
departure at port until the ship navigation system was replaced on 12/7 at 9:00. The $TSINV 
heading value became accurate while in port so the position of the TSI shadowband was 
automatically controlled correctly both at sea and at port.

• region_zenith_count_thin
• region_sun_count
• region_horizon_count
• region_zenith_count_opaque
• region_sun_count_thin
• region_horizon_count_thin
• region_horizon_count_opaque
• region_sun_count_opaque
• Cloud amount, opaque (percent)(percent_opaque)
• Cloud amount, thin (percent)(percent_thin)
• region_zenith_count

• JPEG data stream - documentation not yet available

• Cloud decision images, Total Sky Imager, PNG format(png)

MAG/TSI/M1 - Data processing problem

Values of count_opaque and count_thin are reals but should be integers 
(units = pixels).

• count_thin
• count_opaque

MAG/MPL/M1 - Instrument problem

Backscatter image is indicating some strange artifact at 3-5 km with higher than expected 
returns. The ship is currently at sea, so I am not able to look at the data directly. The 
only indication of the issue is with this comparison plot.

Rich, what do you think. Could a reboot help with this issue?

• qc_detector_temp
• qc_signal_return_cross_pol
• range
• alt
• polarization_control_voltage
• lat
• background_signal_cross_pol
• background_signal_co_pol
• qc_range_offset
• overlap_correction
• dead_time_corrected
• scope_temp
• Attenuated backscatter, copol(signal_return_co_pol)
• energy_monitor
• num_bins
• qc_time
• range_bin_width
• overlap_correction_heights
• time
• deadtime_correction
• Attenuated backscatter, cross pol(signal_return_cross_pol)
• range_bin_time
• qc_laser_temp
• max_altitude
• background_signal_std_cross_pol
• pulse_rep
• qc_preliminary_cbh
• base_time
• laser_temp
• polarization_control
• detector_temp
• time_offset
• qc_energy_monitor
• lon
• qc_scope_temp
• Preliminary cloud base height(preliminary_cbh)
• qc_signal_return_co_pol
• mcs_mode
• Pressure, associated geometric height, at altitude, NGM model output(height)
• first_data_bin
• background_signal_std_co_pol
• deadtime_correction_counts
• num_channels
• range_bins
• range_offset