Search NASA⌕ Search

SEARCH · Search NASA

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 541 records · Page 30
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

Quantitative simulation of extraterrestrial engineering devices

This is a multicomponent, multidisciplinary project whose overall objective is to build an integrated database, simulation, visualization, and optimization system for the proposed oxygen manufacturing plant on Mars. Specifically, the system allows users to enter physical description, engineering, and connectivity data through a uniform, user-friendly interface and stores the data in formats compatible with other software also developed as part of this project. These latter components include: (1) programs to simulate the behavior of various parts of the plant in Martian conditions; (2) an animation program which, in different modes, provides visual feedback to designers and researchers about the location of and temperature distribution among components as well as heat, mass, and data flow through the plant as it operates in different scenarios; (3) a control program to investigate the stability and response of the system under different disturbance conditions; and (4) an optimization program to maximize or minimize various criteria as the system evolves into its final design. All components of the system are interconnected so that changes entered through one component are reflected in the others.

Arabyan, A.↗
NASA NTRS2016

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗
NASA NTRS1999

A User's Manual for ROTTILT Solver: Tiltrotor Fountain Flow Field Prediction

A CFD solver has been developed to provide the time averaged details of the fountain flow typical for tiltrotor aircraft in hover. This Navier-Stokes solver, designated as ROTTILT, assumes the 3-D fountain flowfield to be steady and incompressible. The theoretical background is described in this manual. In order to enable the rotor trim solution in the presence of tiltrotor aircraft components such as wing, nacelle, and fuselage, the solver is coupled with a set of trim routines which are highly efficient in CPU and suitable for CFD analysis. The Cartesian grid technique utilized provides the user with a unique capability for insertion or elimination of any components of the bodies considered for a given tiltrotor aircraft configuration. The flowfield associated with either a semi or full-span configuration can be computed through user options in the ROTTILT input file. Full details associated with the numerical solution implemented in ROTTILT and assumptions are presented. A description of input surface mesh topology is provided in the appendices along with a listing of all preprocessor programs. Input variable definitions and default values are provided for the V22 aircraft. Limited predicted results using the coupled ROTTILT/WOPWOP program for the V22 in hover are made and compared with measurement. To visualize the V22 aircraft and predictions, a preprocessor graphics program GNU-PLOT3D was used. This program is described and example graphic results presented.

Tadghighi, Hormoz↗
NASA NTRS2005

Parallel Rendering of Large Time-Varying Volume Data

Interactive visualization of large time-varying 3D volume datasets has been and still is a great challenge to the modem computational world. It stretches the limits of the memory capacity, the disk space, the network bandwidth and the CPU speed of a conventional computer. In this SURF project, we propose to develop a parallel volume rendering program on SGI's Prism, a cluster computer equipped with state-of-the-art graphic hardware. The proposed program combines both parallel computing and hardware rendering in order to achieve an interactive rendering rate. We use 3D texture mapping and a hardware shader to implement 3D volume rendering on each workstation. We use SGI's VisServer to enable remote rendering using Prism's graphic hardware. And last, we will integrate this new program with ParVox, a parallel distributed visualization system developed at JPL. At the end of the project, we Will demonstrate remote interactive visualization using this new hardware volume renderer on JPL's Prism System using a time-varying dataset from selected JPL applications.

Garbutt, Alexander E.↗
NASA NTRS2006

Identifying Trends in Deep Space Network Monitor Data

A computer program has been developed that analyzes Deep Space Network monitor data, looking for changes of trends in critical parameters. This program represents a significant improvement over the previous practice of manually plotting data and visually inspecting the resulting graphs to identify trends. This program uses proven numerical techniques to identify trends. When a statistically significant trend is detected, then it is characterized by means of a symbol that can be used by pre-existing model-based reasoning software. The program can perform any of the following functions: Given an expectation that data in a given list should exhibit an upward, downward, constant, or unknown trend, it can determine whether the data do or do not follow such a trend. Given a list of data, it can identify which of the aforementioned trends the data follow. Given two lists of data, it can determine whether or not both follow the same trend. This program can be executed on a variety of computers. It can be distributed in either source code or binary code form. It must be run in conjunction with any one of a number of Lisp compilers that are available commercially or as shareware.

