Search NASA⌕ Search

SEARCH · Search NASA

Results for “ELEVATION ANGLE”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records

The Impact of Nonzenith Elevation Angles on Ground-Based Infrared Thermodynamic Retrievals

Observing thermodynamic profiles within the planetary boundary layer is essential to understanding and predicting atmospheric phenomena because of the significant exchange of sensible and latent heat between the land and atmosphere within that layer. The Atmospheric Emitted Radiance Interferometer (AERI) is a ground-based infrared spectrometer used to obtain the vertical profiles of temperature and water vapor mixing ratio. Most AERIs are only capable of zenith views, although the Marine AERI (M-AERI) has a design that allows it to view various elevation angles. In this study, we quantify the improvement in the information content and accuracy of the retrieved profiles when nonzenith angles are included, as is common with microwave radiometer profilers. The impacts of the additional scan angles are quantified through both a synthetic study and with M-AERI observations from the ARM Cloud Aerosol Precipitation Experiment (ACAPEX) campaign. Furthermore, the simulation study shows that low elevation angles contain more information content for temperature whereas high elevation angles have more information content for water vapor. Outside of very humid environments, the addition of low elevation angles also results in lower root-mean-square errors when compared with high angles for both temperature and water vapor mixing ratio, although this is primarily a result of averaging multiple observations together to reduce instrument noise. Real-world results from the ACAPEX dataset indicate similar results as were found for the simulation study, although not all predicted benefits are realized because of the small sample size and observational uncertainties.

54 ENVIRONMENTAL SCIENCES↗

Temperature Inversions below 1 km from a V-Band Scanning Radiometer at the North Slope of Alaska

A single-channel (56.7 GHz) scanning radiometer was deployed in August 2022 at the Atmospheric Radiation Measurement (ARM) North Slope of Alaska site near Utqiaġvik. The radiometer is designed to provide temperature profiles between 0 and 1 km every 5 min. Averaging kernels show that this single-channel radiometer, taking observations at 10 discrete elevation angles, yields approximately the same information as a seven-channel V-band radiometer scanning three elevation angles. The instrument is able to reproduce the occurrence of temperature inversions between the surface and 1 km and their strength showing a correlation of 0.85, bias of −0.6 K, and slope of 1.04 with respect to radiosondes. Uncertainty in the inversion base height varies from 50 m near the surface to ∼300 m above 0.4 km when compared with radiosondes. Conversely, the inversion top height is overestimated and has higher uncertainty due to the degrading effects of the averaging kernels on the vertical resolution of the retrievals. Thanks to the high temporal resolution of the retrievals, the diurnal cycle of boundary layer temperature was evaluated showing that the radiometer can capture some aspects of the boundary layer thermal structure. The present analysis provides an overview of the capabilities of this simple observing configuration for selected applications.

Atmospheric profilers↗

The Baryonic Content of Galaxies Mapped by MaNGA and the Gas Around Them

We analyze the cool gas in and around 14 nearby galaxies (at z < 0.1) mapped with the Sloan Digital Sky Survey IV MaNGA survey by measuring absorption lines produced by gas in spectra of background quasars/active galactic nuclei at impact parameters of 0–25 effective radii from the galactic centers. Using Hubble Space Telescope/Cosmic Origins Spectrograph, we detect absorption at the galactic redshift and measure or constrain column densities of neutral (H I, N I, O I, and Ar I), low-ionization (Si II, S II, C II, N II, and Fe II), and high-ionization (Si III, Fe III, N v, and O vI) species for 11 galaxies. We derive the ionization parameter and ionization-corrected metallicity using cloudy photoionization models. The H i column density ranges from ~1013 to ~1020 cm-2 and decreases with impact parameter for r ≳ Re. Galaxies with higher stellar mass have weaker H I absorption. Comparing absorption velocities with MaNGA radial velocity maps of ionized gas line emissions in galactic disks, we find that the neutral gas seen in absorption corotates with the disk out to ~10 R e . Sight lines with lower elevation angles show lower metallicities, consistent with the metallicity gradient in the disk derived from MaNGA maps. Higher-elevation angle sight lines show higher ionization, lower H I column density, supersolar metallicity, and velocities consistent with the direction of galactic outflow. Our data offer the first detailed comparisons of circumgalactic medium (CGM) properties (kinematics and metallicity) with extrapolations of detailed galaxy maps from integral field spectroscopy; similar studies for larger samples are needed to more fully understand how galaxies interact with their CGM.

