Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Visual Programming”

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 919 records · Page 51
All sourcesNASA NTRSDOE OSTI
NASA NTRS2000

An Assessment of Gigabit Ethernet Technology and Its Applications at the NASA Glenn Research Center

This paper describes Gigabit Ethernet and its role in supporting R&D programs at NASA Glenn. These programs require an advanced high-speed network capable of transporting multimedia traffic, including real-time visualization, high- resolution graphics, and scientific data. GigE is a 1 Gbps extension to 10 and 100 Mbps Ethernet. The IEEE 802.3z and 802.3ab standards define the MAC layer and 1000BASE-X and 1000BASE-T physical layer specifications for GigE. GigE switches and buffered distributors support IEEE 802.3x flow control. The paper also compares GigE with ATM in terms of quality of service, data rate, throughput, scalability, interoperability, network management, and cost of ownership.

Bakes, Catherine Murphy↗
NASA NTRS2003

Laser-Based Relative Navigation and Guidance for Space Shuttle Proximity Operations

American manned spacecraft have used visual piloting techniques in the terminal phase of randezvous during the Gemini, Apollo, Skylab, and Space Shuttle programs. In the last several years, space- shuttle astronauts have used the Rendezvous and Proximity Operations Program (RPOP), running; on a laptop computer, as a guidance and navigation aid during proximity operations. By processing measurements to the target satellite taken by a laser sensor, RPOP provides the shuttle crew with a more accurate relative position and velocity than from any other source. The inclusion of guidance algorithms allows RPOP to determine delta-velocities to fly very efficient, repeatable trajectories. This paper will focus on the guidance and navigation algorithms in RPOP, as well as results from simulation and flight. Although developed for shuttle proximity operations, the RPOP algorithms have potential applicability to an automated vehicle.

Laser sensors↗
NASA NTRS1988

Frequency distribution histograms for the rapid analysis of data

The mean and standard error are good representations for the response of a population to an experimental parameter and are frequently used for this purpose. Frequency distribution histograms show, in addition, responses of individuals in the population. Both the statistics and a visual display of the distribution of the responses can be obtained easily using a microcomputer and available programs. The type of distribution shown by the histogram may suggest different mechanisms to be tested.

NASA Discipline Plant Biology↗
NASA NTRS2004

Force, Surface Pressure, and Flowfield Measurements on a Slender Missile Configuration with Square Cross-Section at Supersonic Speeds

A wind-tunnel investigation of a square cross-section missile configuration has been conducted to obtain force and moment measurements, surface pressure measurements, and vapor screen flow visualization photographs for comparison with computational fluid dynamics studies conducted under the auspices of The Technical Cooperation Program (TTCP). Tests were conducted on three configurations which included: (1) body alone, (2) body plus tail fins mounted on the missile corners, and (3) body plus tail fins mounted on the missile side. This test was conducted in test section #2 of the NASA Langley Unitary Plan Wind Tunnel at Mach numbers of 2.50 and 4.50 and at a Reynolds number of 4 million per ft. The data were obtained over an angle of attack range from -4 deg. to 24 deg. and roll angles from 0 deg. to 45 deg., i.e., from a diamond shape (as viewed from the rear) at a roll angle of 0 deg. to a square shape at 45 deg.

Wilcox, Floyd J., Jr.↗
NASA NTRS2009

Hazard Detection Methods for Lunar Landing

The methods and experiences from the Apollo Program are fundamental building blocks for the development of lunar landing strategies for the Constellation Program. Each of the six lunar landing Apollo missions landed under near ideal lighting conditions. The astronauts visually performed terrain relative navigation while looking out of windows, and were greatly aided by external communication and well lit scenes. As the LM approached the landing site, the astronauts performed visual hazard detection and avoidance, also under near-ideal lighting conditions. The astronauts were looking out of the windows trying to the best of their ability to avoid rocks, slopes, and craters and find a safe landing location. NASA has expressed a desire for global lunar access for both crewed and robotic sortie lunar exploration missions (Cook, 2007) (Dale, 2006). Early NASA architecture studies have identified the lunar poles as desirable locations for early lunar missions. These polar missions have less than ideal lighting conditions and will significantly affect the way a crewed vehicle plans to land at such locales. Consequently, a variety of hazard identification methods should be considered for use by the crew to ensure a high degree of safety. This paper discusses such identification methods applicable to the poorly lit polar lunar environment, better ensuring global access for the soon to be designed Lunar Lander Vehicle (LLV).