James, Mark↗
NASA NTRS1993

RighTime: A real time clock correcting program for MS-DOS-based computer systems

A computer program is described which effectively eliminates the misgivings of the DOS system clock in PC/AT-class computers. RighTime is a small, sophisticated memory-resident program that automatically corrects both the DOS system clock and the hardware 'CMOS' real time clock (RTC) in real time. RighTime learns what corrections are required without operator interaction beyond the occasional accurate time set. Both warm (power on) and cool (power off) errors are corrected, usually yielding better than one part per million accuracy in the typical desktop computer with no additional hardware, and RighTime increases the system clock resolution from approximately 0.0549 second to 0.01 second. Program tools are also available which allow visualization of RighTime's actions, verification of its performance, display of its history log, and which provide data for graphing of the system clock behavior. The program has found application in a wide variety of industries, including astronomy, satellite tracking, communications, broadcasting, transportation, public utilities, manufacturing, medicine, and the military.

Becker, G. Thomas↗
NASA NTRS2005

Facilitating Navigation Through Large Archives

Automated Visual Access (AVA) is a computer program that effectively makes a large collection of information visible in a manner that enables a user to quickly and efficiently locate information resources, with minimal need for conventional keyword searches and perusal of complex hierarchical directory systems. AVA includes three key components: (1) a taxonomy that comprises a collection of words and phrases, clustered according to meaning, that are used to classify information resources; (2) a statistical indexing and scoring engine; and (3) a component that generates a graphical user interface that uses the scoring data to generate a visual map of resources and topics. The top level of an AVA display is a pictorial representation of an information archive. The user enters the depicted archive by either clicking on a depiction of subject area cluster, selecting a topic from a list, or entering a query into a text box. The resulting display enables the user to view candidate information entities at various levels of detail. Resources are grouped spatially by topic with greatest generality at the top layer and increasing detail with depth. The user can zoom in or out of specific sites or into greater or lesser content detail.

Shelton, Robert O.↗
NASA NTRS2005

Reference Models for Structural Technology Assessment and Weight Estimation

Previously the Exploration Concepts Branch of NASA Langley Research Center has developed techniques for automating the preliminary design level of launch vehicle airframe structural analysis for purposes of enhancing historical regression based mass estimating relationships. This past work was useful and greatly reduced design time, however its application area was very narrow in terms of being able to handle a large variety in structural and vehicle general arrangement alternatives. Implementation of the analysis approach presented herein also incorporates some newly developed computer programs. Loft is a program developed to create analysis meshes and simultaneously define structural element design regions. A simple component defining ASCII file is read by Loft to begin the design process. HSLoad is a Visual Basic implementation of the HyperSizer Application Programming Interface, which automates the structural element design process. Details of these two programs and their use are explained in this paper. A feature which falls naturally out of the above analysis paradigm is the concept of "reference models". The flexibility of the FEA based JAVA processing procedures and associated process control classes coupled with the general utility of Loft and HSLoad make it possible to create generic program template files for analysis of components ranging from something as simple as a stiffened flat panel, to curved panels, fuselage and cryogenic tank components, flight control surfaces, wings, through full air and space vehicle general arrangements.

Cerro, Jeff↗
NASA NTRS1994

A Study on the Effect of Communication Performance on Message-Passing Parallel Programs: Methodology and Case Studies

