Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “FILES”

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 1,477 records · Page 82

100 TeV pp collisions, SM type, PYTHIA8 generator: tev100pp_qcd_pythia8_pt2700

Inclusive dijets with PT above 2700 GeV. Particle records are slimmed (all stable with pT>0.4 GeV and |eta|<4) and (PID=5 || PID=6) or PID>22 && PID<38) or PID>10 && PID<17). 40,000 events per file. The complete log files from generators are attached inside the files. The quoted cross section is approximate since based on a single file. For more accurate cross section, run over multiple files.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

100 TeV pp collisions, Exotics type, PYTHIA8 generator: tev100pp_qstar_pythia8_mbins_slim

Excited Fermions in mass range pT=5-40 TeV. 10000 events per file, 100 files per mass. Compositeness scale (Lambda) is set to the mass of the fermion, so the width is expected to be small (see the log files for details) Cross sections are included in the log files (mass dependent) Note that data are slimmed (see the log file). How to decode name: Name: tev100_pythia8_qstar_m[MASS]_[NUMBER] where [MASS] is generator-level mass as given below: Mass bins (in GeV) m[1]=5000 m[2]=10000 ......... How to use: To get a sample with a given mass, use "glob" regular expressions. Slimmed as: Particle records are slimmed (all stable with pT>0.3 GeV) and (PID=5 || PID=6) or PID>22 && PID<38) or PID>10 && PID<17).

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

100 TeV pp collisions, SM type, PYTHIA8 generator: tev100pp_minbias_a2_pythia8_l3

MinBias events used to mix with signal processes. 60k events per file. Pythia8 Minimum bias (ND+SD+DD) sample with ATLAS MB Tune A2-MSTW2008LO tune, i.e. events include non-diffractive, single diffractive and double diffractive events. Events are slimmed with pT>0.4 GeV cut. The file uses low-precision varint 1000 ("l3") for length units to make it comparable with some signal files. Due to reduced precision for decay length, this file is smaller than the standard file with 10^4 units.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

100 TeV pp collisions, SM type, PYTHIA8 generator: tev100pp_minbias_a2_pythia8_nosl

MinBias events used to mix with signal processes. 60k events per file. Pythia8 Minimum bias (ND+SD+DD) sample with ATLAS MB Tune A2-MSTW2008LO tune, i.e. events include non-diffractive, single diffractive and double diffractive events. Events are slimmed with pT>0.4 GeV cut. No slimming. The file uses low-precision varint 1000 ("l3") for length units to make it comparable with some signal files. Due to reduced precision for decay length, this file is smaller than the standard file with 10^4 units.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

13 TeV pp collisions, Top type, MADGRAPH/PY6 generator: tev13pp_mg5_ttbar_njet

top+N-jet-quark production (ttbar+N jet) at LO QCD +PS. Madgraph5 with Pythia6. Version MG5_aMC v2_3_2_2. All top decays. PYTHIA6 used for parton_shower and hadronization. PDF is 230000 (nn23lo1). See more details in the log file. Note: Number of events and cross section in the sample was estimated from a single file. The number of events varies from file to file. You need to run over all files to calculate correctly luminosity.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

Epi Archive: Automated Synthesis of Global Notifiable Disease Data