79 ASTRONOMY AND ASTROPHYSICS↗

Statistical Correlation of Heliostat Pointing Deviation With Wind

This work was carried out as part of the Heliostat Consortium (HelioCon) Field Deployment subtask with the aim to develop a reduced order model framework for correlating wind speed and pointing deviation of a heliostat facet. There are only sparse field measurements of heliostat pointing deviations and accompanying wind conditions published in the literature. Heliostat test standards, such as IEC 62862-4-3, propose a suite of tests including laser pointing repeatability at wind speeds below 4 m/s, and provide technical requirements for heliostat slope and tracking deviations in coarse average wind speed bins of 4 m/s, 6 m/s, and 8 m/s. In addressing the gap of the variation of heliostat pointing deviation with wind speed, field measurements of laser pointing on a grid target and wind conditions were analyzed in this study at the Third-Party Metrology Platform at the National Laboratory of the Rockies (NLR) Flatirons Campus. Horizontal pointing deviations were found to follow a logarithmic relationship with peak wind speed, whereas vertical pointing deviations follow an exponential relationship with peak wind speed. Both horizontal and vertical pointing deviations also follow a second order polynomial relationship, as expected from the proportionality of elastic loads and deformations with the square of wind speed. The results indicate that heliostat facet pointing deviations in the vertical direction increase at a faster rate than in the horizontal direction with increasing wind speed over the tested range, however these are dependent on the heliostat structural design. Next steps are recommended for additional field measurements to confirm a linear relationship of pointing deviation with applied moment on a heliostat facet, and to distinguish between gravity-induced and wind-induced pointing deviations at different elevation angles. The derived correlations in the preliminary analysis in this report serve as a case study for heliostat developers and plant operators to estimate the wind-induced pointing deviations and their variation with peak gust wind speed. Next steps in future work would recommend higher resolution and longer duration datasets for different elevation angles and wind directions to reduce uncertainties and variance of collected laser beam spot data and their correlations with bin-averaged wind speed.

17 WIND ENERGY↗

Baltimore Social-Environmental Collaborative (BSEC) Doppler Lidar & Derived Products

This repository contains all processed Doppler‐lidar outputs from the PSU lidar deployed for the Baltimore Social‐Environmental Collaborative (BSEC) project. Vertical Stare Scans (fixed‐beam, vertical profiling): 1 Hz backscatter intensity (m⁻¹ sr⁻¹), signal‐to‐noise ratio (unitless), and Doppler vertical‐velocity (m s⁻¹) on ~30 m range gates, stored as CF-compliant NetCDF. Wind Profiles (horizontal‐wind retrieval): daily NetCDF outputs of retrieved horizontal wind speed (m s⁻¹) and direction (degrees), computed from the angled‐scan returns. Profile Statistics (summary statistics on the vertical velocity): 15 min windows (default) of mean, variance, skewness, kurtosis, high-frequency variance, etc., as a function of height; saved as CF-compliant NetCDF files. Boundary Layer Height (BLH) (fuzzy-logic output): 15 min BLH estimates (m), with lower/upper fuzzy bounds (m) and a quality flag (0–4) indicating data status (e.g., no data, good, below range, ran out of signal, cloud-topped). Cloud Base Height (Haar-gradient detection): 15 min estimates of cloud-base height (m) with a cloud-detection quality flag (0–3: none, low, moderate, high). All five product streams are organized by year and date under their own top-level folders (01_Vertical_Stare_Scans/ through 05_Cloud_Height/). Each folder contains a data_ /YYYY/ subdirectory with daily CF-compliant NetCDF outputs (96 windows per day at 15 min intervals). Global attributes in each file include creation history, version (2.0.0), institution, and source. Instrument & MeasurementsThe PSU Doppler Lidar samples aerosol backscatter (m⁻¹ sr⁻¹), signal-to-noise ratio, and radial velocity at ~1 Hz. Vertical stare scans point the beam straight up; after collecting angled scans through multiple elevation angles, the "Wind Profiles" product contains the fully retrieved horizontal wind speed and direction. Data were collected continuously at ~30 m range resolution, with a typical height ceiling of ~12 km. How to Use Open any NetCDF with Python's xarray, MATLAB, or similar CF-compliant tools. Stare scans and angled-scan retrievals (Wind Profiles) are CF-compliant daily NetCDF files. Profile-Statistics, BLH, and Cloud Height files are daily 15 min summaries (96 time steps per file). Inspect the included variables (e.g., vertical_velocity_variance, wind_speed, BLH, cloud_base_height) for your analyses. Use the quality flags (BLH_flag, cloud_flag) to filter out poor-quality retrievals. For more information or questions about processing methods, please contact:Nicholas E. Prince ⟨nec5299@psu.edu⟩Penn State Department of Meteorology & Atmospheric Science