From a source-program perspective, the performance achieved on distributed/parallel systems is governed by the underlying message-passing library overhead and the network capabilities of the architecture. Studying the impact of changes in these features on the source-program. can have a significant influence in the development of next-generation system designs. In this paper we introduce a simple and robust tool that can be used for this purpose. This tool is based on event-driven simulation of programs that generates a new set of trace events - that preserves causality and partial order - corresponding to the expected execution of the program in the simulated environment. Trace events can be visualized and source-level profile information can be used to pin-point locations of program which are most significantly affected with changing system parameters in the simulated environment. We present a number of examples from the NAS benchmark suite, executed on the Intel Paragon and iPSC/860 that are used to identify and expose performance bottlenecks with varying system parameters. Specific aspects of the system that significantly effect these benchmarks are presented and discussed,

Sarukkai, Sekhar R.↗
NASA NTRSDate not supplied

2023 Artemis Crew Health and Performance System Model Development

While the NASA Human Research Program (HRP) utilizes a Crew Health and Performance (CHP) System to represent all the Agency’s efforts to ensure the health and performance of NASA astronauts, there is no shared mental model of a CHP system at NASA. Some groups may consider a CHP system to be only a medical kit, while others may not be using the concept at all. To facilitate the integration of functions and capabilities to ensure astronaut health and performance during vehicle development, HRP has proposed a CHP Shared Mental Model derived from the NASA Human Health, Medical, and Performance Spaceflight Standards (NASA-STD-3001 Vol.1/Vol.2). [1] Even though many vehicle, ground, and communication systems as well as mission operations are modeled for the Artemis Campaigns, no mission level CHP system model was created to achieve the intent of the HRP CHP Shared Mental Model. The lack of this model renders it difficult to visualize and understand how the many programs work together to provide the necessary cross program functions and capabilities to ensure the health and performance of the crew throughout an Artemis mission. For this purpose, the Exploration Medical Capability (ExMC) element of HRP developed a CHP system model for the Artemis III and IV missions to provide a view of how each program contributes to and interacts with the overall CHP system. To develop the 2023 Artemis CHP system model, ExMC leveraged existing data and models from the Moon to Mars Program Office, the Office of the Chief Health and Medical Officer (OCHMO) and the Orion, Gateway, Extravehicular Activity and Human Surface Mobility (EHP) and Human Landing System (HLS) programs. By using a Model-Based Systems Engineering (MBSE) approach, existing requirements, functions, and concepts of operations were combined to create a single system model focused on representing CHP from the launch to the return to Earth segments of the Artemis III and IV missions. Additionally, by incorporating the HRP Systems Platform for Aggregating and Relating Capabilities, or SPARC tool, the data from the programs was also related back to the 2nd volume of the NASA Human Health, Medical, and Performance Spaceflight Standard (NASA-STD-3001, Vol.2) and the human system risks identified by the Human System Risk Board (HSRB). The first version of the 2023 Artemis CHP system model was baselined in Fall of 2023 after the model was demonstrated to be a potentially useful tool for systems engineers integrating CHP capabilities in vehicle development as well as members of the Health and Medical Technical Authority providing oversight of those programs. The model may also be useful to any stakeholder of astronaut health and performance by providing insights on how an Artemis mission satisfies the NASA Human Health, Medical, and Performance Spaceflight Standards as well as how they mitigate the HSRB Human System Risks. This presentation highlights how the model was developed and the possible benefits of the model. [1] NASA HRP (2022), Crew Health and Performance System Whitepaper

Systems engineering↗
NASA NTRS2024

2023 Artemis Crew Health and Performance (CHP) System Model Development

