Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “text file”

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 91 records · Page 5

A Solid State Zwitterionic Plastic Crystal with High Static Dielectric Constant

The dielectric data in Figure 3, Figure 4, Figure S6 of the published paper was extracted from 2EOIMTSA-BDS-DATA .txt file. This file can be directly opened using a text file editor. It can also be imported to Excel/ Origin for further plotting and analysis. The G' and G'' in Figure 3 of the publihsed paper was plotted from data in file 2EOImTSA-temperature-sweep.xlsx. This file can be directly opend using Excel. The details of DFT simulations mentioned in Figure 2, Figure 7, and Figure S9 of the published paper are included in the DFT.zip file.

Huang, Zitan [Pennsylvania State University]↗

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↗

Adams-Based Rover Terramechanics and Mobility Simulator - ARTEMIS

The Mars Exploration Rovers (MERs), Spirit and Opportunity, far exceeded their original drive distance expectations and have traveled, at the time of this reporting, a combined 29 kilometers across the surface of Mars. The Rover Sequencing and Visualization Program (RSVP), the current program used to plan drives for MERs, is only a kinematic simulator of rover movement. Therefore, rover response to various terrains and soil types cannot be modeled. Although sandbox experiments attempt to model rover-terrain interaction, these experiments are time-intensive and costly, and they cannot be used within the tactical timeline of rover driving. Imaging techniques and hazard avoidance features on MER help to prevent the rover from traveling over dangerous terrains, but mobility issues have shown that these methods are not always sufficient. ARTEMIS, a dynamic modeling tool for MER, allows planned drives to be simulated before commands are sent to the rover. The deformable soils component of this model allows rover-terrain interactions to be simulated to determine if a particular drive path would take the rover over terrain that would induce hazardous levels of slip or sink. When used in the rover drive planning process, dynamic modeling reduces the likelihood of future mobility issues because high-risk areas could be identified before drive commands are sent to the rover, and drives planned over these areas could be rerouted. The ARTEMIS software consists of several components. These include a preprocessor, Digital Elevation Models (DEMs), Adams rover model, wheel and soil parameter files, MSC Adams GUI (commercial), MSC Adams dynamics solver (commercial), terramechanics subroutines (FORTRAN), a contact detection engine, a soil modification engine, and output DEMs of deformed soil. The preprocessor is used to define the terrain (from a DEM) and define the soil parameters for the terrain file. The Adams rover model is placed in this terrain. Wheel and soil parameter files can be altered in the respective text files. The rover model and terrain are viewed in Adams View, the GUI for ARTEMIS. The Adams dynamics solver calls terramechanics subroutines in FORTRAN containing the Bekker-Wong equations.

Trease, Brian P.↗

SOFC Microstructures (PFIB-SEM and synthetic) from JPS 2018

This is the microstructural data used in the publication "Mesoscale characterization of local property distributions in hetergeneous electrodes" by Tim Hsu, William K. Epting, Rubayyat Mahbub, et al., published in the Journal of Power Sources in 2018. (DOI 10.1016/j.jpowsour.2018.03.025). Included are a commercial cathode and anode active layer (Materials and Systems Research, Inc., Salt Lake City, UT) imaged by Xe plasma FIB-SEM (FEI, Hillsboro, OR), and four synthetic microstructures of varying particle size distribution widths generated by DREAM3D (BlueQuartz Software, Springboro, OH). For the MSRI electrodes, both the original greyscale and the segmented versions are provided. Each .zip file contains a "stack" of .tif image files in the Z dimension, and an .info ascii text file containing useful information like voxel sizes and phase IDs. More details can be found in the pertinent publication at http://dx.doi.org/10.1016/j.jpowsour.2018.03.025.

FIB-SEM,SOFC,microstructure↗

2D reactive transport model of shale chemical weathering and biogeochemical fluxes along a mountainous hillslope, East River Watershed, Colorado: Input files and simulation results