Air Quality↗

Baltimore Social-Environmental Collaborative (BSEC) Doppler Lidar & Derived Products

This repository contains all processed Doppler‐lidar outputs from the PSU lidar deployed for the Baltimore Social‐Environmental Collaborative (BSEC) project. Vertical Stare Scans (fixed‐beam, vertical profiling): 1 Hz backscatter intensity (m⁻¹ sr⁻¹), signal‐to‐noise ratio (unitless), and Doppler vertical‐velocity (m s⁻¹) on 30 m range gates (and 3 m range gates), stored as CF-compliant NetCDF. Wind Profiles (horizontal‐wind retrieval): daily NetCDF outputs of retrieved horizontal wind speed (m s⁻¹) and direction (degrees), computed from the angled‐scan returns. Profile Statistics (summary statistics on the vertical velocity): 15 min windows (default) of mean, variance, skewness, kurtosis, high-frequency variance, etc., as a function of height; saved as CF-compliant NetCDF files. Boundary Layer Height (BLH) (fuzzy-logic output): 15 min BLH estimates (m), with lower/upper fuzzy bounds (m) and a quality flag (0–4) indicating data status (e.g., no data, good, ran out of signal, below range, cloud-topped). Cloud Base Height (Haar-gradient detection): 10 min estimates of cloud-base height (m). All five product streams are organized by year and date under their own top-level folders (01_Vertical_Stare_Scans/ through 05_Cloud_Height/). Each folder contains a data_ /YYYY/ subdirectory with daily CF-compliant NetCDF outputs (96 windows per day at 15 min intervals). Global attributes in each file include creation history, version (3.0.0), institution, and source. Instrument & MeasurementsThe PSU Doppler Lidar samples aerosol backscatter (m⁻¹ sr⁻¹), signal-to-noise ratio, and radial velocity at ~1 Hz. Vertical stare scans point the beam straight up; after collecting angled scans through multiple elevation angles, the "Wind Profiles" product contains the fully retrieved horizontal wind speed and direction. Data were collected continuously at ~30 m range resolution (and 3 m for the year of 2025), with a typical height ceiling of ~12 km. How to Use Open any NetCDF with Python's xarray, MATLAB, or similar CF-compliant tools. Stare scans and angled-scan retrievals (Wind Profiles) are CF-compliant daily NetCDF files. Profile-Statistics, BLH, and Cloud Height files are daily 15 min (10 min for Cloud Heights) summaries (96 time steps per file). Inspect the included variables (e.g., vertical_velocity_variance, wind_speed, BLH, cloud_base_height) for your analyses. Use the quality flags (BLH_flag, cloud_flag) to filter out poor-quality retrievals. For more information or questions about processing methods, please contact:Nicholas E. Prince ⟨nec5299@psu.edu⟩Penn State Department of Meteorology & Atmospheric Science