While the NASA Human Research Program (HRP) utilizes a Crew Health and Performance (CHP) System to represent all the Agency’s efforts to ensure the health and performance of NASA astronauts, there is no shared mental model of a CHP system at NASA. Some groups may consider a CHP system to be only a medical kit, while others may not be using the concept at all. To facilitate the integration of functions and capabilities to ensure astronaut health and performance during vehicle development, HRP has proposed a CHP Shared Mental Model derived from the NASA Human Health, Medical, and Performance Spaceflight Standards (NASA-STD-3001 Vol.1/Vol.2). [1] Even though many vehicle, ground, and communication systems as well as mission operations are modeled for the Artemis Campaigns, no mission level CHP system model was created to achieve the intent of the HRP CHP Shared Mental Model. The lack of this model renders it difficult to visualize and understand how the many programs work together to provide the necessary cross program functions and capabilities to ensure the health and performance of the crew throughout an Artemis mission. For this purpose, the Exploration Medical Capability (ExMC) element of HRP developed a CHP system model for the Artemis III and IV missions to provide a view of how each program contributes to and interacts with the overall CHP system. To develop the 2023 Artemis CHP system model, ExMC leveraged existing data and models from the Moon to Mars Program Office, the Office of the Chief Health and Medical Officer (OCHMO) and the Orion, Gateway, Extravehicular Activity and Human Surface Mobility (EHP) and Human Landing System (HLS) programs. By using a Model-Based Systems Engineering (MBSE) approach, existing requirements, functions, and concepts of operations were combined to create a single system model focused on representing CHP from the launch to the return to Earth segments of the Artemis III and IV missions. Additionally, by incorporating the HRP Systems Platform for Aggregating and Relating Capabilities, or SPARC tool, the data from the programs was also related back to the 2nd volume of the NASA Human Health, Medical, and Performance Spaceflight Standard (NASA-STD-3001, Vol.2) and the human system risks identified by the Human System Risk Board (HSRB). The first version of the 2023 Artemis CHP system model was baselined in Fall of 2023 after the model was demonstrated to be a potentially useful tool for systems engineers integrating CHP capabilities in vehicle development as well as members of the Health and Medical Technical Authority providing oversight of those programs. The model may also be useful to any stakeholder of astronaut health and performance by providing insights on how an Artemis mission satisfies the NASA Human Health, Medical, and Performance Spaceflight Standards as well as how they mitigate the HSRB Human System Risks. This presentation highlights how the model was developed and the possible benefits of the model. [1] NASA HRP (2022), Crew Health and Performance System Whitepaper

Systems engineering↗
NASA NTRS2005

ASK Magazine; No. 21

THIS ISSUE FEATURES A VISUAL DEPICTION OF THE ACADEMY of Program and Project Leadership (APPL). I imagine a variety of initial reactions to the drawing. One might be, "What is a cartoon doing in a magazine about project management?" Or perhaps, "Wow, nice colors-and fun." Another may be to closely search the image for signs, symbols and meaning. Still another, to read a new level of innovation and creativity into the picture. Undoubtedly, some readers will raise questions about the cost. Of course, any reaction is a sign of engagement. The stronger, the more energized the emotional and cognitive processing, the better. It is a sign of attention and interaction. For I've heard it said, "You only need to worry if they don t care one way or the other." So what is the point of the picture? To stimulate interest, raise questions, promote discussion, and maybe raise a smile.. .That, at least, was my initial reaction when I was introduced to the work of Nancy Hegedus, who helps to create these drawings for Root Learning Inc. At the NASA PM Conference, I was first shown the work Nancy had been doing with the help of Goddard s Knowledge Management Architect, Dr. Ed Rogers. I was immediately drawn into the power of visualization as a tool for more effective learning, communicating, and conveying complex knowledge concepts. We need new tools in today s world, where information and data overwhelms by sheer volume. There are articles, pamphlets, communications, and white papers-all aiming to convince and influence. Reactions to these tend to be either avoidance or mind-numbing, heavy-eyed consent; the message never registers or enters the soul. That s one of the reasons that APPL s Knowledge Sharing Initiative (KSI) has turned to storytelling as a memorable way of transfer- ring knowledge, inspiring imitation of best practices, and spurring reflection. ASK Magazine s recent fourth birthday marks an important milestone in APPL s continuing quest to provide ongoing support to project managers and to promote mission success. And similar to storytelling, the power of visualization is receiving increasing attention in recent years as a way to stimulate engagement. Pictures and visual graphs are viewed as one of the most effective ways for displaying, describing, and generating discussion about quantitative and technically complex information. Prototypes, models, and simulations are considered essential for stimulating innovation through open and engaging discussions. There has also been extensive writing on the use of visual graphics, pictures, and cartoons to facilitate memory, creativity, openness, attention-and even well-being. For many of these reasons, I am excited to have a colorful visual depiction of the APPL world included in ASK. Without the addition of text or slides, the intent is to invite people into the world of the APPL mission-as well as its products, services, customers, and partners- in a fun and engaging manner. As project leaders strive to find ways to encourage engagement, learning, and transmission of knowledge, traditional technologies are proving to be as valuable as modern technologies. (But for those who want more information in the form of texts and slide presentations, we certainly have an abundance of those as well.)