Brady, Tye↗
NASA NTRS2005

NASA Tech Briefs, September 2005

Topivs include: Diamond-Coated Carbon Nanotubes for Efficient Field Emission; Improved Anode Coatings for Direct Methanol Fuel Cells; Advanced Ablative Insulators and Methods of Making Them; PETIs as High-Temperature Resin-Transfer-Molding Materials; Stable Polyimides for Terrestrial and Space Uses; Low-Density, Aerogel-Filled Thermal-Insulation Tiles; High-Performance Polymers Having Low Melt Viscosities; Nonflammable, Hydrophobic Aerogel Composites for Insulation; Front-Side Microstrip Line Feeding a Raised Antenna Patch; Medium-Frequency Pseudonoise Georadar; Facilitating Navigation Through Large Archives; Program for Weibull Analysis of Fatigue Data; Comprehensive Micromechanics-Analysis Code - Version 4.0; Component-Based Visualization System; Software for Engineering Simulations of a Spacecraft; LabVIEW Interface for PCI-SpaceWire Interface Card; Path Following with Slip Compensation for a Mars Rover; International Space Station Electric Power System Performance Code-SPACE; Software for Automation of Real-Time Agents, Version 2; Software for Optimizing Plans Involving Interdependent Goals; Computing Gravitational Fields of Finite-Sized Bodies; Custom Sky-Image Mosaics from NASA's Information Power Grid; ANTLR Tree Grammar Generator and Extensions; Generic Kalman Filter Software; Alignment Stage for a Cryogenic Dilatometer; Rugged Iris Mechanism; Treatments To Produce Stabilized Aluminum Mirrors for Cryogenic Uses; Making AlNx Tunnel Barriers Using a Low-Energy Nitrogen-Ion Beam; Making Wide-IF SIS Mixers with Suspended Metal-Beam Leads; Sol-Gel Glass Holographic Light-Shaping Diffusers; Automated Counting of Particles To Quantify Cleanliness; Phase Correction for GPS Antenna with Nonunique Phase Center; Compact Infrasonic Windscreen; Broadband External-Cavity Diode Laser; High-Efficiency Solar Cells Using Photonic-Bandgap Materials; Generating Solid Models from Topographical Data; Computationally Lightweight Air-Traffic-Control Simulation; Spool Valve for Switching Air Flows Between Two Beds; Partial Model of Insulator/ Insulator Contact Charging; Asymmetric Electrostatic Radiation Shielding for Spacecraft; and Reusable Hybrid Propellant Modules for Outer-Space Transport.

Source record↗
NASA NTRS2020

Systems Development, Data Mining, and Knowledge Discovery

I worked as a NASA OSTEM virtually during the Fall 2020 term. Working in the IT division under my mentor Dr. Ali Shaykhian, our overall goal for the duration of this internship is to get a better understanding of the Visual Basic Language and how it can be used to make forms and collaboration with other workers to be more dynamics. I also worked with 3 other interns throughout this internship, using Microsoft Office to help each other to get a better understanding of how we approached our projects individually. Every week, my mentor Dr. Ali assigned me a task and a goal to finish by the end of each week. My overall project was figuring out a way to make email submissions and emails in general more dynamic for the NASA database. For example, instead of only using the same generic email for hundreds of different workers, a code can be used to send an individual email with more personalization such as each recipient’s name and personal info. I have also been assigned to create an email graphical user interface by the end of this internship. For these tasks to be made possible, I had to learn more about the capabilities of Microsoft Office, such as Macros in Microsoft Excel and Visual Basic in both Microsoft Excel and Word. Although it was challenging at first, I developed new programming skilled in a new language and actually made it possible to create this code along the way. Alongside doing the individual assignments, Dr. Ali also assigned up to replicate other intern’s work to get a better understanding of their approach and learn how to do it ourselves.

Janelisse Morales Gonzalez↗
NASA NTRS2006