ObjectiveLANL has built software that automatically collects global notifiable disease data, synthesizes the data, and makes it available to humans and computers within the Biosurveillance Ecosystem (BSVE) as a novel data stream. These data have many applications including improving the prediction and early warning of disease events.IntroductionMost countries do not report national notifiable disease data in a machine-readable format. Data are often in the form of a file that contains text, tables and graphs summarizing weekly or monthly disease counts. This presents a problem when information is needed for more data intensive approaches to epidemiology, biosurveillance and public health.While most nations likely store incident data in a machine-readable format, governments are often hesitant to share data openly for a variety of reasons that include technical, political, economic, and motivational issues1.A survey conducted by LANL of notifiable disease data reporting in over fifty countries identified only a few websites that report data in a machine-readable format. The majority (>70%) produce reports as PDF files on a regular basis. The bulk of the PDF reports present data in a structured tabular format, while some report in natural language.The structure and format of PDF reports change often; this adds to the complexity of identifying and parsing the desired data. Not all websites publish in English, and it is common to find typos and clerical errors.LANL has developed a tool, Epi Archive, to collect global notifiable disease data automatically and continuously and make it uniform and readily accessible.MethodsWe conducted a survey of the national notifiable disease reporting systems notating how the data are reported and in what formats. We determined the minimal metadata that is required to contextualize incident counts properly, as well as optional metadata that is commonly found.The development of software to regularly ingest notifiable disease data and make it available involves three or four main steps: scraping, detecting, parsing and persisting.Scraping: we examine website design and determine reporting mechanisms for each country/website, as well as what varies across the reporting mechanisms. We then designed and wrote code to automate the downloading of the data for each country. We store all artifacts presented as files (PDF, XLSX, etc.) in their original form, along with appropriate metadata for parsing and data provenance.Detecting: This step is required when parsing structured non-machine-readable data such as tabular data in PDF files. We combined the Nurminen methodology of PDF table detection with in-house heuristics to find the desired data within PDF reports2.Parsing: We determined what to extract from each dataset and parsed these data into uniform data structures, correctly accommodating the variations in metadata (e.g., time interval definitions) and the various human languages.Persisting: We store the data in the Epi Archive database and make it available on the internet and through the BSVE. The data is persisted into a structured and normalized SQL database.ResultsThe Epi Archive tool currently contains national and/or subnational notifiable disease data from twenty nations. When a user accesses the Epi Archive site, they are prompted with four fields: country, subregion, disease of interest, and date duration. Upon form submission, a time series is generated from the users’ specifications. The generated graph can then be downloaded into a CSV file if a user is interested in performing personal analysis. Additionally, the data from Epi Archive can be reached through a REST API (Representational State Transfer Application Programming Interface).ConclusionsLANL, as part of a currently funded DTRA effort, is automatically and continually collecting global notifiable disease data. While 20 nations are in production, more are being brought online in the near future. These data are already being utilized and will have many applications including improving the prediction and early warning of disease events.References[1] van Panhuis WG, Paul P, Emerson C, et al. A systematic review of barriers to data sharing in public health. BMC Public Health. 2014. 14:1144. doi:10.1186/1471-2458-14-1144[2] Nurminen, Anssi. "Algorithmic extraction of data in tables in PDF documents." (2013).

Khalsa, Hari S.↗

$\bar{\nu}_\mu$ charged-current $\pi^0$ data release

Data release for the NOvA muon antineutrino charged-current (CC) pi^0 cross section presented in arXiv:2511.05807. The signal for this analysis is defined as muon antineutrino CC interactions in the fiducial volume of the NOvA near detector (a 2.7 m × 2.7 m × 9.0 m region) that produce at least one pi^0 in the final state emerging from the nucleus, within the phase space of muon momentum [0.5, 2.5) GeV/c and muon angle [0, 60) degree, as described in arXiv:2511.05807. The released zip file contains two files: NOvA_NumubarCCPi0_DataRelease.root README.txt The ROOT file includes the cross-section results as well as the statistical and systematic covariance matrices for each variable used in this analysis. The README provides a detailed description of the contents of the data release. Official Flux: The flux used in this analysis is available from the NOvA Public Docs: https://publicdocs.fnal.gov/cgi-bin/ShowDocument?docid=8. File structure --- The ROOT file contains the following TDirectories: pi0p - pi^0 momentum distributions pi0dir - pi^0 angular distributions muonp - muon momentum distributions muondir - muon angular distributions Q2 - reconstructed Q^2 distributions Wmass - reconstructed W_mass distributions Each directory contains three histograms: xsec (TH1D): Cross section result cov_stat (TH2D): Statistical covariance matrix cov_syst (TH2D): Systematic covariance matrix Usage notes: - xsec gives the measured differential cross section w.r.t. the corresponding variable. - cov_stat and cov_syst provide the full covariance matrices. - The bin definitions and kinematic phase spaces follow those used in arXiv:2511.05807. Citation --- If you use these data, please cite: NOvA Collaboration, arXiv:2511.05807.