Air Quality↗

Baltimore Social-Environmental Collaborative (BSEC) Doppler Lidar & Derived Products

This repository contains all processed Doppler‐lidar outputs from the PSU lidar deployed for the Baltimore Social‐Environmental Collaborative (BSEC) project. Vertical Stare Scans (fixed‐beam, vertical profiling): 1 Hz backscatter intensity (m⁻¹ sr⁻¹), signal‐to‐noise ratio (unitless), and Doppler vertical‐velocity (m s⁻¹) on 30 m range gates (and 3 m range gates), stored as CF-compliant NetCDF. Wind Profiles (horizontal‐wind retrieval): daily NetCDF outputs of retrieved horizontal wind speed (m s⁻¹) and direction (degrees), computed from the angled‐scan returns. Profile Statistics (summary statistics on the vertical velocity): 15 min windows (default) of mean, variance, skewness, kurtosis, high-frequency variance, etc., as a function of height; saved as CF-compliant NetCDF files. Boundary Layer Height (BLH) (fuzzy-logic output): 15 min BLH estimates (m), with lower/upper fuzzy bounds (m) and a quality flag (0–4) indicating data status (e.g., no data, good, ran out of signal, below range, cloud-topped). Cloud Base Height (Haar-gradient detection): 10 min estimates of cloud-base height (m). All five product streams are organized by year and date under their own top-level folders (01_Vertical_Stare_Scans/ through 05_Cloud_Height/). Each folder contains a data_ /YYYY/ subdirectory with daily CF-compliant NetCDF outputs (96 windows per day at 15 min intervals). Global attributes in each file include creation history, version (3.0.1), institution, and source. Instrument & MeasurementsThe PSU Doppler Lidar samples aerosol backscatter (m⁻¹ sr⁻¹), signal-to-noise ratio, and radial velocity at ~1 Hz. Vertical stare scans point the beam straight up; after collecting angled scans through multiple elevation angles, the "Wind Profiles" product contains the fully retrieved horizontal wind speed and direction. Data were collected continuously at ~30 m range resolution (and 3 m for the year of 2025), with a typical height ceiling of ~12 km. How to Use Open any NetCDF with Python's xarray, MATLAB, or similar CF-compliant tools. Stare scans and angled-scan retrievals (Wind Profiles) are CF-compliant daily NetCDF files. Profile-Statistics, BLH, and Cloud Height files are daily 15 min (10 min for Cloud Heights) summaries (96 time steps per file). Inspect the included variables (e.g., vertical_velocity_variance, wind_speed, BLH, cloud_base_height) for your analyses. Use the quality flags (BLH_flag, cloud_flag) to filter out poor-quality retrievals. For more information or questions about processing methods, please contact:Nicholas E. Prince ⟨nec5299@psu.edu⟩Penn State Department of Meteorology & Atmospheric Science

Air Quality↗

dlmcfpt.c1

The DLMC VAP uses inertial data from the ARM NAV system to transform the Doppler lidar beam angles (az and el) from the lidar's frame of reference to an Earth-fixed frame such the azimuth angle is measured clockwise from true north and the elevation angle is measured from the local horizon. Additionally, the VAP compensates the observed radial (air) velocity data for the effects of the platform velocity (i.e. corrected_radial_velocity = observed_radial_velocity-platform_radial_velocity). The VAP was developed specifically for MOSAiC. The dlmcfpt.c1 product contains the fixed point, or staring data. The dlmcusr.c1 product contains a user defined scan which is anything the operator wants it to be.

54 ENVIRONMENTAL SCIENCES↗

dlmcusr.c1

The DLMC VAP uses inertial data from the ARM NAV system to transform the Doppler lidar beam angles (az and el) from the lidar's frame of reference to an Earth-fixed frame such the azimuth angle is measured clockwise from true north and the elevation angle is measured from the local horizon. Additionally, the VAP compensates the observed radial (air) velocity data for the effects of the platform velocity (i.e. corrected_radial_velocity = observed_radial_velocity-platform_radial_velocity). The VAP was developed specifically for MOSAiC. The dlmcfpt.c1 product contains the fixed point, or staring data. The dlmcusr.c1 product contains a user defined scan which is anything the operator wants it to be.