This data package contains input files and simulation results for a two-dimensional (2D) reactive transport model used to quantitatively analyze the coupled hydrological and biogeochemical processes governing shale weathering and associated biogeochemical fluxes under realistic environmental conditions in the high-elevation East River Watershed. These data support the conclusions presented in Stolze et al. (Water Resources Research, under review), "Model-based interpretation of solute exports and carbon partitioning during shale weathering in a mountainous hillslope". The model simulates atmospheric-subsurface gas exchange, subsurface water flow, and shale weathering processes under dynamic, year-scale conditions along a shale-underlain hillslope located in the East River watershed. The simulations were performed using the PFLOTRAN flow and reactive transport code and executed on the Perlmutter supercomputer to leverage its large-scale parallel computing capabilities. The data package contains two zipped folders, "model_input_files" and "simulation_results", and one readme.txt file. "model_input_files" contains the necessary input files to run the calibrated base-base model presented in Stolze et al. (Water Resources Research, under review). "simulation_results" contains a single hdf5 file ("Output_2D_hillslope_model.h5") which includes the results of simulation performed using the base-case model. This file can be opened with HDFView 3.1.4, Python, or MATLAB. "readme.txt" contains relevant information about the base-case model and provides guidelines on how to run the associated input files provided in the folder "model_input_files". Furthermore, readme.txt provides information regarding the model results provided in "Output_2D_hillslope_model.h5" such as matrix dimensionality and output units. Field datasets used to evaluate model performance were collected at three monitoring wells located along a hillslope transect (PLM1, PLM2, and PLM3). Dissolved ion concentration data were collected from November 2016 to October 2021 for Ca, Mg, DIC, Na, K, SO4 (Dong et al., 2025 - dic_npoc_data_2014_2024.zip - DOI:10.15485/1660459; Williams et al., 2025 - anion_data_2014_2024.zip - DOI:10.15485/1668054; Dong et al., 2025 - cation_data_2014_2024.zip - DOI:10.15485/1668055). Note that we used the files named er_PLM1_xx_yy, er_PLM2_xx_yy, and er_PLM3_xx_yy where xx stands for the name of the aqueous species and yy stands for the depth where the measurements were performed. Soil water content ([0 - 1] m) and water table depth were collected from November 2016 to October 2021 (Wan et al., 2024 - Dynamic_water_table__depthsFig2b.csv and Soil_water_content_Fig4e.csv - DOI:10.15485/2322567). Gaseous CO2 concentration were collected from October 2020 to December 2021(Wan et al., 2024 - Soil_CO2_concentrations_Fig4h.csv - DOI:10.15485/2322567) Gaseous CO2 flux from the subsurface to the atmosphere were collected in the vicinity of PLM2 from October 2019 to May 2022 (Wu et al., 2025). Soil microbial biomass concentration was measured from August 2016 to June 2017 (Sorensen et al., 2019 - 2017_East_River_Pumphouse_Microbial_Biomass__1_.csv - DOI:10.15485/1577267) All field data are published as CSV files compatible with Microsoft Excel, MATLAB, and Python, or as text files. The coordinates of the monitoring wells and the CO2(g) flux sensor in the coordinate system WGS84 are: -PLM1: [38.9197710 ; -106.9492750] -PLM2: [38.9201580 ; -106.9487170] -PLM3: [38.9207843 ; -106.9483668] -PLM4: 38.9210060 ; -106.9479528] -CO2(g) flux sensor: [38.9199180 ; -106.9489906] ------------------------------------------------------------------------------------------- This work was supported by the Watershed Function Science Focus Area at Lawrence Berkeley National Laboratory funded by the US Department of Energy, Office of Science, Biological and Environmental Research under Contract No. DE-AC02-05CH11231. This research used resources of the National Energy Research Scientific Computing Center (NERSC), a Department of Energy User Facility using NERSC award BER-ERCAP 23980, BER-ERCAP 28550, and BER-ERCAP 33789.

54 ENVIRONMENTAL SCIENCES↗

Asynchronous file transfer to IBM PC's

The Asynchronous File Transfer System is used for interactively selecting and tramsmitting text files from the Langley Research Center's Business Data Systems Division (BDSD) host processor to an IBM Personal Computer. The IBM asynchronous communications support package is used for handling the communications on the personal computer. An application program (NATURAL, COBOL, etc.) is used for selecting and formatting the records to be transmitted, and three subroutine modules residing on the BDSD host processor are used for interfacing the application program and the communications software. Each record transmitted to the Personal Computer must be in the standard ASCII format. This record format is directly accessible by BASIC and many of the personal computer software packages provide utility programs for converting them to the format required for the particular package in question.

Hoerger, J.↗

Data, model inputs, and analysis scripts associated with a manuscript on stream intermittency controls across spatial scales in Pacific Northwest watersheds

