Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “input 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 847 records · Page 47

ISPATOM: A Generic Real-Time Data Processing Tool Without Programming

Information Sharing Protocol Advanced Tool of Math (ISPATOM) is an application program allowing for the streamlined generation of comps, which subscribe to streams of incoming telemetry data, perform any necessary computations on the data, then send the data to other programs for display and/or further processing in NASA mission control centers. Heretofore, the development of comps was difficult, expensive, and time-consuming: Each comp was custom written manually, in a low-level computing language, by a programmer attempting to follow requirements of flight controllers. ISPATOM enables a flight controller who is not a programmer to write a comp by simply typing in one or more equation( s) at a command line or retrieving the equation(s) from a text file. ISPATOM then subscribes to the necessary input data, performs all of necessary computations, and sends out the results. It sends out new results whenever the input data change. The use of equations in ISPATOM is no more difficult than is entering equations in a spreadsheet. The time involved in developing a comp is thus limited to the time taken to decide on the necessary equations. Thus, ISPATOM is a real-time dynamic calculator.

Dershowitz, Adam↗

The Profile Envision and Splice Tool (PRESTO): Developing an Atmospheric Wind Analysis Tool for Space Launch Vehicles Using Python

Tropospheric winds are an important driver of the design and operation of space launch vehicles. Multiple types of weather balloons and Doppler Radar Wind Profiler (DRWP) systems exist at NASA's Kennedy Space Center (KSC), co-located on the United States Air Force's (USAF) Eastern Range (ER) at the Cape Canaveral Air Force Station (CCAFS), that are capable of measuring atmospheric winds. Meteorological data gathered by these instruments are being used in the design of NASA's Space Launch System (SLS) and other space launch vehicles, and will be used during the day-of-launch (DOL) of SLS to aid in loads and trajectory analyses. For the purpose of SLS day-of-launch needs, the balloons have the altitude coverage needed, but take over an hour to reach the maximum altitude and can drift far from the vehicle's path. The DRWPs have the spatial and temporal resolutions needed, but do not provide complete altitude coverage. Therefore, the Natural Environments Branch (EV44) at Marshall Space Flight Center (MSFC) developed the Profile Envision and Splice Tool (PRESTO) to combine balloon profiles and profiles from multiple DRWPs, filter the spliced profile to a common wavelength, and allow the operator to generate output files as well as to visualize the inputs and the spliced profile for SLS DOL operations. PRESTO was developed in Python taking advantage of NumPy and SciPy for the splicing procedure, matplotlib for the visualization, and Tkinter for the execution of the graphical user interface (GUI). This paper describes in detail the Python coding implementation for the splicing, filtering, and visualization methodology used in PRESTO.

Orcutt, John M.↗

burtscher/LICO

LICO is a fast lossless image compressor. It takes BMP files (in 24-bit BMP3 format) as input.