Validation of Multi-Dimensional Stirling Engine Design Codes: Measurements in the 90-Degree Turn Test Section

The work to be presented herein was motivated largely by a desire to improve the understanding of oscillatory fluid mechanics inside a Stirling engine. To this end, a CFD project was undertaken at Cleveland State University with the goal of accurately predicting the fluid dynamics within an engine or engine component. Along with the CFD efforts, a code validation project was undertaken at the University of Minnesota. The material covered herein consists of four main parts. In section 1, an experimental investigation of a small aspect ratio impinging jet is discussed. Included in this discussion is a description of the test facilities and instrumentation. A presentation of the collected data is given and comments are made. Next, in section 2, a parallel experimental investigation is presented in which the same geometry as that of section 1 is used, but the flow conditions are changed from steady unidirectional flow to sinusoidally oscillating flow. In section Two, collected data are presented and comments are made. In section 3, a comparison is made between the results of sections 1 and 2, namely, sinusoidally oscillating flow results are compared to steady, unidirectional flow results from the same geometry. Finally, in section 4, a comparison is made between experimentally collected data (the main subject of this work) and CFD generated results. Furthermore, in appendix A, an introductory description of the primary measurement tool used in the experimental process the hot wire anemometer is given for the unfamiliar. The anemometer calibration procedure is described in appendix B. A portfolio of data reduction and data processing codes is provided in appendix C and lastly, a DVD and a roadmap of its contents is provided in an appendix D. 1.0 Unidirectional Flow Investigations 1.1 Introduction This unidirectional experimental program was undertaken to complement an oscillatory flow investigation conducted at the University of Minnesota. The oscillatory investigation is discussed thoroughly in section 2. We defer the description of the motivation behind these experiments until the introduction of section 2. The work that is discussed in this thesis began (chronologically) with oscillatory flow visualization experiments. It was decided that it would be valuable and important to investigate the flow under unidirectional conditions in the same geometry as that of the oscillatory experiments. The thought was that the unidirectional case would be less complicated to model with a CFD program (a moving boundary would be replaced with a steady state boundary condition). Thus, a series of unidirectional experiments were carried out to capture the important features of the flow within the test section. The purpose of these experiments was to provide a data set for comparison to CFD generated velocity fields. Hot-wire anemometry data were taken and flow visualization was conducted as a standard for code validation. The flow geometry was simple, such that it could be easily gridded in a CFD program. However, the geometry provided separation and transition zones, shear layers and recirculation zones. These characteristics made the flow complex and challenging for CFD computation. We comment that the order of experiments that produced this report is as follows: experimental flow visualization under oscillatory flow conditions was carried out; this was followed by unidirectional flow visualization and hot wire anemometry; finally, oscillatory hot wire anemometry was conducted. We present the results out of chronological order for the following reason: the unidirectional results are easier

Simon, Terrence W.↗
NASA NTRS1995

Educational software for the visualization of space plasma processes

The UCLA Space Physics Group has developed educational software composed of a series of modules to assist students with understanding basic concepts of space plasmas and charged particle motion. Present modules cover planetary magnetospheres, charged particle motion, cold plasma waves, collisionless shock waves, and solar wind. The software is designed around the principle that students can learn more by doing rather than by reading or listening. The programs provide a laboratory-like environment in which the student can control, observe, and measure complex behavior. The interactive graphics environment allows the student to visualize the results of his or her experimentation and to try different parameters as desired. The current version of the software runs on UNIX-based operating systems in an X-Windows environment. It has been used in a classroom setting at both UCLA and the University of California at San Diego.

Russell, C. T.↗
NASA NTRS1998

A Geometry Based Infra-Structure for Computational Analysis and Design