NOTE: The manuscript associated with this data package is currently in review. The data may be revised based on reviewer feedback. Upon manuscript acceptance, this data package will be updated with the final dataset and additional metadata. This data package is associated with the manuscript "Hydroclimatic Memory and Watershed Template Shape Stream Intermittency: Multi-scale Attribution Using Process-based Simulation and Explainable ML" by Niroula et al. (2026), submitted to Water Resources Research (WRR). The study investigates the dominant controls on stream intermittency across local, reach, and watershed scales using a coupled process-based simulation and explainable machine-learning framework. Long-term daily simulations from the Advanced Terrestrial Simulator (ATS) were used to generate wetness states and ponded-depth responses over river-corridor cells. These ATS outputs were then aggregated across scales and used to train XGBoost (eXtreme Gradient Boosting) models. SHAP (SHapley Additive exPlanations) was applied to quantify the relative importance of hydroclimatic forcings, watershed template attributes, and antecedent-memory effects in shaping intermittency behavior. The analysis is carried out for three contrasting Pacific Northwest watersheds: Oak Creek (OCW), American River Watershed (ARW), and H.J. Andrews (HJA). Across these testbeds, the package contains ATS-ready watershed inputs, ATS run configuration and selected output files, model-evaluation data products, intermittency-analysis datasets, machine-learning target-feature tables, SHAP outputs, and notebooks used to organize, analyze, and visualize results. At a high level, the package documents a workflow in which ATS provides the physically based simulation backbone and explainable machine learning is used as a post-processing attribution tool. The contents are intended to support interpretation of the manuscript figures and results, provide context for how intermittency metrics were generated at multiple scales, and preserve the key artifacts needed to understand and reuse the analysis workflow. The package contains a high-level directory summary file (`summary.txt`) and four main content folders (1) `evaluation_plots` contains evaluation figures and supporting evaluation datasets; (2) `intermittency_plots` contains intermittency-focused analysis notebook and prepared datasets; (3) `ml-training-and-shap_values_plots` contains ML training inputs, SHAP outputs, and figure-generation notebooks; and (4) `watershed_mesh_and_ats_input` contains ATS model setup materials, forcing inputs, geometry, and selected run files. More specifically, the `evaluation_plots` folder contains the notebook used for ATS evaluation plotting and site-specific evaluation datasets. These include evapotranspiration and water-balance products for three watersheds, as well as an Oak Creek field-measurement discharge file. The `intermittency_plots` folder contains the notebook used for intermittency analysis and the prepared datasets used to analyze intermittent and non-intermittent wetness behavior across the study watersheds. The `ml-training-and-shap_values_plots` folder contains notebooks and outputs for the machine-learning and explainability workflow. This includes the main XGBoost and SHAP notebook(s), a beeswarm plotting notebook, target-feature tables for machine-learning training, SHAP summary tables, and per-sample SHAP value archives. The `watershed_mesh_and_ats_input` folder contains ATS-related watershed inputs and supporting materials. This includes mesh and shape products, ATS-readable LAI and meteorological forcing inputs, selected ATS spinup and transient-run files, and a watershed workflow example notebook. Subdirectories are organized by watershed where applicable.All files are .cpg (codepage files), .csv (comma-separated values), .dbf (database files), .exo (Exodus mesh format), .h5 (HDF5 format), .ipynb (Jupyter notebooks), .pkl (Python pickle), .prj (projection files), .sh (shell scripts), .shp (shapefile geometry), .shx (shapefile index), .txt (text files), or .xml (markup data).

Advanced Terrestrial Simulator↗

ATOMIC Simulations and Experimental Data for Sodium and Copper Mixtures

This data consists of simulations and experimental measurements of laser-induced breakdown spectroscopy (LIBS). The simulations are produced by ATOMIC, a general purpose plasma modeling and kinetics code that has been designed to compute emission (or absorption) spectra from plasmas [1]. Our overall suite of simulations contains 12 sets of simulations: training and validation sets of simulations for each of two resolutions of each of sodium, copper, and mixtures of the two. The training data were produced using a 500-run design that varies input parameters temperature (T), electron density (Ne), proportion of sodium (pNa), and proportion of copper (pCu). The latter two variables sum to one and are unused in the single-element simulations. The validation data was produced with a 25-run design. The coarse simulations produce spectra over a range of 240nm - 880nm that roughly mimics the range collected by the ChemCam instrument on the Mars rover Curiosity. The fine resolution simulations produce spectra over a range of 550nm to 600nm and were produced to mimic the included experimental results. The experimental results cover four mixtures of sodium and copper. All data sets are kept in zip files whose names indicate the elemental composition (NaCu, Na, or Cu), resolution (coarse or fine), and purpose (training or validation) with file names numbered to indicate the line in the design files used to produce the simulation. The designs are provided as text files with names indicating their purpose. The experimental data is provided as a CSV file. See attached abstract for figures.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗

ATOMIC Simulations and Experimental Data for Basalt-like Compounds

This data consists of simulations and experimental measurements of laser-induced breakdown spectroscopy (LIBS). The simulations are produced by ATOMIC, a general purpose plasma modeling and kinetics code that has been designed to compute emission (or absorption) spectra from plasmas [2]. The makeup of the plasma was considered to be divided into some proportion water, some proportion Martian atmosphere (CO2), and some proportion target (from the rock or object impacted by the laser), where these proportions add to 1. Based on expert knowledge, the proportion of water was kept in the range [0.0,0.5] and the proportion of atmosphere was kept in the range [0.02, 0.9]. Our overall suite of simulations contains six sets of simulations that differ in which elements were considered to make up the target. Within each set, we used uniformly drawn temperatures and log mass densities within pre-specified ranges. The temperature range was [0.5,1.5] eV and the log (base 10) mass density range was [-7,-4]. The proportion of water, atmosphere, and target were drawn from a symmetric Dirichlet distribution, but draws in which the propor- tion of water or atmosphere exceeded the pre-specified limits were rejected from the design. Up to eleven constituent elements (Si, Al, Fe, Mg, Ca, O, Ti, Mn, Na, K, P) were considered for the target, as they are the most common elements found in basalt compounds and were used in [1]. For each run, the proportions of the constituent elements making up the target were drawn from a symmetric Dirichlet distribution. We ran 1,350 simulations that included nonzero proportions of all eleven elements. We also ran simulations which excluded some of these elements. In particular, we ran 1,000 simulations that only included nonzero proportions for the six most common elements (Si, Al, Fe, Mg, Ca, O). We also ran five sets, each with 500 simulations, that only included nonzero proportions for five of the six most common elements (but where all sets included O). Thus, we generated a total of 4,850 spectra representing basalt-like compounds in which the target was comprised of oxygen and between four and ten other elements. The ATOMIC code produced spectra over a range of 240nm - 880nm that roughly mimics the range collected by the ChemCam instrument on the Mars rover Curiosity. Each spectra had 32,000 wavelengths split across three spectrometer ranges (to mimic ChemCam). The experimental data, described in [1], measures a prepared basalt sample. All files are kept in directories whose names indicate the set of elements considered for the target with file names numbered to indicate the line in the design files used to produce the simulation. The designs are provided as text files with names indicating their purpose. The experimental data is provided as a CSV file which contains a header with measurement information, followed by a collection of 50 shots across a collection of wavelengths, along with the computed median and mean across shots.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗

ATOMIC Simulations and Experimental Data for CaCO3 Mixtures