54 ENVIRONMENTAL SCIENCES↗

TRACER CLAMPS1 Doppler Lidar VAD Data

These files contain 24 hour periods of data collected from the CLAMPS1 Halo Streamline XR Doppler lidar. The Doppler lidar conducts regular conical scans at a set elevation angle. These data are then passed through a typical VAD algorithm to retrieve horizontal wind speed and direction profiles. These data were collected during the TRACER project. For the TRACER campaign, the CLAMPS1 Doppler lidar collected PPI scans at 70 deg elevation every 20 minutes.

54 ENVIRONMENTAL SCIENCES↗

RHOD Site - NOAA PSL Wind Retrievals WINDoe / Derived Data

This dataset contains daily NetCDF files with horizontal wind profiles retrieved with the WINDoe retrieval (Gebauer and Bell 2024) at Rhode Island (RHOD). WINDoe retrievals datasets are also available at Nantucket Island (NANT, nant.windoe.z01.c1) and Block Island (BLOC, bloc.windoe.z01.c1). WINDoe is an optimal estimation algorithm to retrieve wind profiles combining multiple instruments. The code is available in this github repository (https://github.com/OAR-atmospheric-observations/WINDoe/tree/main) and the retrieval is described by Gebauer and Bell (2024). WINDoe allows combining the individual datasets and outputs into one profile taking into account the information and uncertainties of each dataset. The use of WINDoe minimizes data gaps and maximizes data availability, compared to using wind profiles from only one of the instruments. The regular height grid eases comparisons to numerical weather prediction models. Code modifications have been made that include reading in WFIP3 specific instruments, averaging Doppler lidar radial velocities at various azimuth angles to avoid overfitting, and allowing the user to define a height grid by the user in the vipfile. The instruments used as input to the retrieval are a radar wind profiler (low- and high resolution mode) providing data in and above the boundary layer, a scanning Doppler lidar usually providing data throughout the boundary layer, a profiling lidar providing data from 50 to 200 m at BLOC and NANT, and from 10 to 280 m at Rhode Island, and a surface tower (4 m at NANT and RHOD and 10 m at BLOC). From the scanning lidars, we used radial velocity measurements at 60 deg elevation angle at six different azimuth angles with a resolution of approximately 30 m along the line of sight and the lowest range gate at approximately 70 m. The wind profiles are retrieved with WINDoe up to 3.74 km with 10 m vertical resolution. The profiles are retrieved every 15 min at BLOC and NANT and every 60 min at RHOD.

17 WIND ENERGY↗

BLOC Site - NOAA PSL Wind Retrievals WINDoe / Derived Data

This dataset contains daily netcdf files with horizontal wind profiles retrieved with the WINDoe retrieval (Gebauer and Bell 2024) at Block Island (BLOC). WINDoe retrievals datasets are also available at Nantucket Island (NANT, nant.windoe.z01.c1) and Rhode Island (RHOD, rhod.windoe.z01.c1). WINDoe is an optimal estimation algorithm to retrieve wind profiles combining multiple instruments. The code is available in this github repository (https://github.com/OAR-atmospheric-observations/WINDoe/tree/main), and the retrieval is described by Gebauer and Bell (2024). WINDoe allows combining the individual datasets and outputs into one profile taking into account the information and uncertainties of each dataset. The use of WINDoe minimizes data gaps and maximizes data availability, compared to using wind profiles from only one of the instruments. The regular height grid eases comparisons to numerical weather prediction models. Code modifications have been made that include reading in WFIP3 specific instruments, averaging Doppler lidar radial velocities at various azimuth angles to avoid overfitting, and allowing the user to define a height grid by the user in the vipfile. The instruments used as input to the retrieval are a radar wind profiler (low- and high resolution mode) providing data in and above the boundary layer, a scanning Doppler lidar usually providing data throughout the boundary layer, a profiling lidar providing data from 50 to 200 m at BLOC and NANT, and from 10 to 280 m at Rhode Island, and a surface tower (4 m at NANT and RHOD and 10 m at BLOC). From the scanning lidars, we used radial velocity measurements at 60 deg elevation angle at six different azimuth angles with a resolution of approximately 30 m along the line of sight and the lowest range gate at approximately 70 m. The wind profiles are retrieved with WINDoe up to 3.74 km with 10 m vertical resolution. The profiles are retrieved every 15 min at BLOC and NANT and every 60 min at RHOD.

17 WIND ENERGY↗

NANT Site - NOAA PSL Wind Retrievals WINDoe / Derived Data

This dataset contains daily NetCDF files with horizontal wind profiles retrieved with the WINDoe retrieval (Gebauer and Bell 2024) at Nantucket Island (NANT). WINDoe retrievals datasets are also available at Block Island (BLOC, bloc.windoe.z01.c1) and Rhode Island (RHOD, rhod.windoe.z01.c1). WINDoe is an optimal estimation algorithm to retrieve wind profiles combining multiple instruments. The code is available in this github repository (https://github.com/OAR-atmospheric-observations/WINDoe/tree/main), and the retrieval is described by Gebauer and Bell (2024). WINDoe allows combining the individual datasets and outputs into one profile taking into account the information and uncertainties of each dataset. The use of WINDoe minimizes data gaps and maximizes data availability, compared to using wind profiles from only one of the instruments. The regular height grid eases comparisons to numerical weather prediction models. Code modifications have been made that include reading in WFIP3 specific instruments, averaging Doppler lidar radial velocities at various azimuth angles to avoid overfitting, and allowing the user to define a height grid by the user in the vipfile. The instruments used as input to the retrieval are a radar wind profiler (low- and high resolution mode) providing data in and above the boundary layer, a scanning Doppler lidar usually providing data throughout the boundary layer, a profiling lidar providing data from 50 to 200 m at BLOC and NANT, and from 10 to 280 m at Rhode Island, and a surface tower (4 m at NANT and RHOD and 10 m at BLOC). From the scanning lidars, we used radial velocity measurements at 60 deg elevation angle at six different azimuth angles with a resolution of approximately 30 m along the line of sight and the lowest range gate at approximately 70 m. The wind profiles are retrieved with WINDoe up to 3.74 km with 10 m vertical resolution. The profiles are retrieved every 15 min at BLOC and NANT and every 60 min at RHOD.

17 WIND ENERGY↗

twoaxistracking – a python package for simulating self-shading of two-axis tracking solar collectors

Self-shading in fields of two-axis tracking collectors typically ranges from 1% to 6% of the annual incident irradiation. It is thus essential to account for shading in order to obtain accurate yield estimates and financing for such solar projects. The present study presents the free and open-source Python package twoaxistracking for simulating self-shading in fields of two-axis tracking collectors. The package is freely available at: https://github.com/pvlib/twoaxistracking. The main steps of the method and mathematical formulation are described. Additionally, a demonstration of how to use the package is presented. The shading calculation method excels over previous methods found in the literature in that it can: handle arbitrary aperture geometries and distinguish between the total and active areas; account for sloped ground and collectors with different heights within the same field; reduce computation time by skipping calculations at high solar elevation angles.

14 SOLAR ENERGY↗

Surface Cloud Grid Version 2 (SFCCLDGRID2) Value-Added Product: Description of Update"

This document describes the algorithm used for the Surface Cloud Grid Value-Added Product (VAP). This VAP uses as input the 15-min. output from the Shortwave (SW) Flux Analysis VAP (see Long 2001; Long and Ackerman 2000; Long et al. 1999) from the Atmospheric Radiation Measurement (ARM) Climate Reseach Facility (ACRF) Southern Great Plains (SGP) Central Facility and extended facilities. This network of 21 sites is unevenly spaced over northern Oklahoma into southern Kansas, covering an area from 95.5° to 99.5° west longitude and 34.5° to 38.5° north latitude. For research applications such as single-column modeling, an estimate of the cloud and cloud effects distribution over this entire domain is desirable. The Surface Cloud Grid VAP applies a multi-pass weighted sum analytic approximation technique (Caracena 1987), which uses Gaussian weighting and an imposed scale length, to interpolate to a 0.25° by 0.25° lat/long grid over the SGP domain. The output, like the input, includes solar elevation angles of 10° or greater.

97 MATHEMATICS AND COMPUTING↗

Doppler Lidar Motion-Correction Wind Profiles (DLMCPROF-WIND) Value-Added Product Report

Wind speed and direction, together with pressure, temperature, and relative humidity, are the most fundamental atmospheric state parameters. Accurate measurement of these parameters is crucial for numerical weather prediction. Vertically resolved wind measurements in the atmospheric boundary layer are particularly important for modeling pollutant and aerosol transport. The U.S. Department of Energy (DOE) Atmospheric Radiation Measurement (ARM) user facility currently operates several scanning coherent Doppler lidar (DL) systems that provide accurate height-resolved measurements of wind speed and direction. These instruments operate in the near infrared (IR;1.5 microns) and provide range-resolved measurements of radial velocity, attenuated aerosol backscatter, and signal-to-noise ratio (SNR). The systems are operated using a fixed scan schedule consisting of plan position indicator (PPI) or Doppler Beam-Swing (DBS) scans. PPI scans are performed by scanning the beam in azimuth while maintaining a fixed elevation angle, and DBS scans are similar but typically also include a vertical beam. Radial velocity data from these scans are processed to yield profiles of wind speed direction. For stationary ground-based deployments, the Doppler Lidar Horizontal Wind Profiles (DLPROF-WIND) Value-Added-Product (VAP) provides height- and time-resolved measurements of the winds (Newsom and Krishnamurthy 2022). For operation on a moving platform, modifications to the existing DLPROF-WIND VAP are required to compensate for the effects of the platform motion. This report describes a parallel VAP, DLMCPROF-WIND, that was developed for computing motion-compensated wind profiles from ARM Doppler lidar data acquired during the Multidisciplinary drifting Observatory for the Study of Arctic Climate (MOSAiC) campaign, when the lidar was deployed on the German icebreaker Polarstern.

54 ENVIRONMENTAL SCIENCES↗

Numerical Investigation of Wall-Cooling Effect on Aero-Optical Distortions for Hypersonic Boundary Layer

Compressible wall-modeled large-eddy simulations of Mach 8 turbulent boundary-layer flows over a flat plate were carried out for the conditions of the hypersonic wind tunnel at Sandia National Laboratories. The simulations provide new insight into the effect of wall cooling on the aero-optical path distortions for hypersonic turbulent boundary-layer flows. Four different wall-to-recovery temperature ratios, 0.3, 0.48, 0.71, and 0.89, are considered. Despite the much lower grid resolution, the mean velocity, temperature, and resolved Reynolds stress profiles from the simulation for a temperature ratio of 0.48 are in good agreement with those from a reference direct numerical simulation. The normalized root-mean-square optical path difference obtained from the present simulations is compared with that from reference direct numerical simulations, Sandia experiments, as well as predictions obtained with a semi-analytical model by Notre Dame University. Here the present analysis focuses on the effect of wall cooling on the wall-normal density correlations, on key underlying assumptions of the aforementioned model such as the strong Reynolds analogy, and on the elevation angle effect on the optical path difference. Wall cooling is found to increase the velocity fluctuations and decrease the density fluctuations, resulting in an overall reduction of the normalized optical path distortion. Compared to the simulations, the basic strong Reynolds analogy overpredicts the temperature fluctuations for cooled walls. Also different from the strong Reynolds analogy, the velocity and temperature fluctuations are not perfectly anticorrelated. Finally, as the wall temperature is raised, the density correlation length, away from the wall but inside the boundary layer, increases significantly for beam paths tilted in the downstream direction.

42 ENGINEERING↗