The computational steps traditionally taken for most engineering analysis suites (computational fluid dynamics (CFD), structural analysis, heat transfer and etc.) are: (1) Surface Generation -- usually by employing a Computer Assisted Design (CAD) system; (2) Grid Generation -- preparing the volume for the simulation; (3) Flow Solver -- producing the results at the specified operational point; (4) Post-processing Visualization -- interactively attempting to understand the results. For structural analysis, integrated systems can be obtained from a number of commercial vendors. These vendors couple directly to a number of CAD systems and are executed from within the CAD Graphical User Interface (GUI). It should be noted that the structural analysis problem is more tractable than CFD; there are fewer mesh topologies used and the grids are not as fine (this problem space does not have the length scaling issues of fluids). For CFD, these steps have worked well in the past for simple steady-state simulations at the expense of much user interaction. The data was transmitted between phases via files. In most cases, the output from a CAD system could go to Initial Graphics Exchange Specification (IGES) or Standard Exchange Program (STEP) files. The output from Grid Generators and Solvers do not really have standards though there are a couple of file formats that can be used for a subset of the gridding (i.e. PLOT3D data formats). The user would have to patch up the data or translate from one format to another to move to the next step. Sometimes this could take days. Specifically the problems with this procedure are:(1) File based -- Information flows from one step to the next via data files with formats specified for that procedure. File standards, when they exist, are wholly inadequate. For example, geometry from CAD systems (transmitted via IGES files) is defined as disjoint surfaces and curves (as well as masses of other information of no interest for the Grid Generator). This is particularly onerous for modern CAD systems based on solid modeling. The part was a proper solid and in the translation to IGES has lost this important characteristic. STEP is another standard for CAD data that exists and supports the concept of a solid. The problem with STEP is that a solid modeling geometry kernel is required to query and manipulate the data within this type of file. (2) 'Good' Geometry. A bottleneck in getting results from a solver is the construction of proper geometry to be fed to the grid generator. With 'good' geometry a grid can be constructed in tens of minutes (even with a complex configuration) using unstructured techniques. Adroit multi-block methods are not far behind. This means that a million node steady-state solution can be computed on the order of hours (using current high performance computers) starting from this 'good' geometry. Unfortunately, the geometry usually transmitted from the CAD system is not 'good' in the grid generator sense. The grid generator needs smooth closed solid geometry. It can take a week (or more) of interaction with the CAD output (sometimes by hand) before the process can begin. One way Communication. (3) One-way Communication -- All information travels on from one phase to the next. This makes procedures like node adaptation difficult when attempting to add or move nodes that sit on bounding surfaces (when the actual surface data has been lost after the grid generation phase). Until this process can be automated, more complex problems such as multi-disciplinary analysis or using the above procedure for design becomes prohibitive. There is also no way to easily deal with this system in a modular manner. One can only replace the grid generator, for example, if the software reads and writes the same files. Instead of the serial approach to analysis as described above, CAPRI takes a geometry centric approach. This makes the actual geometry (not a discretized version) accessible to all phases of the analysis. The connection to the geometry is made through an Application Programming Interface (API) and NOT a file system. This API isolates the top-level applications (grid generators, solvers and visualization components) from the geometry engine. Also this allows the replacement of one geometry kernel with another, without effecting these top-level applications. For example, if UniGraphics is used as the CAD package then Parasolid (UG's own geometry engine) can be used for all geometric queries so that no solid geometry information is lost in a translation. This is much better than STEP because when the data is queried, the same software is executed as used in the CAD system. Therefore, one analyzes the exact part that is in the CAD system. CAPRI uses the same idea as the commercial structural analysis codes but does not specify control. Software components of the CAD system are used, but the analysis suite, not the CAD operator, specifies the control of the software session. This also means that the license issues (may be) minimized and individuals need not have to know how to operate a CAD system in order to run the suite.

Haimes, Robert↗
NASA NTRS2011

Common Bolted Joint Analysis Tool

Common Bolted Joint Analysis Tool (comBAT) is an Excel/VB-based bolted joint analysis/optimization program that lays out a systematic foundation for an inexperienced or seasoned analyst to determine fastener size, material, and assembly torque for a given design. Analysts are able to perform numerous what-if scenarios within minutes to arrive at an optimal solution. The program evaluates input design parameters, performs joint assembly checks, and steps through numerous calculations to arrive at several key margins of safety for each member in a joint. It also checks for joint gapping, provides fatigue calculations, and generates joint diagrams for a visual reference. Optimum fastener size and material, as well as correct torque, can then be provided. Analysis methodology, equations, and guidelines are provided throughout the solution sequence so that this program does not become a "black box:" for the analyst. There are built-in databases that reduce the legwork required by the analyst. Each step is clearly identified and results are provided in number format, as well as color-coded spelled-out words to draw user attention. The three key features of the software are robust technical content, innovative and user friendly I/O, and a large database. The program addresses every aspect of bolted joint analysis and proves to be an instructional tool at the same time. It saves analysis time, has intelligent messaging features, and catches operator errors in real time.

Imtiaz, Kauser↗
NASA NTRS1982

Interim review of the Energy Efficient Engine /E3/ Program

The NASA-sponsored Energy Efficient Engine (E3) Program, which is now in its fourth year, is assessed from the viewpoint of one of its research contractors. Attention is given to the development status of the shroudless fan, segmented combustor and exhaust mixer components which are encompassed by the program. The shroudless fan blades are two-thirds hollow for lightness, and are fabricated by means of plies and cores subjected to hot isostatic pressing diffusion bonding. The combustor's segmented liner is cast from turbine blade materials. Exhaust mixer flow visualization tests are described. Consideration is given to the effects of integrating the technology described with the low and high pressure advanced turbines whose development is also part of the E3 program.

Gardner, W. B.↗
NASA NTRS1979

Seat test program

The test program has the objectives to: (1) evaluate severity of newspaper ignition source with contemporary seats (determine weight loss, visual damage, and if ignition source is severe enough to show improvement with new material configurations); (2) compare damage with jet A-1 ignition source; and (3) determine if materials for seat tests pass FAR 25 and obtain L01. Test configurations, data acquired, material test results, seat test results, and conclusions are presented.

Bricker, R. W.↗
NASA NTRS1979

Systems level feasibility study for the detection of extra-solar planets. Volume 1: Infrared interferometer (IRIS) known as the Stanford Concept

A sensor system for the direct detection of extrasolar planets from an Earth orbit is evaluated: a spinning, infrared interferometer (IRIS). It is shuttle deployed, free flying, requires no on-orbit assembly and no reservicing over a design life of five years. The sensor concept and the mission objectives are reviewed, and the performance characteristics of a baseline sensor for standard observation conditions are derived. A baseline sensor design is given and the enabling technology discussed. Cost and weight estimates are performed; and a schedule for an IRIS program including technology development and assessment of risk are given. Finally, the sensor is compared with the apodized visual telescope sensor (APOTS) proposed for the same mission. The major conclusions are: that with moderate to strong technology advances, particularly in the fields of long life cryogenics, dynamical control, mirror manufacturing, and optical alignment, the detection of a Jupiter like planet around a Sunlike star at a distance of 30 light years is feasible, with a 3 meter aperture and an observation time of 1 hour. By contrast, major and possibly unlikely breakthroughs in mirror technology are required for APOTS to match this performance.

Source record↗
NASA NTRS1982

Moonport to Spaceport - The changing face at KSC

The facilities and planned operations of the Orbiter Processing Facility (OPF) at Kennedy Space Center are described, noting an eventual goal of five to six weeks turnaround for the vehicle. The dual-bay OPF is being developed to handle processing of two Orbiters in parallel. Once in the facility, all fuels are drained, parts and systems needing maintenance are removed for shipping and refurbishing or repair in-place, hazardous cargo is secured, and a thorough visual inspection is made of all accessible areas. Mobile launch platforms previously used as transports in the Apollo program have been upgraded and modernized and serve for the Shuttle launch preparations. Details of launch procedures are outlined, and the reduction of launch personnel to 45 persons is mentioned. Finally, details of payload insertion and mating with the Spacelab modules are described, along with the progress on the test flights.

Boggs, W. H.↗
NASA NTRS1993

Lunar rover navigation concepts

With regard to the navigation of mobile lunar vehicles on the surface, candidate techniques are reviewed and progress of simulations and experiments made up to now are described. Progress that can be made through precursor investigations on Earth is considered. In the early seventies the problem was examined in a series of relevant tests made in the California desert. Meanwhile, Apollo rovers made short exploratory sorties and robotic Lunokhods traveled over modest distances on the Moon. In these early missions some of the required methods were demonstrated. The navigation problem for a lunar traverse can be viewed in three parts: to determine the starting point with enough accuracy to enable the desired mission; to determine the event sequence required to reach the site of each traverse objective; and to redetermine actual positions enroute. The navigator's first tool is a map made from overhead imagery. The Moon was almost completely photographed at moderate resolution by spacecraft launched in the sixties, but that data set provides imprecise topographic and selenodetic information. Therefore, more advanced orbital missions are now proposed as part of a resumed lunar exploration program. With the mapping coverage expected from such orbiters, it will be possible to use a combination of visual landmark navigation and external radio and optical references (Earth and Sun) to achieve accurate surface navigation almost everywhere on the near side of the Moon. On the far side and in permanently dark polar areas, there are interesting exploration targets where additional techniques will have to be used.

Burke, James D.↗
NASA NTRS2011

Improve Data Mining and Knowledge Discovery Through the Use of MatLab

Data mining is widely used to mine business, engineering, and scientific data. Data mining uses pattern based queries, searches, or other analyses of one or more electronic databases/datasets in order to discover or locate a predictive pattern or anomaly indicative of system failure, criminal or terrorist activity, etc. There are various algorithms, techniques and methods used to mine data; including neural networks, genetic algorithms, decision trees, nearest neighbor method, rule induction association analysis, slice and dice, segmentation, and clustering. These algorithms, techniques and methods used to detect patterns in a dataset, have been used in the development of numerous open source and commercially available products and technology for data mining. Data mining is best realized when latent information in a large quantity of data stored is discovered. No one technique solves all data mining problems; challenges are to select algorithms or methods appropriate to strengthen data/text mining and trending within given datasets. In recent years, throughout industry, academia and government agencies, thousands of data systems have been designed and tailored to serve specific engineering and business needs. Many of these systems use databases with relational algebra and structured query language to categorize and retrieve data. In these systems, data analyses are limited and require prior explicit knowledge of metadata and database relations; lacking exploratory data mining and discoveries of latent information. This presentation introduces MatLab(R) (MATrix LABoratory), an engineering and scientific data analyses tool to perform data mining. MatLab was originally intended to perform purely numerical calculations (a glorified calculator). Now, in addition to having hundreds of mathematical functions, it is a programming language with hundreds built in standard functions and numerous available toolboxes. MatLab's ease of data processing, visualization and its enormous availability of built in functionalities and toolboxes make it suitable to perform numerical computations and simulations as well as a data mining tool. Engineers and scientists can take advantage of the readily available functions/toolboxes to gain wider insight in their perspective data mining experiments.

Shaykhian, Gholam Ali↗
NASA NTRS2011

Improve Data Mining and Knowledge Discovery through the use of MatLab

Data mining is widely used to mine business, engineering, and scientific data. Data mining uses pattern based queries, searches, or other analyses of one or more electronic databases/datasets in order to discover or locate a predictive pattern or anomaly indicative of system failure, criminal or terrorist activity, etc. There are various algorithms, techniques and methods used to mine data; including neural networks, genetic algorithms, decision trees, nearest neighbor method, rule induction association analysis, slice and dice, segmentation, and clustering. These algorithms, techniques and methods used to detect patterns in a dataset, have been used in the development of numerous open source and commercially available products and technology for data mining. Data mining is best realized when latent information in a large quantity of data stored is discovered. No one technique solves all data mining problems; challenges are to select algorithms or methods appropriate to strengthen data/text mining and trending within given datasets. In recent years, throughout industry, academia and government agencies, thousands of data systems have been designed and tailored to serve specific engineering and business needs. Many of these systems use databases with relational algebra and structured query language to categorize and retrieve data. In these systems, data analyses are limited and require prior explicit knowledge of metadata and database relations; lacking exploratory data mining and discoveries of latent information. This presentation introduces MatLab(TradeMark)(MATrix LABoratory), an engineering and scientific data analyses tool to perform data mining. MatLab was originally intended to perform purely numerical calculations (a glorified calculator). Now, in addition to having hundreds of mathematical functions, it is a programming language with hundreds built in standard functions and numerous available toolboxes. MatLab's ease of data processing, visualization and its enormous availability of built in functionalities and toolboxes make it suitable to perform numerical computations and simulations as well as a data mining tool. Engineers and scientists can take advantage of the readily available functions/toolboxes to gain wider insight in their perspective data mining experiments.

Shaykahian, Gholan Ali↗