SEARCH · Search NASA

Results for “Horizontal wind”

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.

SourceResearch connectionFrom yearThrough year

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

At least 19 records

All sources NASA NTRS DOE OSTI

DOE OSTI2025

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↗

DOE OSTI2026

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↗

DOE OSTI2026

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↗

DOE OSTI2025

CROCUS Urban Canyons - Space Science and Engineering Center (SPARC) Doppler lidar data

This is the netCDF format output from the Halo Photonics Streamline XR Doppler lidar that was deployed next to the Space Science and Engineering Center (SPARC) trailer at the University of Illnois-Chicago greenhouse parking lot during CROCUS Urban Canyons. The purpose of collecting this dataset is to provide vertical and horizontal wind profiles for studying the characteristics of turbulence over the urban canyon of Chicago. This data contains the radial velocity, intensity, and backscatter from the vertical profile, range height indicator, and sector scans that were performed over both Intensive Operating Period 1 and 2 of CROCUS Urban Canyons. There are four different types of files: * The Range Height Indicator (RHI) files contain scans that are along a constant azimuth, spanning the entire hemisphere of elevation values above the surface. * The Velocity Azimuth Display (VAD) files contain the raw radial velocity data from the 6-beam, 60 degree scans. * The User1 files contain stacked Plan Position Indicator scans over a 45 degree quadrant over downtown Chicago. * The Stare files contain vertically pointing scans. These are standard netCDF files that can be opened using xarray. The VAD scans can be processed from their raw radial velocities to horizontal wind speeds with the Atmospheric data Community Toolkit (https://arm-doe.github.io/ACT/).

EARTH SCIENCE > ATMOSPHERE > ATMOSPHERIC WINDS↗

DOE OSTI2025

Eddy Correlation Flux Measurement System (ECOR) Instrument Handbook

The eddy correlation (ECOR) flux measurement system provides in situ, half-hour measurements of the surface turbulent fluxes of momentum, sensible heat, latent heat, and carbon dioxide (CO 2 ) (and methane at the U.S. Department of Energy (DOE) Atmospheric Radiation Measurement (ARM) user facility’s North Slope of Alaska central facility [NSA Barrow], and at the ARM Mobile Facility (AMF) deployment at Oliktok Point). The fluxes are obtained with the eddy covariance technique, which involves correlation of the vertical wind component with the horizontal wind component, the air temperature, the water vapor density, and the CO 2 concentration. The instruments used are: a fast-response, three-dimensional (3D) wind sensor (sonic anemometer) to obtain the orthogonal wind components and the speed of sound (SOS) (used to derive the air temperature), an open-path infrared gas analyzer (IRGA) to obtain the water vapor density and the CO 2 concentration, and an open-path infrared gas analyzer (IRGA) to obtain methane density and methane flux at NSA Barrow and at the AMF deployment at Oliktok Point. The ECOR systems are deployed at the locations where other methods for surface flux measurements (e.g., energy balance Bowen ratio [EBBR] systems) are difficult to employ, primarily at the north edge of a field of crops. A surface energy balance system (SEBS) has been installed collocated with each deployed ECOR system in SGP, NSA, Tropical Western Pacific (TWP), and each of three ARM Mobile Facilities. The surface energy balance system consists of upwelling and downwelling solar and infrared radiometers within one net radiometer, a wetness sensor, and soil measurements. Finally, the SEBS measurements allow the comparison of ECOR sensible and latent heat fluxes with the energy balance determined from the SEBS and provide information on wetting of the sensors for data quality purposes.

47 OTHER INSTRUMENTATION↗

DOE OSTI2026

Eddy Correlation Flux Measurement System (ECOR) Instrument Handbook

The eddy correlation (ECOR) flux measurement system provides in situ, half-hour measurements of surface turbulent fluxes of momentum, sensible heat, latent heat, and carbon dioxide (CO 2 ) at the U.S. Department of Energy (DOE) Atmospheric Radiation Measurement (ARM) User Facility sites. ARM’s ECORs also historically measured methane fluxes at Utqiaġvik and Oliktok Point, Alaska. The fluxes are obtained with the eddy covariance technique, which involves correlation of the vertical wind component with the horizontal wind component, the air temperature, the water vapor density, and the CO 2 concentration.

54 ENVIRONMENTAL SCIENCES↗

DOE OSTI2025

CO2 Profiling System for CO2 Storage (a1-level)

The Southern Great Plains (SGP) carbon dioxide flux (CO2FLUX) measurement systems provide half-hour average fluxes of CO2, H2O (latent heat), sensible heat, and momentum. The systems use the eddy covariance technique, which computes the fluxes from the vertical wind speed in combination with the concentrations of CO2 and H2O, temperature, and horizontal wind speed, respectively. A 3D sonic anemometer obtains the wind components and the temperature, while an infrared gas analyzer measures CO2 and H2O. A sub-system also measures half-hour averages of radiation, meteorological, and soil measurements.

54 ENVIRONMENTAL SCIENCES↗

DOE OSTI2026

Horizontal and vertical wind speed and direction from ultrasonic wind sensor (b1-level)

Horizontal and vertical wind speed and direction from ultrasonic wind sensor (Thies Clima Ultrasonic 3D Anemometer)

anemometer↗

DOE OSTI2026

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↗

DOE OSTI2026

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↗

DOE OSTI2026

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↗

DOE OSTI2025

Robot-based Additive Manufacturing of Lego-type Modular Molds for Wind Blades

The objective of this project is to reduce the cost and lead time of horizontal wind turbine blade mold tooling and blade transportation, while maintaining the highest standards of blade quality. The solution involves a smart-design family of modular molds that are easily transportable to fabrication sites near the place of service. Key innovations include the use of additive manufacturing (AM) to integrate conformal thermal management channels, offering enhanced control over the thermal profiles tailored to specific blade materials. This approach enables in-situ quality assurance during mold fabrication, significantly improves mold life, and allows for reuse across multiple production cycles. Ultimately, the solution aims to optimize both tooling and transportation costs, contributing to the scalability of wind turbine blade production. A significant barrier to scaling up the production of large wind turbine blades lies in the high costs associated with tooling and the transportation of blades. Traditional molds are expensive, bulky, and difficult to transport, adding considerable lead time and cost to the overall manufacturing process. Additionally, transporting blades to distant locations for final assembly further exacerbates these challenges. The project aims to address these inefficiencies by demonstrating a modularized, additive-manufactured mold that meets all necessary blade specification requirements, specifically for blade lengths between 120m and 150m.

17 WIND ENERGY↗

DOE OSTI2025

Lidar-Based Evaluation of HRRR Performance in California’s Diablo Range

The performance of the NOAA High-Resolution Rapid Refresh (HRRR) model for capturing low-level winds near a wind energy production site during summer 2019 is evaluated. This study catalogs the ability of HRRR to predict boundary layer dynamics relevant to wind energy interests over complex terrain, which has presented challenges for weather and energy forecasting. Performance is evaluated by comparing HRRR output to wind-profiling Doppler lidars at Lawrence Livermore National Laboratory Site 300. HRRR captured the diurnal profile of horizontal winds in the observed 150-m layer, despite strong underpredictions (∼4 m s −1 ) during evening and nighttime hours. These underpredictions may be a result of local speedup flows observed by the lidars, which were unresolved in HRRR due to their small spatial extent. HRRR bias magnitude relative to observations was found to be minimal during days with synoptic-scale troughs and strong 850-hPa geopotential gradients, while bias magnitude was maximal during days with synoptic ridging and weak 850-hPa geopotential gradients. To translate wind speed predictions to energy forecasting, generic turbine models were used to estimate power generation for turbines characteristic of the nearby Altamont Pass Wind Resource Area. Results show that HRRR-based energy estimates predicted daytime power generation adequately relative to lidar-based estimates with an 18-h lead time (bias magnitude < 0.4 MW from 0900 to 1400 LT) but overpredicted power during the rest of the diurnal cycle (bias > 1 MW). These results demonstrate conditions under which HRRR performs well for wind energy applications in complex terrain, while highlighting biases that require further investigation to support usage of a high-resolution model for wind energy forecasts.

Boundary layer↗

DOE OSTI2025

BLOC Site - Radar Wind Profiler / Derived Data Reformatted

A radar wind profiler measures the Doppler shift of electromagnetic energy scattered back from atmospheric turbulence and hydrometeors along 3-5 vertical and off-vertical point beam directions. Back-scattered signal strength and radial-component velocities are remotely sensed along all beam directions and combined to derive the horizontal wind field over the radar. These data are typically sampled and averaged hourly or sub-hourly (15-min) and usually have 60-m and/or 100-m vertical resolutions up to 4 km for the 915 MHz system. Both a high-resolution, lower height coverage mode and a low-resolution, higher height coverage mode are used to collect the data.

17 WIND ENERGY↗

DOE OSTI2025

NANT Site - Radar Wind Profiler / Derived Data Reformatted

17 WIND ENERGY↗

DOE OSTI2026

Wind and Temperature Consensus at Horn Point, HU-Beltsville, Piney Run (Maryland) in support of CoURAGE

The Maryland Department of the Environment (MDE) operates a ground-based atmospheric profiling network consisting of collocated radar wind profilers (RWP) and radio acoustic sounding systems (RASS) as part of its Ambient Air Monitoring Program. This network provides continuous observations of wind and temperature structure in the lower troposphere to support air quality forecasting, regulatory analysis, and atmospheric research. The network currently includes three fixed sites across Maryland: Horn Point (HP, lower eastern shore) [38.587525°,-76.141006°], Howard University-Beltsville (HUB, central Maryland) [39.055277°, -76.878632°], and Piney Run (PR, western Maryland) [39.705950°, -79.012000°] The network is designed to capture regional variability in atmospheric transport and boundary-layer processes. These systems measure vertical profiles of horizontal wind speed and direction using Doppler radar techniques, with observations typically spanning from ~100 m above ground level up to approximately 2.5–4 km. Measurements are derived from the Doppler shift of backscattered electromagnetic signals, enabling retrieval of wind vectors at multiple altitudes with high temporal resolution (e.g., 30-minute averages reported every 6 minutes). Each radar wind profiler is paired with a Radio Acoustic Sounding System (RASS) to provide profiles of virtual temperature in the lower atmosphere (~100–200 m AGL) by measuring the propagation speed of acoustic waves. Together, the RWP/RASS system yields a coupled data set of thermodynamic and kinematic atmospheric structure, including additional parameters such as vertical velocity, radial velocity, signal-to-noise ratio, and spectral width for advanced analysis. There are two types of files for each station: wind data (files with a "w" prefix) and virtual temperature RASS data (files with a "t" prefix). The wind data files are in the format wYYDDD.cns, where YY is the 2-digit year and DDD is the day of the year. The RASS virtual temperature data files are in the format tYYDDD.cns. Each record has the following header structure: Line 1 : Station Name RASS files Line 2 : RASS rev DeTect_2.0, WINDS files Line 2 : WINDS rev ATI 5.1 Line 3 : N latitude, W longitude, and site elevation (m) Line 4 : Date and begin time of consensus: yy mm dd hh mn ss plus # minutes to add to get UTC Line 5 : Consensus averaging time (minutes); number of beams; number of range gates Line 6 : Number of records required to make consensus (num) total number of records (tot) and the consensus window size (m/s) in the format: num:tot (window) RASS files Line 7 : no. of coded cells, no. of spec, pulse width (ns), and inter-pulse period (µs), WINDS files Line 7 : No. of coded cells, no. of spectra, pulse width (ns), and inter-pulse period (µs), each with a pair of values: first value is for oblique beams, second for vertical RASS files Line 8 : Full scale Doppler value (m/s) Delay to first gate (ns) Number of gates Spacing of gates (ns), WINDS files Line 8 : Full scale Doppler velocity (m/s), oblique and vertical Vertical correction applied to oblique beams? (0 = no, 1 = yes) Delay to first gate (ns), oblique and vertical Number of gates, oblique and vertical Spacing of gates (ns), oblique and vertical Line 9 : Azimuth and elevation (9s indicate vertical beam not used) RASS files Line 10, values : HT = Height above ground (km), T = Uncorrected virtual temperature consensus (deg C), Tc = Corrected virtual temperature consensus (deg C), W = Vertical wind consensus (9s indicate vertical beam not used, w-component, positive upward, m/s), CNT = Number of records that made consensus (for the 3 values in same order), SNR = Average signal to noise ratio (dB) of records in consensus (same order) WINDS files Line 10, values : HT = Height above ground (km), SPD = Wind speed (m/s), DIR = Wind direction (deg E of N from N), RAD = Radial velocities for each beam (m/s) in order given in azimuth and elevation line (positive toward radar; 9s indicate vertical beam not used, CNT = Number of records that made consensus, SNR = Average signal to noise ratio (dB) of records in consensus

{"wind speed and direction",temperature}↗

DOE OSTI2024

Aerosol Vertical Turbulent Mass Flux Retrievals Through Novel Remote Sensing Algorithm

Abstract Integrated measurements of aerosol, radiation, cloud, and turbulent transport in the planetary boundary layer (PBL) are essential for understanding and modeling climate and air quality. Here, we developed a new technique for the identification of convective turbulent regions and deriving the vertical distribution of aerosol turbulent mass fluxes within PBL. The algorithm uses retrievals from coherent Doppler lidars and a high spectral resolution lidar. The technique was applied to study particle mass fluxes over 2 months (November–December 2020) during the campaign conducted at the DOE Atmospheric Radiation Measurement Southern Great Plains (SGP) site in Lamont, Oklahoma. The algorithm developed here is capable of continuously deriving vertically resolved (curtains) aerosol mass fluxes. Our data analysis shows that at the site, the 30‐min averaged fluxes at 135 m above the surface were mainly positive (upward) at ∼1 μg m −2 s −1 , suggesting that the surface is the primary source of the particle mass supplied to the boundary layer at the SGP site. Analyses of the individual case studies have revealed that not all the derived fluxes can be linked to surface emissions. Both positive and negative values in a range of ±5 μg m −2 s −1 can be caused by convective thermals interacting between the residual layer and the mixed layer and by rotation of the horizontal wind with the height. Large erroneous negative fluxes can also be caused by drizzling/precipitating clouds. We anticipate that the application of the current technique will lead to a more realistic representation of aerosol mass budgets and bidirectional mixing rates.

54 ENVIRONMENTAL SCIENCES↗

DOE OSTI2025

Evaluation of Marine Boundary Layer Clouds Over the Northeast Pacific During the CSET Campaign in E3SM Version 2

It is still challenging to reproduce marine boundary layer (MBL) clouds well in large-scale models despite their importance to the Earth's radiation budget and hydrological cycle. This study evaluates representation of the MBL and clouds in the Energy Exascale Earth System Model (E3SM) version 2. This study compares the E3SM simulation results with remote sensing and reanalysis data during the Cloud System Evolution in the Trades (CSET) field campaign to better understand the stratocumulus-to-cumulus cloud transition (SCT) over the northeast Pacific. E3SM results are extracted along the CSET Lagrangian trajectories. The comparison shows that the E3SM simulation applying horizontal wind nudging performs well in reproducing thermodynamic variables of the MBL and evolution trends of cloud variables along the trajectories. However, substantial overestimations of aerosol and cloud drop number (N d ) are observed, which is explained as an issue with version 2 of the model. Cloud fraction (CF) does decrease from the Californian coast to Hawaii in the E3SM simulation, but most CF values indicate either an overcast or almost clear sky, which differs from satellite and reanalysis data. The effect of N d overestimation on CF evolution is assessed via prescribed-N d simulations. Those simulations with N d modifications show negligible CF changes. A comparison of estimated inversion strength (EIS) also shows that the simulated EIS values are similar to those of reanalysis data. Our study suggests that cloud macrophysics and boundary layer processes are more important in improving the simulation to capture the SCT than refining the model's thermodynamics or cloud microphysics.

Choi, Kyoung Ock [Univ. of Washington, Seattle, WA↗