Data / Data Sources

TROPOE

TROPoe retrievals from SGP C1

PI

Purpose

The TROPoe (formerly called AERIoe) algorithm (Turner and Löhnert 2014, 2021; Turner and Blumberg 2019) retrieves profiles of temperature and water vapor mixing ratio, together with cloud properties for a single-layer cloud (i.e., LWP, effective radius), from AERI-observed infrared radiance spectrum. The data can be used to characterize the evolution of the planetary boundary layer and boundary layer clouds.

This data set was collected at the ARM SGP Central Facility (CF) during and after the MicroPulse DIAL Demonstration (MPDDEMO) field campaign. The TROPoe retrieval was run at 5-minute resolution, but retrievals can be performed at the maximum temporal resolution of the AERI instrument (order 30 s) -- if this higher temporal resolution is desired, please contact Dave Turner.

This is a physical-iterative retrieval method. The retrieval of thermodynamic profiles from spectral infrared radiance observations is an ill-posed problem, and thus constraints need to be included in the retrieval algorithm to provide physically plausible results. Here, we use a climatology of radiosonde profiles collected at the ARM SGP site during the summer as our prior information in an optimal estimation framework. Surface meteorology and output from the rapid-refresh (RAP) numerical weather prediction model (above 4 km) were used as additional constraints by the retrieval. As the method uses an optimal estimation framework, a full error covariance matrix of each solution is included in the output file. The 1-sigma uncertainty of each retrieved variable, which is derived from the error covariance matrix, is included for each scientific field and is named "sigma_X", where "X" is the name of the scientific field (e.g., 'temperature'). The information content in the AERI observations, which is in the "dfs" field, on the thermodynamic profiles is primarily concentrated in the lowest 3 km or up to cloud base; the retrieved data should not be used above that level (or used with caution).

There is an overall "qc_flag" field that is set when a retrieval should not be trusted. However, the logic that sets this flag did not work correctly, and it should not be used. Instead, consider all retrievals that have a value for "converged_flag" greater than 0 as valid. If you have any questions, contact Dave Turner.

This is Release_2_12 of the TROPoe algorithm.