This data consists of simulations and experimental measurements of laser-induced breakdown spectroscopy (LIBS). The simulations are produced by ATOMIC, a general purpose plasma modeling and kinetics code that has been designed to compute emission (or absorption) spectra from plasmas [1] and are used to develop a statistical characterization of matrix effects. Our overall suite of simulations includes contains several sets of simulations: training and validation sets of simulations for three and four element mixtures of calcium, carbon, oxygen, and nitrogen (included to account for atmosphere) along with simulations of the individual elements. The 4-element simulations include the mixture of all four elements mentioned and for each of the four individual elements. The 3-element simulations include output for the mixture of calcium, carbon, oxygen and for these three individual elements. The training data were produced using a 600-run design, shown in Figure 1, that varies input parameters temperature (T), electron density (Ne), and proportion of the elements calcium, carbon, oxygen, and nitrogen (Ca; C; O; N) for the 4 element output. The 3-element output includes all parameters except for the proportion of nitrogen. The element proportions (all the variables but T and Ne) sum to one and are unused in the single-element simulations. The validation data was produced with a 80-run design shown in Figure 2. The training and validation simulation outputs for the 4-element simulations for the mixture and for the single element calcium are shown as sample simulations in Figures 3 and 4 respectively. The simulations produce spectra over a range of 190nm - 950nm that roughly mimics the range collected by the SciAps Z-300 LIBS instrument that was used for the experimental data. The measured spectra for a CaCO3 (which may include contribution from Earth's atmosphere) in the experiment is shown in in Figure 5. All files are kept in directories whose names indicate the elemental composition (CaCO3, Ca, C, O, or N), number of elements (3 or 4), and purpose (training, which is not labeled in the file name, or validation) with file names numbered to indicate the line in the design files used to produce the simulation. The designs are provided as text files with names indicating their purpose. The experimental data is provided as a CSV file. [1] J Colgan, EJ Judge, DP Kilcrease, and JE Barefield II. Ab-initio modeling of an iron laser-induced plasma: Comparison between theoretical and experimental atomic emission spectra. Spectrochimica Acta Part B: Atomic Spectroscopy, 97:65{73}, 2014.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

Peptide Hit Results Processor

The Peptide Hit Results Processor (PHRP) can be used to convert an X!Tandem results file (XML format), MSGF+ .tsv search result file, Sequest Synopsis/First Hits file, or Inspect search result into a series of tab-delimited text files summarizing the results. It will insert modification symbols into the peptide sequences for modified peptides. Parallel files are created containing sequence information, modification details, and protein information. The user can optionally provide a modification definition file that specifies the symbol to use for each modification mass.

Gibbons, Bryson↗

Station Program Note Pull Automation

Upon commencement of my internship, I was in charge of maintaining the CoFR (Certificate of Flight Readiness) Tool. The tool acquires data from existing Excel workbooks on NASA's and Boeing's databases to create a new spreadsheet listing out all the potential safety concerns for upcoming flights and software transitions. Since the application was written in Visual Basic, I had to learn a new programming language and prepare to handle any malfunctions within the program. Shortly afterwards, I was given the assignment to automate the Station Program Note (SPN) Pull process. I developed an application, in Python, that generated a GUI (Graphical User Interface) that will be used by the International Space Station Safety & Mission Assurance team here at Johnson Space Center. The application will allow its users to download online files with the click of a button, import SPN's based on three different pulls, instantly manipulate and filter spreadsheets, and compare the three sources to determine which active SPN's (Station Program Notes) must be reviewed for any upcoming flights, missions, and/or software transitions. Initially, to perform the NASA SPN pull (one of three), I had created the program to allow the user to login to a secure webpage that stores data, input specific parameters, and retrieve the desired SPN's based on their inputs. However, to avoid any conflicts with sustainment, I altered it so that the user may login and download the NASA file independently. After the user has downloaded the file with the click of a button, I defined the program to check for any outdated or pre-existing files, for successful downloads, to acquire the spreadsheet, convert it from a text file to a comma separated file and finally into an Excel spreadsheet to be filtered and later scrutinized for specific SPN numbers. Once this file has been automatically manipulated to provide only the SPN numbers that are desired, they are stored in a global variable, shown on the GUI, and transferred over to a new Excel worksheet for comparison. I managed to get my application to acquire the CSWG (Computer Safety Working Group) and the SPNWG (Space Station Working Group) SPN's with just two mouse clicks for each pull, as opposed to several from the original process. When all three pulls are performed, an Excel sheet containing all three different results will be generated for the user to compare and determine which SPN's will be presented or reviewed the following month. The experience from this internship has been spectacular. As a high school senior who will begin attending college in the fall, this internship has been both educationally and occupationally beneficial. The internship has allowed me the opportunities to learn new programming languages, effectively network with NASA personnel from a variety of departments at JSC, and allowed me to learn new professional skills and etiquette. My internship at NASA's Johnson Space Center has further motivated me to pursue a Master's degree in Software Engineering and strive for a prosperous career with NASA as a civil servant.

Delgado, Ivan↗

Automated ISS Flight Utilities

During my internship at NASA Johnson Space Center, I worked in the Space Radiation Analysis Group (SRAG), where I was tasked with a number of projects focused on the automation of tasks and activities related to the operation of the International Space Station (ISS). As I worked on a number of projects, I have written short sections below to give a description for each, followed by more general remarks on the internship experience. My first project is titled "General Exposure Representation EVADOSE", also known as "GEnEVADOSE". This project involved the design and development of a C++/ ROOT framework focused on radiation exposure for extravehicular activity (EVA) planning for the ISS. The utility helps mission managers plan EVAs by displaying information on the cumulative radiation doses that crew will receive during an EVA as a function of the egress time and duration of the activity. SRAG uses a utility called EVADOSE, employing a model of the space radiation environment in low Earth orbit to predict these doses, as while outside the ISS the astronauts will have less shielding from charged particles such as electrons and protons. However, EVADOSE output is cumbersome to work with, and prior to GEnEVADOSE, querying data and producing graphs of ISS trajectories and cumulative doses versus egress time required manual work in Microsoft Excel. GEnEVADOSE automates all this work, reading in EVADOSE output file(s) along with a plaintext file input by the user providing input parameters. GEnEVADOSE will output a text file containing all the necessary dosimetry for each proposed EVA egress time, for each specified EVADOSE file. It also plots cumulative dose versus egress time and the ISS trajectory, and displays all of this information in an auto-generated presentation made in LaTeX. New features have also been added, such as best-case scenarios (egress times corresponding to the least dose), interpolated curves for trajectories, and the ability to query any time in the EVADES output. As mentioned above, GEnEVADOSE makes extensive use of ROOT version 6, the data analysis framework developed at the European Organization for Nuclear Research (CERN), and the code is written to the C++11 standard (as are the other projects). My second project is the Automated Mission Reference Exposure Utility (AMREU).Unlike GEnEVADOSE, AMREU is a combination of three frameworks written in both Python and C++, also making use of ROOT (and PyROOT). Run as a combination of daily and weekly cron jobs, these macros query the SRAG database system to determine the active ISS missions, and query minute-by-minute radiation dose information from ISS-TEPC (Tissue Equivalent Proportional Counter), one of the radiation detectors onboard the ISS. Using this information, AMREU creates a corrected data set of daily radiation doses, addressing situations where TEPC may be offline or locked up by correcting doses for days with less than 95% live time (the total amount time the instrument acquires data) by averaging the past 7 days. As not all errors may be automatically detectable, AMREU also allows for manual corrections, checking an updated plaintext file each time it runs. With the corrected data, AMREU generates cumulative dose plots for each mission, and uses a Python script to generate a flight note file (.docx format) containing these plots, as well as information sections to be filled in and modified by the space weather environment officers with information specific to the week. AMREU is set up to run without requiring any user input, and it automatically archives old flight notes and information files for missions that are no longer active. My other projects involve cleaning up a large data set from the Charged Particle Directional Spectrometer (CPDS), joining together many different data sets in order to clean up information in SRAG SQL databases, and developing other automated utilities for displaying information on active solar regions, that may be used by the space weather environment officers to monitor solar activity. I consulted my mentor Dr. Ryan Rios and Dr. Kerry Lee for project requirements and added features, and ROOT developer Edmond Offermann for advice on using the ROOT library. I also received advice and feedback from Dr. Janet Barzilla of SRAG, who tested my code. Besides these inputs, I worked independently, writing all of the code by myself. The code for all these projects is documented throughout, and I have attempted to write it in a modular format. Assuming that ROOT is updated accordingly, these codes are also Y2038-compliant (and Y10K-compliant). This allows the code to be easily referenced, modified and possibly repurposed for non-ISS missions in the future, should the necessary inputs exist. These projects have taught me a lot about coding and software design - I have become a much more skilled C++ programmer and ROOT user, and I also learned to code in Python and PyROOT (and its advantages and disadvantages compared to C++/ ROOT). Furthermore, I have learned about space radiation and radiation modeling, topics that greatly interest me as I pursue a degree in physics. Working alongside experimental physicists like Dr. Rios, I have developed a greater understanding and appreciation for experimental science, something I have always leaned towards but to which I lacked significant exposure. My work in SRAG has also given me the invaluable opportunity to witness the work environment for physicists at NASA, and what a career in academia may look like at a government laboratory such as NASA Johnson Space Center. As I continue my studies and look forward to graduate school and a future career, this experience at NASA has given me a meaningful and enjoyable opportunity to put my skills to use and see what my future career path might hold.

Offermann, Jan Tuzlic↗

Uniprot-DAT-File-Parser

This program can read a Uniprot .Dat file and parse out the information for each entry, creating a tab delimited text file or a FASTA file.

Monroe, Matthew↗

OBO-Data-Converter

The OBO Data Converter reads an Ontology file in the OBO format and converts the data to a tab-delimited text file.

Monroe, Matthew↗

Wind speed data from NCEI Marcos A Gelabert station, Panama, Jan 2008 – Dec 2019

This data package contains wind speed data retrieved from the National Oceanic and Atmospheric Administration's National Center for Environmental Information (NCEI). Measurements were collected at the Marcos A. Gilbert airport in Panama City, Panama. This station can be considered as an analogue to the NGEE Tropics Parque Natural Metropolitano site in Panama. In the attached Excel file, wind speed units have been converted from MPH to m/s (1MPH = 0.447 m/s). Data from NCEI can be accessed at: https://gis.ncdc.noaa.gov/maps/ncei/, STATION NAME: MARCOS A GELABERT (Airport in Panama City). Within the attached zip file are three .csv data files, three PDF files containing an explanation of gap filling procedures and site information, and a read.me text file with metadata and instructions for accessing data from NCEI.

54 ENVIRONMENTAL SCIENCES↗

Utah FORGE: Phase 2C Seismic Observation and Ground Water Well Data and Well Locations

This submission contains the following data associated with Utah FORGE Phase 2C within the Roosevelt Hot Springs geothermal area: - An ArcGIS shapefile with well locations for wells 58-32, 78-32, 68-32, OH-3, OH-4, WOW-2, and WOW-3. Well 58-32 is the deep test well, wells 68-32 and 78-32 are seismic test wells, and the OH and WOW wells were used for ground water monitoring and temperature gradient logging. - Drilling reports, lithologic logs, daily drilling reports, cuttings logs, and drilling photos for seismic monitoring wells 78-32 and 68-32. - Raw and post-processing temperature logs for wells OH-3, OH-4, WOW-2, and WOW-4. The archive also includes a README.txt file, which contains an explanation of the data and how it was acquired, and a text file with coordinates for the logged wells.

15 GEOTHERMAL ENERGY↗

Geophysical and Environmental Monitoring Data, and Subsurface Flow Modelling Results for Chicken Bone Meadow, Mt. Snodgrass, Crested Butte, CO

This dataset includes geoelectrical monitoring data acquired between October 2021 and November 2022, soil moisture and temperature data, groundwater data obtained from borehole SNIB covering the period from June 2021 to September 2022, and hydrological modelling results. The data were acquired to investigate how variations in bedrock type and topography, and vegetation cover control subsurface flow dynamics. To provide insights into the subsurface flow dynamics and their controls, a monitoring transect was installed at the Chicken Bone Meadow, Mt. Snodgrass, Crested Butte, CO, measuring the spatio-temporal variations of soil moisture, soil and snow temperature, subsurface electrical resistivity variations, and groundwater dynamics. Field data are organized in a folder structure, with Electrical Resistivity Tomography (ERT) data being provided as one file per measurement, and data of the soil moisture and temperature sensors being provided as text files covering the entire monitoring period. The ‘Locations.csv’ file contains the location of all sensors, given in NAD83 – UTM Zone 13N. ERT monitoring data has been processed to filter data based on reciprocal errors (data with errors > 30% were removed), a linear error model was fitted to each survey, and to ensure a constant set of measurements for time-lapse inversion, filtered data were interpolated and assigned a 100% measurement error. Soil moisture and temperature data were acquired at 15 min intervals, and averaged to provide 1h data. Weather data and borehole data (groundwater depth, conductivity and temperature) were acquired at 30 min intervals, and are provided as daily measurements; all measurements are averaged, except of precipitation values, which are given as daily accumulation. The hydrological model was set up along the ERT monitoring transect, and net infiltration was used as surface boundary condition and derived from the weather data. Four different results are provided, (1) results for a parameterization using hydraulic permeability and porosity as derived from the ERT data through petrophysical relationships, and (2) three simplified model results, using 1 to 3 geological layers above the bedrock. Modelling was performed using PFLOTRAN, and for each model the PFLOTRAN input files are provided. The result files include weekly hydrological modelling results (e.g., saturation, velocities, pressures), as well as the model parameterization. The dataset additionally includes a file-level metadata (flmd.csv) file that lists each file contained in the dataset with associated metadata; and a data dictionary (dd.csv) file that contains column/row headers used throughout the files along with a definition, units, and data type.

54 ENVIRONMENTAL SCIENCES↗