Laufer, Alexander↗
NASA NTRS2001

Quantifying the performance limits of human saccadic targeting during visual search

In previous studies of saccadic targeting, the issue how visually guided saccades to unambiguous targets are programmed and executed has been examined. These studies have found different degrees of guidance for saccades depending on the task and task difficulty. In this study, we use ideal-observer analysis to estimate the visual information used for the first saccade during a search for a target disk in noise. We quantitatively compare the performance of the first saccadic decision to that of the ideal observer (ie absolute efficiency of the first saccade) and to that of the associated final perceptual decision at the end of the search (ie relative efficiency of the first saccade). Our results show, first, that at all levels of salience tested, the first saccade is based on visual information from the stimulus display, and its highest absolute efficiency is approximately 20%. Second, the efficiency of the first saccade is lower than that of the final perceptual decision after active search (with eye movements) and has a minimum relative efficiency of 19% at the lowest level of saliency investigated. Third, we found that requiring observers to maintain central fixation (no saccades allowed) decreased the absolute efficiency of their perceptual decision by up to a factor of two, but that the magnitude of this effect depended on target salience. Our results demonstrate that ideal-observer analysis can be extended to measure the visual information mediating saccadic target-selection decisions during visual search, which enables direct comparison of saccadic and perceptual efficiencies.

Non-NASA Center↗
NASA NTRS1994

FAST User Guide

The Flow Analysis Software Toolkit, FAST, is a software environment for visualizing data. FAST is a collection of separate programs (modules) that run simultaneously and allow the user to examine the results of numerical and experimental simulations. The user can load data files, perform calculations on the data, visualize the results of these calculations, construct scenes of 3D graphical objects, and plot, animate and record the scenes. Computational Fluid Dynamics (CFD) visualization is the primary intended use of FAST, but FAST can also assist in the analysis of other types of data. FAST combines the capabilities of such programs as PLOT3D, RIP, SURF, and GAS into one environment with modules that share data. Sharing data between modules eliminates the drudgery of transferring data between programs. All the modules in the FAST environment have a consistent, highly interactive graphical user interface. Most commands are entered by pointing and'clicking. The modular construction of FAST makes it flexible and extensible. The environment can be custom configured and new modules can be developed and added as needed. The following modules have been developed for FAST: VIEWER, FILE IO, CALCULATOR, SURFER, TOPOLOGY, PLOTTER, TITLER, TRACER, ARCGRAPH, GQ, SURFERU, SHOTET, and ISOLEVU. A utility is also included to make the inclusion of user defined modules in the FAST environment easy. The VIEWER module is the central control for the FAST environment. From VIEWER, the user can-change object attributes, interactively position objects in three-dimensional space, define and save scenes, create animations, spawn new FAST modules, add additional view windows, and save and execute command scripts. The FAST User Guide uses text and FAST MAPS (graphical representations of the entire user interface) to guide the user through the use of FAST. Chapters include: Maps, Overview, Tips, Getting Started Tutorial, a separate chapter for each module, file formats, and system administration.

Walatka, Pamela P.↗