Wu, Wanwei [Pittsburgh U.] (ORCID:0000000326327215↗

Dataset and scripts for manuscript "Using Neural Network Ensembles to Separate Ocean Biogeochemical and Physical Drivers of Phytoplankton Biogeography in Earth System Models"

Please note: The title of this version contains an updated title for the manuscript compared to the previous version of this dataset. This is only due to title updates during the peer review process for the manuscript. The zip file contains the scripts, functions, and source files for the manuscript titled "Using Neural Network Ensembles to Separate Ocean Biogeochemical and Physical Drivers of Phytoplankton Biogeography in Earth System Models." The manuscript has been submitted for peer review. Please consult the README file for information on the specifications of the files. These files may occasionally be updated to add annotations to the scripts to make them more user friendly and to correct any errors.

54 ENVIRONMENTAL SCIENCES↗

ARM - Midlatitude Continental Convective Clouds Microwave Radiometer Profiler (jensen-mwr)

A major component of the Mid-latitude Continental Convective Clouds Experiment (MC3E) field campaign was the deployment of an enhanced radiosonde array designed to capture the vertical profile of atmospheric state variables (pressure, temperature, humidity wind speed and wind direction) for the purpose of deriving the large-scale forcing for use in modeling studies. The radiosonde array included six sites (enhanced Central Facility [CF-1] plus five new sites) launching radiosondes at 3-6 hour sampling intervals. The network will cover an area of approximately (300)2 km2 with five outer sounding launch sites and one central launch location. The five outer sounding launch sites are: S01 Pratt, KS [ 37.7oN, 98.75oW]; S02 Chanute, KS [37.674, 95.488]; S03 Vici, Oklahoma [36.071, -99.204]; S04 Morris, Oklahoma [35.687, -95.856]; and S05 Purcell, Oklahoma [34.985, -97.522]. Soundings from the SGP Central Facility during MC3E can be retrieved from the regular ARM archive. During routine MC3E operations 4 radiosondes were launched from each of these sites (approx. 0130, 0730, 1330 and 1930 UTC). On days that were forecast to be convective up to four additional launches were launched at each site (approx. 0430, 1030, 1630, 2230 UTC). There were a total of approximately 14 of these high frequency launch days over the course of the experiment. These files contain brightness temperatures observed at Purcell during MC3E. The measurements were made with a 5 channel (22.235, 23.035, 23.835, 26.235, 30.000GHz) microwave radiometer at one minute intervals. The results have been separated into daily files and the day of observations is indicated in the file name. All observations were zenith pointing. Included in the files are the time variables base_time and time_offset. These follow the ARM time conventions. Base_time is the number seconds since January 1, 1970 at 00:00:00 for the first data point of the file and time_offset is the offset in seconds from base_time.

54 ENVIRONMENTAL SCIENCES↗

ARM - Midlatitude Continental Convective Clouds - Ultra High Sensitivity Aerosol Spectrometer(tomlinson-uhsas)

Ultra High Sensitivity Aerosol Spectrometer (UHSASA) A major component of the Mid-latitude Continental Convective Clouds Experiment (MC3E) field campaign was the deployment of an enhanced radiosonde array designed to capture the vertical profile of atmospheric state variables (pressure, temperature, humidity wind speed and wind direction) for the purpose of deriving the large-scale forcing for use in modeling studies. The radiosonde array included six sites (enhanced Central Facility [CF-1] plus five new sites) launching radiosondes at 3-6 hour sampling intervals. The network will cover an area of approximately (300)2 km2 with five outer sounding launch sites and one central launch location. The five outer sounding launch sites are: S01 Pratt, KS [ 37.7oN, 98.75oW]; S02 Chanute, KS [37.674, 95.488]; S03 Vici, Oklahoma [36.071, -99.204]; S04 Morris, Oklahoma [35.687, -95.856]; and S05 Purcell, Oklahoma [34.985, -97.522]. Soundings from the SGP Central Facility during MC3E can be retrieved from the regular ARM archive. During routine MC3E operations 4 radiosondes were launched from each of these sites (approx. 0130, 0730, 1330 and 1930 UTC). On days that were forecast to be convective up to four additional launches were launched at each site (approx. 0430, 1030, 1630, 2230 UTC). There were a total of approximately 14 of these high frequency launch days over the course of the experiment. These files contain brightness temperatures observed at Purcell during MC3E. The measurements were made with a 5 channel (22.235, 23.035, 23.835, 26.235, 30.000GHz) microwave radiometer at one minute intervals. The results have been separated into daily files and the day of observations is indicated in the file name. All observations were zenith pointing. Included in the files are the time variables base_time and time_offset. These follow the ARM time conventions. Base_time is the number seconds since January 1, 1970 at 00:00:00 for the first data point of the file and time_offset is the offset in seconds from base_time.

54 ENVIRONMENTAL SCIENCES↗

Electric Field Data from the North Slope of Alaska

File contains raw as well as calibrated electric field values (V/m) from two CS110 electric field meters. The file also contains raw 2-m U and V winds at the same site. The sampling rate is 1Hz. All files contain raw electric field data, as well as calibrated values to a one week ground-based calibration setup. During this week, simultaneous upward-facing ground based electric field measurements were taken alongside the two downward facing instruments on the pole (CS110-3 at 2m and CS110-2 at 5m). Slopes and intercepts were calculated and applied to the values influenced by the pole to convert the raw data to calibrated values. These calibrated values are absolute electric field measurements. There are no missing data codes. The missong data is not included in the files, and thus any files with missing data will be shorter than the normal 86,400 values. In July 2023, the CS110-3 was replaced with an identical instrument named CS110-8, and the CS110-2 was replaced with an identical instrument called CS110-9. All the variable names remained consistent and the same.

54 ENVIRONMENTAL SCIENCES↗

Combined Mesonet and Tracker

Title: Combined Mesonet and Trackers (UNL Mobile Mesonets) Authors University of Nebraska PI: Adam Houston, UNL Professor (ahouston2@unl.edu) Mailing Address: 126 Bessey Hall P.O. Box 880340 Lincoln, NE 68588-0340 CoMeT Overview The University of Nebraska-Lincoln operates three Combined Mesonet and Tracker (CoMeTs). CoMeTs are Ford Explorers (model years 2015, 2017, and 2019) with forward-mounted suites of meteorological sensors and dual moonroofs, combining the capability of a mobile mesonet to collect near-surface observations with the capability of an unmanned aircraft systems (UAS) tracker vehicle, which enables an observer in the second row of seats to see the aircraft and maintain compliance with Federal Aviation Administration policies on UAS operation. The CoMeTs collect observations of slow temperature and humidity at ~2 m above ground level (AGL) using a Vaisala HMP155A, fast temperature at ~2 m AGL using a Campbell Scientific 109SS-L thermistor, pressure at ~2.5 m AGL using a Vaisala PTB210, wind speed and direction at ~3.25 m AGL using an R.M. Young 05103 propeller anemometer, and vehicle heading using a KVH Industries C-100 fluxgate compass (Barbieri et al. 2019). The HMP155A and 109SS-L thermistor are shielded and aspirated within a U-tube (Waugh and Frederickson 2010; Houston et al. 2016). This list of sensors is also included in the CoMeT data file metadata. Manufacturer specifications for these instruments are given in Table 1 of Hanft and Houston (2018). The reported measured quantities are summarized below.CoMeT-3 was funded through an equipment allocation included in the NSF TORUS award (AGS-1824649). Instrument Description The specific sensors included on each CoMeT are summarized in the table at the end of this section. In general each CoMeT collects observations of slow temperature and humidity at ~2 m above ground level (AGL) using a Vaisala HMP155, fast temperature at ~2 m AGL using a Campbell Scientific 109SS-L thermistor, pressure at ~2.5 m AGL using a Vaisala PTB210 barometer with a Gill pressure port, wind speed and direction at ~3.25 m AGL using an R.M. Young 05103 propeller anemometer, position using a Garmin 19x HVS receiver, and vehicle heading using a KVH Industries C-100 fluxgate compass. The HMP155 and 109SS are shielded and aspirated within a U-tube (Waugh and Frederickson 2010; Houston et al. 2016). Fast temperature and corrected RH measurements (using sensors housed within the U-tube) have a time constant of 10-12 s based on data collected across a temperature and RH shock during the CLOUD-MAP 2017 calibration/validation tests on June 26, 2017. Vehicle speed was < 10 kts for this test. CoMeT-1 CoMeT-2 CoMeT-3 Slow Temperature Slow RH Vaisala HMP155A-L20-PT Part #: 22280-7 Vaisala HMP155E Part #: E1AA11A0B1A1A0A Vaisala HMP155E Part #: E1AA11A0B1A1A0A Fast temperature Campbell Scientific 109SS-L20-PT Part #: 21448-3 Campbell Scientific 109SS-L12-PW Part #: 21448-109 Campbell Scientific 109SS-L12-PW Part #: 21448-150 Pressure Vaisala PTB-210 Part #: A1A1B Gill Pressure Port Part #: 61002 Vaisala PTB-210 Part #: A1A1B Gill Pressure Port Part #: 61002 Vaisala PTB-210 Part #: A1A1B Gill Pressure Port Part #: 61002 Wind RM Young 05103-L20-PT Part #: 18435-310 RM Young 05103-L20-PW Part #: 18435-244 RM Young 05103-L20-PW Part #: 18435-244 GPS Garmin GPS 19x HVS (NMEA 0183) Part #: 010-01010-00 Garmin GPS 19x HVS (NMEA 0183) Part #: 010-01010-00 Garmin GPS 19x HVS (NMEA 0183) Part #: 010-01010-00 Compass KVH C-100 Part #: 01-0177-15 KVH C-100 Part #: 01-0177-15 KVH C-100 Part #: 01-0177-15 Logger Campbell Scientific CR6-NA-XT-SW Part #: 28385-9 Campbell Scientific CR6-WIFI-XT-SW Part #: 28385-6 Campbell Scientific CR6-WIFI-XT-SW Part #: 28385-6 Data Collection and Real-Time Processing The reported measured quantities are summarized in the table below. Quantity Units Source Epoch time Seconds GPS Latitude and longitude Degrees GPS Altitude m GPS Pressure hPa PTB210 Temperature (fast) deg C 109SS-L Temperature (slow) deg C HMP155 RH (slow) % HMP155 Vehicle speed m/s GPS Vehicle heading deg C-100 and GPS In addition to the measured variables, several derived variables are calculated. Corrected/fast relative humidity (%) Relative humidity is adjusted to the fast temperature following Richardson et al. (1998) and Houston et al. (2016). Water vapor mixing ratio (g/kg) Dew point temperature (&deg;C) Potential temperature (Kelvin) Virtual potential temperature (Kelvin) Equivalent potential temperature (Kelvin) Regular intercomparisons between all three CoMeTs were performed during TORUS 2019. Comparisons were also conducted between CoMeT-1 and CoMeT-2 during LAPSE-RATE (2018) on 14 July. In these intercomparisons, the vehicles were parked adjacent to each other aligned perpendicular to (and facing into) the wind. To minimize engine heating effects, intercomparisons were only conducted when the wind speed was >10 kts. Data Format Original data files for each deployment are saved as text files and then converted to NetCDF. NetCDF versions have units that are CF compliant and may not match the original units in the txt files. The naming convention for the NetCDF files is as follows: UNL.CoMeT3.{deployment date YYYYMMDD}.{start time of observation collection in UTC HHMM}.L2.{post-processing codes}.cdf example: UNL.CoMeT3.20190627.1931.L2.g1.f1.cdf Post-processing codes are included to track modifications to the raw data. These codes are closely connected to error flags associated with each record. Each letter corresponds to a particular instrument: g: GPS p: Barometer tf: Fast temperature ts: Slow temperature rh: Relative humidity f: Compass w: Wind monitor a: All instruments Each number corresponds to a particular post-processing action described more below. Measured and derived variables are included in the following table. Variable Heading Standard Name Units time Time seconds since 00:00:00, 01-01-1970 Alt Altitude meters lat Latitude degrees north lon Longitude degrees east fast_temp Air Temperature kelvin slow_temp Air Temperature kelvin pressure Air Pressure pascals logger_RH Relative Humidity percent calc_corr_RH Relative Humidity percent wind_speed Wind Speed meters per second wind_dir Wind From Direction degrees vehicle_dir Vehicle Direction degrees dewpoint Dew Point Temperature kelvin mixing_ratio Humidity Mixing Ratio g/g theta Air Potential Temperature kelvin theta_v Virtual Potential Temperature kelvin theta_e Equivalent Potential Temperature Kelvin error_flag The error_flag variable is a string that matches the post-processing codes listed above. All instruments will have an associated code, but will have a &ldquo;0&rdquo; if the datum is unchanged from the initial processed value. Error Codes The following table summarizes the error codes for data collected before 2020: Error Code Relevant CoMeT Description g1 1,2,3 Exact correction. GPS position and time reprocessed from raw data g2 1 As far as we can tell this is an exact correction to an error in the GPS time. During the correct time periods the time suddenly went backwards ~250s and stayed at this offset for 750s when it corrected itself. The offset was applied to the &ldquo;time warp&rdquo; period. p1 2 Approximate correction. Hole in the pressure tube connecting the pressure port to the barometer. Resulted in erroneously low air pressure measurements when the vehicle was in motion. Derived variables recalculated (dew point temperature [e depends on qv and p], water vapor mixing ratio, potential temperature, virtual potential temperature, equivalent potential temperature) a1 3 Exact correction. Missing data reprocessed from raw data a2 1 Bug fix to bias correction for ts1, ts2, and rh1: water vapor mixing ratio was off by a factor of 10 and virtual potential temperature was wrong because of this. f1 3 No correction, missing data. Fluxgate compass inoperable. Wind speed and direction calculated using GPS-derived vehicle heading instead. rh1 1 Approximate correction. Constant bias of +1.7% removed from relative humidity. Derived variables recalculated (corrected/fast relative humidity, dew point temperature, water vapor mixing ratio, virtual potential temperature, equivalent potential temperature) ts1 1 Approximate correction. Constant bias of +0.6 K removed from slow temperature. Derived variables recalculated (corrected/fast relative humidity, dew point temperature, water vapor mixing ratio, virtual potential temperature, equivalent potential temperature) ts2 1 Approximate correction. Constant bias of +1.0 K removed. Derived variables recalculated (corrected/fast relative humidity, dew point temperature, water vapor mixing ratio, virtual potential temperature, equivalent potential temperature) References Bolton, D., 1980: The Computation of Equivalent Potential Temperature. Mon. Wea. Rev., 108, 1046&ndash;1053, https://doi.org/10.1175/1520-0493(1980)108<1046:TCOEPT>2.0.CO;2. Hanft, W., and A. L. Houston, 2018: An Observational and Modeling Study of Mesoscale Air Masses with High Theta-E. Mon. Wea. Rev., 146, 2503&ndash;2524, https://doi.org/10.1175/MWR-D-17-0389.1.Wexler Houston, A. L., R. J. Laurence III, T. W. Nichols, S. Waugh, B. Argrow, and C. L. Ziegler, 2016: Intercomparison of unmanned aircraft-borne and mobile mesonet atmospheric sensors. Journal of Atmospheric and Oceanic Technology. 33, 1569-1582, doi: 10.1175/JTECH-D-15-0178.1. Lowe, P. R., 1977: An Approximating Polynomial for the Computation of Saturation Vapor Pressure. J. Applied Meteorology, 16, 100&ndash;103. Richardson, S. J., S. E. Frederickson, F. V. Brock, and J. A. Brotzge, 1998: Combination temperature and relative humidity probes: Avoiding large air temperature errors and associated relative humidity errors. Preprints, 10th Symp. On Meteorological Observations and Instrumentation, Phoenix, AZ, Amer. Meteor. Soc., 278&ndash;283. Waugh, S., and S. E. Frederickson, 2010: An improved aspirated temperature system for mobile meteorological observations, especially in severe weather. 25th Conf. on Severe Local Storms, Denver, CO, Amer. Meteor. Soc., P5.2. [Available online at https://ams.confex.com/ams/25SLS/techprogram/paper_176205.htm.]

54 ENVIRONMENTAL SCIENCES↗

CCN PI sample dataset from two BNF facilities

This dataset contains CCN instrument data files showing the sample time series of CCN concentrations in #/cm^3. The file also shows the instrument records and CCN data. The CCN_S20_data_250605000000.csv data file contains information from the S20 facility at Courteland, and the CCN_S30_data_250605000000.csv data file contains information from the S30 facility at Falkville. See the attached CCN-200 Manual for information about the variables and units with the data files.

ccn↗

The Importance of Freeze/Thaw Cycles on Lateral Transport in Ice-Wedge Polygons: Modeling Archive

This Modeling Archive is in support of an NGEE Arctic publication "The importance of freeze/thaw cycles on lateral transport in ice-wedge polygons". The dataset includes xml input/configuration files. These files are compatible with the ATS version 1.0 and higher. The mesh folder contains mesh files used for high-centered polygon (hcp) and low-centered polygon (lcp). The mesh files represent the transect of the polygonal tundra (Fig 1). Here we used two types of mesh with impermeable layer and without. The mesh with an impermeable layer corresponds to the synthetic permafrost (no freezeup case). The freeze up case uses mesh without impermeable layer to simulated frozen ground start at the same depth where the impermeable layer is for the no freezeup case. The meteorological data used drive the model saved in the "inputs" folder. The processed tracer flow rates are saved in the "tracer-flow-ratesCfolder. To plot figures 1 and 2, we used VisIt software. To plot all the flow rates, we used ipython notebook script. All required inputs are saved in "freezeup" and "no freezeup" folders. Each folder includes the corresponding "lcp" and "hcp" folders. The "freezeup" folder has also flat-centered polygon (fcp) case, low porosity "lpor", and low permeability "lper" cases. Included are *.xml, *.exo, *.h5, *pdf, *.ipynb, *.sh, *.py, and *.out files. NGEE Arctic Project Summary: The Next-Generation Ecosystem Experiments: Arctic (NGEE Arctic), was a research effort to reduce uncertainty in Earth System Models by developing a predictive understanding of carbon-rich Arctic ecosystems and feedbacks to climate. NGEE Arctic was supported by the Department of Energy's Office of Biological and Environmental Research. The NGEE Arctic project had two field research sites: 1) located within the Arctic polygonal tundra coastal region on the Barrow Environmental Observatory (BEO) and the North Slope near Utqiagvik (Barrow), Alaska and 2) multiple areas on the discontinuous permafrost region of the Seward Peninsula north of Nome, Alaska. Through observations, experiments, and synthesis with existing datasets, NGEE Arctic provided an enhanced knowledge base for multi-scale modeling and contributed to improved process representation at global pan-Arctic scales within the Department of Energy's Earth system Model (the Energy Exascale Earth System Model, or E3SM), and specifically within the E3SM Land Model component (ELM).

54 ENVIRONMENTAL SCIENCES↗

Behavioral Ensemble CLM5 Hydrological Parameter Sets

This repository contains hydrological parameter sets derived using the hybrid regionalization method for three distinct streamflow signatures: Streamflow Signatures: Q10: Represents low flow, indicating the nonexceedance probability of 0.1 for daily streamflow. Q90: Represents high flow, with a nonexceedance probability of 0.9 for daily streamflow. Qmean: Indicates the mean annual flow. Parameters for 464 CAMELS Basins: CAMELS_1000_parameters.csv: Contains 1,000 ensemble parameter sets generated using the Latin hypercube sampling method for CLM5, encompassing 15 hydrological parameters. CAMELS_q10_behavioral_parameter_num.csv: Provides the behavioral ensemble parameter sets for the Q10 streamflow signature for each basin. The associated ID number refers to entries in the CAMELS_1000_parameters.csv file. A minimum of 10 ensemble parameter sets are available for each basin. CAMELS_q90_behavioral_parameter_num.csv: Similar to the above file but for the Q90 streamflow signature. CAMELS_qmean_behavioral_parameter_num.csv: Corresponds to the Qmean streamflow signature, similar to the previous files. Parameters for 50,629 1/8° CONUS Land Grid Cells: CONUS_350_parameters.csv: Contains 350 ensemble parameter sets derived using the Latin hypercube sampling method for CLM5's 15 hydrological parameters within 1/8° CONUS land grid cells. CONUS_q10_behavioral_parameter_num.csv: Holds the behavioral ensemble parameter sets for the Q10 streamflow signature, organized for each grid cell. The ID number relates to entries in CONUS_350_parameters.csv. A minimum of 10 ensemble parameter sets are provided for each grid cell. CONUS_q90_behavioral_parameter_num.csv: Similar to the above file but focusing on the Q90 streamflow signature. CONUS_qmean_behavioral_parameter_num.csv: Corresponds to the Qmean streamflow signature, following a similar structure to the previous files.

Yan, Hongxiang↗

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↗