Burtscher, Martin [Texas State Univ., San Marcos, ↗

Predicting Rocket or Jet Noise in Real Time

A semi-empirical theoretical model and a C++ computer program that implements the model have been developed for use in predicting the noise generated by a rocket or jet engine. The computer program, entitled the Realtime Rocket and Jet Engine Noise Analysis and Prediction Software, is one of two main subsystems of the Acoustic Prediction/Measurement Tool, which comprises software, acoustic instrumentation, and electronic hardware combined to afford integrated capabilities for real-time prediction and measurement of noise emitted by rocket and jet engines. [The other main subsystem, consisting largely of acoustic instrumentation and electronic hardware, is described in Wireless Acoustic Measurement System, which appears elsewhere in this section.] The theoretical model was derived from the fundamental laws of fluid mechanics, as first was done by M. J. Lighthill in his now famous theory of aerodynamically generated sound. The far-field approximation of the Lighthill theory is incorporated into this model. Many other contributions from various researchers have also been introduced into the model. The model accounts for two noise components: shear noise and self noise. The final result of the model is expressed in terms of a volume integral of the acoustic intensities attributable to these two components, subject to various directivity coefficients. The computer program was written to solve the volume integral. The inputs required by the program are two data files from a computational fluid dynamics (CFD) simulation of the flow of interest: the computational-grid file and the solution file. The CFD solution should be one that has been obtained for conditions that closely approximate those of an experimental test that is yet to be performed. In the current state of development of the model and software, it is recommended that the observation points lie along a radius at an angle >60 from the jet axis. The software provides, and is driven via, a graphical user interface, which facilitates its use. Optionally, the program accepts additional input in the form of data on the measured sound pressure level as a function of frequency at a given far-field location, preferably at an angle of 90 from the jet axis. The user is prompted to use default empirical constants or to choose constants based the measurement data. The user can view the results and compare them with other computational or experimental data. Once satisfied with the results, the user can save a graph of the results in a file that can be imported into documents.

Frendi, Kader↗

Mars Global Reference Atmospheric Model 2000 Version (Mars-GRAM 2000): Users Guide

This report presents Mars Global Reference Atmospheric Model 2000 Version (Mars-GRAM 2000) and its new features. All parameterizations for temperature, pressure, density, and winds versus height, latitude, longitude, time of day, and L(sub s) have been replaced by input data tables from NASA Ames Mars General Circulation Model (MGCM) for the surface through 80-km altitude and the University of Arizona Mars Thermospheric General Circulation Model (MTGCM) for 80 to 170 km. A modified Stewart thermospheric model is still used for higher altitudes and for dependence on solar activity. "Climate factors" to tune for agreement with GCM data are no longer needed. Adjustment of exospheric temperature is still an option. Consistent with observations from Mars Global Surveyor, a new longitude-dependent wave model is included with user input to specify waves having 1 to 3 wavelengths around the planet. A simplified perturbation model has been substituted for the earlier one. An input switch allows users to select either East or West longitude positive. This memorandum includes instructions on obtaining Mars-GRAM source code and data files and for running the program. It also provides sample input and output and an example for incorporating Mars-GRAM as an atmospheric subroutine in a trajectory code.

Justus, C. G.↗

Converting from DDOR SASF to APF

A computer program called ddor_sasf2apf converts delta-door (delta differential one-way range) request from an SASF (spacecraft activity sequence file) format to an APF (apgen plan file) format for use in the Mars Reconnaissance Orbiter (MRO) missionplanning- and-sequencing process. The APF is used as an input to APGEN/AUTOGEN in the MRO activity- planning and command-sequencegenerating process to sequence the delta-door (DDOR) activity. The DDOR activity is a spacecraft tracking technique for determining spacecraft location. The input to ddor_sasf2apf is an input request SASF provided by an observation team that utilizes DDOR. ddor_sasf2apf parses this DDOR SASF input, rearranging parameters and reformatting the request to produce an APF file for use in AUTOGEN and/or APGEN. The benefit afforded by ddor_sasf2apf is to enable the use of the DDOR SASF file earlier in the planning stage of the command-sequence-generating process and to produce sequences, optimized for DDOR operations, that are more accurate and more robust than would otherwise be possible.

Gladden, Roy E.↗

AutoBEM-DynamicArchetypes

Automatic Building Energy Modeling (AutoBEM, https://bit.ly/AutoBEM) has been used to create an OpenStudio and EnergyPlus building energy model of 122.9 million U.S. buildings (https://bit.ly/ModelAmerica). Simulating and analyzing a model of every building for large areas (e.g. cities) is often not feasible. This dynamic archetyping capability uses a representative building and calculates a floor-space multiplier that allows millions of buildings to be represented by less than 100 buildings. This script (WRF_Archetypes_Parallel.py) calculates these building archetypes for each of the grid cells from a Weather Research and Forecasting (WRF) model in a parallel fashion. The script works by looping through each of the grid cells in the shapefile in parallel, spatially joining the building metadata table to each grid cell, aggregating relevant archetypes and calculating necessary statistics related to area and number of buildings in each cell. The output is a table (.csv) in which each row is an archetype building with properties about that building as well as statistics that relate that building to the total cell (such as an area multiplier). The following inputs are required: WRF zone shapefile (.shp) (wrf-grids-origin_Vegas_Select_100.geojson) The projection of the shapefile ("EPSG:XXXX") Input table containing building metadata for area corresponding to shapefile (.csv) (https://zenodo.org/record/4552901#.YZQEotDMJPY - ClarkCounty2.csv) The number of cores that will be parallelized (integer) The output file name for the archetype table (.csv) Sample command line inputs: python3 ~/WRF_Archetypes_Parallel.py -i ~/wrf-grids-origin_Vegas_Select_100.geojson -c ~/ClarkCounty2.csv -o ~/OutputArchetypes.csv -j 72 -e EPSG:4326 Using Geopandas Version 0.9.0

Bass, Brett (0000000240988434)↗

MPST Software: MoonKommand

This software automatically processes Sally Ride Science (SRS) delivered MoonKAM camera control files (ccf) into uplink products for the GRAIL-A and GRAIL-B spacecraft as part of an education and public outreach (EPO) extension to the Grail Mission. Once properly validated and deemed safe for execution onboard the spacecraft, MoonKommand generates the command products via the Automated Sequence Processor (ASP) and generates uplink (.scmf) files for radiation to the Grail-A and/or Grail-B spacecraft. Any errors detected along the way are reported back to SRS via email. With Moon Kommand, SRS can control their EPO instrument as part of a fully automated process. Inputs are received from SRS as either image capture files (.ccficd) for new image requests, or downlink/delete files (.ccfdl) for requesting image downlink from the instrument and on-board memory management. The Moon - Kommand outputs are command and file-load (.scmf) files that will be uplinked by the Deep Space Network (DSN). Without MoonKommand software, uplink product generation for the MoonKAM instrument would be a manual process. The software is specific to the Moon - KAM instrument on the GRAIL mission. At the time of this writing, the GRAIL mission was making final preparations to begin the science phase, which was scheduled to continue until June 2012.

Kwok, John H.↗

Development of a ROT22 - DATAMAP interface

This report (Contract NAS2-10331- Mod 10), outlines the development and validation of an interface between the three-dimensional transonic analysis program ROT22 and the Data from Aeromechanics Test and Analytics-Management and Analysis Package (DATAMAP). After development of the interface, the validation is carried out as follows. First, the DATAMAP program is used to analyze a portion of the Tip Aerodynamics and Acoustics Test (TAAT) data. Specifically, records 2872 and 2873 are analyzed at an azimuth of 90 deg, and record 2806 is analyzed at 60 deg. Trim conditions for these flight conditions are then calculated using the Bell performance prediction program ARAM45. Equivalent shaft, pitch, and twist angles are calculated from ARAM45 results and used as input to the ROT22 program. The interface uses the ROT22 results and creates DATAMAP information files from which the surface pressure contours and sectional pressure coefficients are plotted. Twist angles input to ROT22 program are then iteratively modified in the tip region until the computed pressure coefficients closely match the measurements. In all cases studied, the location of the shock is well predicted. However, the negative pressure coefficients were underpredicted. This could be accounted for by blade vortex interaction effects.

Shenoy, K. R.↗

Interactive LORAN-C to geographic and geographic-to-LORAN-C computation

The LORAN program is stored in CMS disk files for use by Avionics Engineering Center terminal users. A CMS EXEC file named LORAN controls program operation. The user types LORAN and the program then prompts for data input and produces output on the terminal. The FORTRAN program refers to a disk file of LORAN master data giving station locations, coding delays, repetition rate and station pair identification letters. For Geographic-to-LORAN conversion, no iterative computations are required; the program is a straightforward coordinate conversion based upon the techniques described by the Navy. For LORAN-to-Geographic conversion, the original Navy program required a dead-reckoned position, near the actual unknown fix, to begin computations. No iteration was performed to obtain the LORAN fix, but internal program errors occurred at execution time if the dead-reckoned fix were displaced from the actual fix by more than a few minutes of latitude or longitude. In order to enhance usefulness of the program for the terminal user, an iterative routine was added which allows a single dead-reckoned position to be entered from the master data file for each LORAN chain. The results compare exactly with the LORAN-C navigation chart, and provide adequate benchmark data for general aviation flight planning and data analysis.

Piecuch, L. M.↗

Public Reference Data for Megawatt-Scale Hydrogen Electrolysis - NLR Historical Solar PV

The U.S. Department of Energy and National Laboratory of the Rockies (NLR) demonstrate hydrogen electrolysis from variable sources, hydrogen compression and storage, and hydrogen fuel cell power production using megawatt-scale equipment at NLR’s Flatirons Campus as part of the Advanced Research on Integrated Energy Systems (ARIES) research platform. This dataset represents part of that effort and is intended for academic, national laboratory, industrial, and other stakeholders to plan, design, and validate models of megawatt-scale hydrogen technologies and diverse energy infrastructure nationwide. These data provide a baseline for how existing hydrogen electrolysis technologies perform when coupled with various energy technologies. Future datasets will demonstrate how existing hydrogen fuel cell technologies can provide controllable, dispatchable, and variable power output for artificial intelligence data centers and other variable loads. This dataset entry describes the behavior of a 1.25-MW proton exchange membrane MC250 electrolyzer system, manufactured by Nel Hydrogen , [1] when fed historical data generated by the 430-kW, fixed-axis solar photovoltaic (PV) array located at NLR’s Flatirons Campus. (While the electrolyzer balance of plant supports up to 2.5 MW of electrolysis, NLR only has a single 1.25-MW electrolysis stack.) Solar PV power output data for the 2020 calendar year were categorized on a daily basis by total energy generation and standard deviation. Each day was then ranked by these metrics, and the 25th, 50th, and 100th percentiles were selected. The 75th percentile day did not exhibit sufficient variability to make for a valuable experiment. A similar process was used for the related historical wind dataset . [2] The historical days in 2020 that represented these percentiles are Dec. 19, March 29, and May 4, respectively. The entire solar day’s power profile was then fed through the MC250 electrolyzer. Due to its length, the 100th percentile day experiment was split into two parts, and the final 3 hours of the solar day were not captured. These final 3 hours contained no spikes or dips of interest and simply represented a slow decay of input solar power. Also, a single timestamp (13:13:47 on Jan. 14, 2026) was lost in the hydrogen system supervisory control and data acquisition. Finally, during the 25th percentile experiment (solar day Dec. 19, 2020) data recording was lost from 11:00:13 to 11:14:45. The roughly 15 minutes of the solar profile were rerun at the end of the experiment and spliced into this time slot during post-processing. The electrolysis system controls hydrogen production by varying direct current applied to the stack, from a maximum of 3,000 A to a minimum safe operation of 300 A, or 10%. Because the current–voltage characteristic changes as the stack ages and efficiency degrades, the actual minimum safe operating power changes over time. The historical solar profiles were translated from power (kilowatts) to current (amperes) using a curve fit with calibration data and sent to the electrolyzer power supply at 1-Hz frequency. For more details on the statistical analysis process, see the slide deck “Public Reference Data for Megawatt-Scale Hydrogen Electrolysis: NLR Historical Solar PV Analysis and Profile Generation” accessible with this data entry. These datasets report relevant hydrogen balance-of-plant and system data, all captured at 1 Hz, including hydrogen mass production measured with an Emerson Coriolis flow meter. Each .zip file represents a single solar PV electrolysis experiment and is formatted as: {technology}_{percentile}_{scaling factor} For instance, “solarPV-430kW_25_2x.zip” reports the experiment using the 25th percentile solar data from the historical 2020 solar PV dataset, scaled to 200%. Scaling factors were applied to the generated solar PV power output files to more closely match the 1.25-MW capacity of the electrolyzer. Each .zip folder contains the following files: A .csv file containing raw data. An .xlsx file explaining all the fields in the raw data. A .png plot showing the time series of hydrogen production, electrolysis power consumption, and solar power input. A PDF file detailing the historical solar data statistical analysis used to generate the solar profile. An experiment labeled “characterization_200.zip” demonstrates the MC250 electrolyzer steady-state response with 30-minute load steps for a total duration of 5 hours. Finally, a .csv file is provided with all experiments combined into one dataset labeled "combined_solarPV_experiments.csv". [1] nelhydrogen.com/product/mc-series-electrolyser . [2] data.nlr.gov/submissions/316 .

08 HYDROGEN↗

Flight dynamics analysis and simulation of heavy lift airships, volume 4. User's guide: Appendices

This table contains all of the input variables to the three programs. The variables are arranged according to the name list groups in which they appear in the data files. The program name, subroutine name, definition and, where appropriate, a default input value and any restrictions are listed with each variable. The default input values are user supplied, not generated by the computer. These values remove a specific effect from the calculations, as explained in the table. The phrase "not used' indicates that a variable is not used in the calculations and are for identification purposes only. The engineering symbol, where it exists, is listed to assist the user in correlating these inputs with the discussion in the Technical Manual.

Emmen, R. D.↗

serial-log-replayer

The code records or logs serial input along with a timestamp to a binary file. The code can then read this log file and replay the serial data with the same relative timings.

Sikkema, Isaac [Oak Ridge National Laboratory (ORN↗

Heavy-Duty Vehicle Activity Updates for MOVES Using NREL Fleet DNA and CE-CERT Data

The U.S. Environmental Protection Agency's (EPA's) Motor Vehicle Emission Simulator (MOVES) is a publicly available tool used by researchers and policymakers to help understand motor vehicle emission sources at a national, county, and project level. Estimates of heavy-duty activity in the most recent version of the model at the time this work was conducted, MOVES2014, was identified as an area in need of improvement. The start activity in MOVES2014 is based on a limited and dated data set. In addition, MOVES2014 relies on drive cycles that represent on-network activity but do not account for idling activity that occurs on off-network roads, such as at a distribution center, while the truck is queuing or during loading and unloading. As a result, MOVES2014 may currently underestimate the number of starts and idle and soak time for heavy-duty trucks in real-world operation. The National Renewable Energy Laboratory (NREL) has previously leveraged its expansive Fleet DNA database of heavy-duty vehicles to idle and start activity for six of the nine heavy-duty vehicle source types of classes in the MOVES model. The data available in Fleet DNA from 416 conventional, diesel-powered vehicles provided activity estimates from more than 120,000 hours of operation throughout 14,682 vehicle days between October 2006 and January 2016. NREL calculated start fraction, starts per day, soak fraction, and idle fraction by hour of the day for each vehicle type, state, and vocation, and provided results in .CSV files that can be translated to MOVES table inputs. The idle and start activity from this initial analysis of Fleet DNA data was used to develop default idle and start data for heavy-duty vehicles in MOVES3. Satisfied with the results from the Fleet DNA data used for MOVES3, the EPA asked NREL to extend this start/soak/idle analysis using additional data from a larger number of vehicles for a potential future update to the MOVES model. Such a data set was achieved from a project led by the University of California at Riverside, College of Engineering, Center for Environmental Research & Technology (CE-CERT) and funded by California Air Resources Board. Specifically, this data set consists of 90 heavy-duty vehicles operated mainly in California, which can be separated into five of the nine heavy-duty vehicle classes in the MOVES model. In addition, the heavy-duty activity database collected by CE-CERT provided activity estimates from more than 44,000 hours of operation throughout 4,724 vehicle days between November 2014 and September 2016. This report details the analysis of the heavy-duty activity database collected from the University of California at Riverside by providing graphical analysis and context for the start, soak, and idle distributions. The comparison of the related results from both the Fleet DNA and CE-CERT data sets are documented as well.

33 ADVANCED PROPULSION SYSTEMS↗

PKI solar thermal plant evaluation at Capitol Concrete Products, Topeka, Kansas

A system feasibility test to determine the technical and operational feasibility of using a solar collector to provide industrial process heat is discussed. The test is of a solar collector system in an industrial test bed plant at Capitol Concrete Products in Topeka, Kansas, with an experiment control at Sandia National Laboratories, Albuquerque. Plant evaluation will occur during a year-long period of industrial utilization. It will include performance testing, operability testing, and system failure analysis. Performance data will be recorded by a data acquisition system. User, community, and environmental inputs will be recorded in logs, journals, and files. Plant installation, start-up, and evaluation, are anticipated for late November, 1981.

Hauger, J. S.↗

A distributed Petri Net controller for a dual arm testbed

This thesis describes the design and functionality of a Distributed Petri Net Controller (DPNC). The controller runs under X Windows to provide a graphical interface. The DPNC allows users to distribute a Petri Net across several host computers linked together via a TCP/IP interface. A sub-net executes on each host, interacting with the other sub-nets by passing a token vector from host to host. One host has a command window which monitors and controls the distributed controller. The input to the DPNC is a net definition file generated by Great SPN. Thus, a net may be designed, analyzed and verified using this package before implementation. The net is distributed to the hosts by tagging transitions that are host-critical with the appropriate host number. The controller will then distribute the remaining places and transitions to the hosts by generating the local nets, the local marking vectors and the global marking vector. Each transition can have one or more preconditions which must be fulfilled before the transition can fire, as well as one or more post-processes to be executed after the transition fires. These implement the actual input/output to the environment (machines, signals, etc.). The DPNC may also be used to simulate a Great SPN net since stochastic and deterministic firing rates are implemented in the controller for timed transitions.

Bjanes, Atle↗

Manual for automatic generation of finite element models of spiral bevel gears in mesh

The goal of this research is to develop computer programs that generate finite element models suitable for doing 3D contact analysis of faced milled spiral bevel gears in mesh. A pinion tooth and a gear tooth are created and put in mesh. There are two programs: Points.f and Pat.f to perform the analysis. Points.f is based on the equation of meshing for spiral bevel gears. It uses machine tool settings to solve for an N x M mesh of points on the four surfaces, pinion concave and convex, and gear concave and convex. Points.f creates the file POINTS.OUT, an ASCI file containing N x M points for each surface. (N is the number of node points along the length of the tooth, and M is nodes along the height.) Pat.f reads POINTS.OUT and creates the file tl.out. Tl.out is a series of PATRAN input commands. In addition to the mesh density on the tooth face, additional user specified variables are the number of finite elements through the thickness, and the number of finite elements along the tooth full fillet. A full fillet is assumed to exist for both the pinion and gear.

Bibel, G. D.↗

Automation of PCXMC and ImPACT for NASA Astronaut Medical Imaging Dose and Risk Tracking

To automate astronaut organ and effective dose calculations from occupational X-ray and computed tomography (CT) examinations incorporating PCXMC and ImPACT tools and to estimate the associated lifetime cancer risk per the National Council on Radiation Protection & Measurements (NCRP) using MATLAB(R). Methods: NASA follows guidance from the NCRP on its operational radiation safety program for astronauts. NCRP Report 142 recommends that astronauts be informed of the cancer risks from reported exposures to ionizing radiation from medical imaging. MATLAB(R) code was written to retrieve exam parameters for medical imaging procedures from a NASA database, calculate associated dose and risk, and return results to the database, using the Microsoft .NET Framework. This code interfaces with the PCXMC executable and emulates the ImPACT Excel spreadsheet to calculate organ doses from X-rays and CTs, respectively, eliminating the need to utilize the PCXMC graphical user interface (except for a few special cases) and the ImPACT spreadsheet. Results: Using MATLAB(R) code to interface with PCXMC and replicate ImPACT dose calculation allowed for rapid evaluation of multiple medical imaging exams. The user inputs the exam parameter data into the database and runs the code. Based on the imaging modality and input parameters, the organ doses are calculated. Output files are created for record, and organ doses, effective dose, and cancer risks associated with each exam are written to the database. Annual and post-flight exposure reports, which are used by the flight surgeon to brief the astronaut, are generated from the database. Conclusions: Automating PCXMC and ImPACT for evaluation of NASA astronaut medical imaging radiation procedures allowed for a traceable and rapid method for tracking projected cancer risks associated with over 12,000 exposures. This code will be used to evaluate future medical radiation exposures, and can easily be modified to accommodate changes to the risk calculation procedure.

Bahadori, Amir↗