Search NASA⌕ Search

SEARCH · Search NASA

Results for “background software”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Enabling a Voice Management System for Space Applications

The sustainable missions beyond Low Earth Orbit (LEO) envisioned for NASA’s Artemis program will require autonomous capabilities. Moreover, Artemis mission crews will need a means to efficiently interact with a spacecraft’s autonomous systems. This interaction can be facilitated by voice and speech communications because voice-based controls enable users to interact hands- and eyes-free, allowing the user to better focus on critical tasks. The goal of our project was to explore the knowledge and technology needed to successfully design effective Voice User Interfaces (VUIs) for autonomous systems utilizing Human Centered Design (HCD) principles. The focus of the human factors’ aspect of engineering, pays close attention to psychological and physiological principles in the development of autonomous crew operation systems. A main objective was to understand how a crew member, through voice interaction, could efficiently and intuitively communicate with a notional autonomous vehicle system manager. This project was a part of the NASA Moon to Mars eXploration Systems and Habitation (M2M X-Hab) 2020 Academic Innovation Challenge. The work from the BLiSS Team, at the University of Michigan, resulted in the design of a system persona, Diego, to which an astronaut may quickly build trust with autonomous systems, to alleviate known stressors on mental health expected during long duration space missions. Optimal software to facilitate integration of the system persona into a reference Lunar orbiting Gateway station was defined. Additionally, a Speech to Text (STT) system and a Graphical User Interface (GUI) that could be implemented in future missions was developed on an Internet of Things (IOT) platform. The Voice User Interface (VUI) design for the M2M X-Hab 2020 project leveraged previous technology developed by the BLiSS team to incorporate a voice-based interface into NASA’s Platform for Autonomous Systems (NPAS) software. This required technologies to convert voice to text, conduct semantic interpretations, and convert responses from the autonomous system to text and to speech; additionally, the spacecraft background noise environment was assessed, a noise mitigation technique was developed, and a relatable personality for the autonomous system was developed in order to facilitate human-like conversations. The success of our effort was largely due to the diversity of the team that included expertise in Space Systems Engineering, Human Computer Interaction, Aerospace Engineering, Computer Science, Biomedical Engineering, and Applied Physics. The diverse perspectives fostered elaborate discussions, resulting in the conception of three main subsystems: (1) User-System, (2) NPAS-System, and (3) Environment-System. The VUI was unique and had to be efficient and intuitive. For this project, 5 subteams were formed, each with a separate objective, Voice Design team, Background Noise Mitigation team, Software Integration team and Graphical User Interface team. The BLiSS team crafted a personality for the VUI to enable human-like conversation and drive user adoption and trust. User surveys were completed and used to help determine the required VUI system personality traits by capturing perspectives and expectations of prospective “Artemis Generation Astronauts”. To further simulate human-like conversations, the system had to be able to quickly interpret user speech and be able to integrate with NASA’s NPAS platform for quick and reliable information transfer. The outcomes of our research were: (1) a working prototype user interface, that is compatible with NASA’s NPAS platform; (2) software that demonstrates the ability of the VUI system to interpret user requests and respond appropriately; (3) the capability to implement fully expanded conversations between user and system using intuitive communication in four request categories; and (4) software and hardware recommendations that optimize the system’s ability to operate in a noisy environment. Our research has laid the foundation for the development of VUI’s for autonomy, and provides a baseline for future VUI developments.

Voice user interface↗
NASA NTRS1993

Designers' models of the human-computer interface

Understanding design models of the human-computer interface (HCI) may produce two types of benefits. First, interface development often requires input from two different types of experts: human factors specialists and software developers. Given the differences in their backgrounds and roles, human factors specialists and software developers may have different cognitive models of the HCI. Yet, they have to communicate about the interface as part of the design process. If they have different models, their interactions are likely to involve a certain amount of miscommunication. Second, the design process in general is likely to be guided by designers' cognitive models of the HCI, as well as by their knowledge of the user, tasks, and system. Designers do not start with a blank slate; rather they begin with a general model of the object they are designing. The author's approach to a design model of the HCI was to have three groups make judgments of categorical similarity about the components of an interface: human factors specialists with HCI design experience, software developers with HCI design experience, and a baseline group of computer users with no experience in HCI design. The components of the user interface included both display components such as windows, text, and graphics, and user interaction concepts, such as command language, editing, and help. The judgments of the three groups were analyzed using hierarchical cluster analysis and Pathfinder. These methods indicated, respectively, how the groups categorized the concepts, and network representations of the concepts for each group. The Pathfinder analysis provides greater information about local, pairwise relations among concepts, whereas the cluster analysis shows global, categorical relations to a greater extent.

Gillan, Douglas J.↗
NASA NTRS1993

The repository-based software engineering program: Redefining AdaNET as a mainstream NASA source

The Repository-based Software Engineering Program (RBSE) is described to inform and update senior NASA managers about the program. Background and historical perspective on software reuse and RBSE for NASA managers who may not be familiar with these topics are provided. The paper draws upon and updates information from the RBSE Concept Document, baselined by NASA Headquarters, Johnson Space Center, and the University of Houston - Clear Lake in April 1992. Several of NASA's software problems and what RBSE is now doing to address those problems are described. Also, next steps to be taken to derive greater benefit from this Congressionally-mandated program are provided. The section on next steps describes the need to work closely with other NASA software quality, technology transfer, and reuse activities and focuses on goals and objectives relative to this need. RBSE's role within NASA is addressed; however, there is also the potential for systematic transfer of technology outside of NASA in later stages of the RBSE program. This technology transfer is discussed briefly.

Source record↗
NASA NTRS1998

Data Analysis of a Space Experiment: Common Software Tackles Uncommon Task

Presented here are the software adaptations developed by laboratory scientists to process the space experiment data products from three experiments on two International Microgravity Laboratory Missions (IML-1 and IML-2). The challenge was to accommodate interacting with many types of hardware and software developed by both European Space Agency (ESA) and NASA aerospace contractors, where data formats were neither commercial nor familiar to scientists. Some of the data had been corrupted by bit shifting of byte boundaries. Least-significant/most-significant byte swapping also occurred as might be expected for the various hardware platforms involved. The data consisted of 20 GBytes per experiment of both numerical and image data. A significant percentage of the bytes were consumed in NASA formatting with extra layers of packetizing structure. It was provided in various pieces to the scientists on magnetic tapes, Syquest cartridges, DAT tapes, CD-ROMS, analog video tapes, and by network FIP. In this paper I will provide some science background and present the software processing used to make the data useful in the months after the missions.

Wilkinson, R. Allen↗
NASA NTRS1988

Plume spectrometry for liquid rocket engine health monitoring

An investigation of Space Shuttle Main Engine (SSME) testing failures identified optical events which appeared to be precursors of those failures. A program was therefore undertaken to detect plume trace phenomena characteristic of the engine and to design a monitoring system, responsive to excessive activity in the plume, capable of delivering a warning of an anomalous condition. By sensing the amount of extraneous material entrained in the plume and considering engine history, it may be possible to identify wearing of failing components in time for a safe shutdown and thus prevent a catastrophic event. To investigate the possibilities of safe shutdown and thus prevent a monitor to initiate the shutdown procedure, a large amount of plume data were taken from SSME firings using laboratory instrumentation. Those data were used to design a more specialized instrument dedicated to rocket plume diagnostics. The spectral wavelength range of the baseline data was about 220 nanometers (nm) to 15 micrometer with special attention given to visible and near UV. The data indicates that a satisfactory design will include a polychromator covering the range of 250 nM to 1000 nM, along with a continuous coverage spectrometer, each having a resolution of at least 5A degrees. The concurrent requirements for high resolution and broad coverage are normally at odds with one another in commercial instruments, therefore necessitating the development of special instrumentation. The design of a polychromator is reviewed herein, with a detailed discussion of the continuous coverage spectrometer delayed to a later forum. The program also requires the development of applications software providing detection, variable background discrimination, noise reduction, filtering, and decision making based on varying historical data.

Powers, William T.↗
NASA NTRS1998

WARP3D-Release 10.8: Dynamic Nonlinear Analysis of Solids using a Preconditioned Conjugate Gradient Software Architecture

This report describes theoretical background material and commands necessary to use the WARP3D finite element code. WARP3D is under continuing development as a research code for the solution of very large-scale, 3-D solid models subjected to static and dynamic loads. Specific features in the code oriented toward the investigation of ductile fracture in metals include a robust finite strain formulation, a general J-integral computation facility (with inertia, face loading), an element extinction facility to model crack growth, nonlinear material models including viscoplastic effects, and the Gurson-Tver-gaard dilatant plasticity model for void growth. The nonlinear, dynamic equilibrium equations are solved using an incremental-iterative, implicit formulation with full Newton iterations to eliminate residual nodal forces. The history integration of the nonlinear equations of motion is accomplished with Newmarks Beta method. A central feature of WARP3D involves the use of a linear-preconditioned conjugate gradient (LPCG) solver implemented in an element-by-element format to replace a conventional direct linear equation solver. This software architecture dramatically reduces both the memory requirements and CPU time for very large, nonlinear solid models since formation of the assembled (dynamic) stiffness matrix is avoided. Analyses thus exhibit the numerical stability for large time (load) steps provided by the implicit formulation coupled with the low memory requirements characteristic of an explicit code. In addition to the much lower memory requirements of the LPCG solver, the CPU time required for solution of the linear equations during each Newton iteration is generally one-half or less of the CPU time required for a traditional direct solver. All other computational aspects of the code (element stiffnesses, element strains, stress updating, element internal forces) are implemented in the element-by- element, blocked architecture. This greatly improves vectorization of the code on uni-processor hardware and enables straightforward parallel-vector processing of element blocks on multi-processor hardware.

Koppenhoefer, Kyle C.↗
NASA NTRS1992

Expert system verification and validation study: ES V/V Workshop

The primary purpose of this document is to build a foundation for applying principles of verification and validation (V&V) of expert systems. To achieve this, some V&V as applied to conventionally implemented software is required. Part one will discuss the background of V&V from the perspective of (1) what is V&V of software and (2) V&V's role in developing software. Part one will also overview some common analysis techniques that are applied when performing V&V of software. All of these materials will be presented based on the assumption that the reader has little or no background in V&V or in developing procedural software. The primary purpose of part two is to explain the major techniques that have been developed for V&V of expert systems.

French, Scott↗
NASA NTRS1981

Identification and evaluation of software measures

A large scale, systematic procedure for identifying and evaluating measures that meaningfully characterize one or more elements of software development is described. The background of this research, the nature of the data involved, and the steps of the analytic procedure are discussed. An example of the application of this procedure to data from real software development projects is presented. As the term is used here, a measure is a count or numerical rating of the occurrence of some property. Examples of measures include lines of code, number of computer runs, person hours expended, and degree of use of top down design methodology. Measures appeal to the researcher and the manager as a potential means of defining, explaining, and predicting software development qualities, especially productivity and reliability.

Card, D. N.↗
NASA NTRS2004

Activity-Centric Approach to Distributed Programming

The first phase of an effort to develop a NASA version of the Cybele software system has been completed. To give meaning to even a highly abbreviated summary of the modifications to be embodied in the NASA version, it is necessary to present the following background information on Cybele: Cybele is a proprietary software infrastructure for use by programmers in developing agent-based application programs [complex application programs that contain autonomous, interacting components (agents)]. Cybele provides support for event handling from multiple sources, multithreading, concurrency control, migration, and load balancing. A Cybele agent follows a programming paradigm, called activity-centric programming, that enables an abstraction over system-level thread mechanisms. Activity centric programming relieves application programmers of the complex tasks of thread management, concurrency control, and event management. In order to provide such functionality, activity-centric programming demands support of other layers of software. This concludes the background information. In the first phase of the present development, a new architecture for Cybele was defined. In this architecture, Cybele follows a modular service-based approach to coupling of the programming and service layers of software architecture. In a service-based approach, the functionalities supported by activity-centric programming are apportioned, according to their characteristics, among several groups called services. A well-defined interface among all such services serves as a path that facilitates the maintenance and enhancement of such services without adverse effect on the whole software framework. The activity-centric application-program interface (API) is part of a kernel. The kernel API calls the services by use of their published interface. This approach makes it possible for any application code written exclusively under the API to be portable for any configuration of Cybele.

Levy, Renato↗
NASA NTRS1994

An overview of the Software Engineering Laboratory

This report describes the background and structure of the SEL organization, the SEL process improvement approach, and its experimentation and data collection process. Results of some sample SEL studies are included. It includes a discussion of the overall implication of trends observed over 17 years of process improvement efforts and looks at the return on investment based on a comparison of total investment in process improvement with the measurable improvements seen in the organization's software product.

Source record↗
NASA NTRS2015

Removing Background Noise with Phased Array Signal Processing

Preliminary results are presented from a test conducted to determine how well microphone phased array processing software could pull an acoustic signal out of background noise. The array consisted of 24 microphones in an aerodynamic fairing designed to be mounted in-flow. The processing was conducted using Functional Beam forming software developed by Optinav combined with cross spectral matrix subtraction. The test was conducted in the free-jet of the Nozzle Acoustic Test Rig at NASA GRC. The background noise was produced by the interaction of the free-jet flow with the solid surfaces in the flow. The acoustic signals were produced by acoustic drivers. The results show that the phased array processing was able to pull the acoustic signal out of the background noise provided the signal was no more than 20 dB below the background noise level measured using a conventional single microphone equipped with an aerodynamic forebody.

Background Noise↗
NASA NTRS1992

Daily quality assurance software for a satellite radiometer system

Six Differential Microwave Radiometers (DMR) on COBE (Cosmic Background Explorer) measure the large-angular-scale isotropy of the cosmic microwave background (CMB) at 31.5, 53, and 90 GHz. Quality assurance software analyzes the daily telemetry from the spacecraft to ensure that the instrument is operating correctly and that the data are not corrupted. Quality assurance for DMR poses challenging requirements. The data are differential, so a single bad point can affect a large region of the sky, yet the CMB isotropy requires lengthy integration times (greater than 1 year) to limit potential CMB anisotropies. Celestial sources (with the exception of the moon) are not, in general, visible in the raw differential data. A 'quicklook' software system was developed that, in addition to basic plotting and limit-checking, implements a collection of data tests as well as long-term trending. Some of the key capabilities include the following: (1) stability analysis showing how well the data RMS averages down with increased data; (2) a Fourier analysis and autocorrelation routine to plot the power spectrum and confirm the presence of the 3 mK 'cosmic' dipole signal; (3) binning of the data against basic spacecraft quantities such as orbit angle; (4) long-term trending; and (5) dipole fits to confirm the spacecraft attitude azimuth angle.

Keegstra, P. B.↗
NASA NTRS1993

The planetary data system educational CD-ROM

The Planetary Data System (PDS) is producing a special educational CD-ROM that contains samples of PDS datasets and is expected to be released in 1993. The CD-ROM will provide university-level instructors with PDS-compatible materials and information that can be used to construct student problem sets using real datasets. The main purposes of the CD-ROM are to facilitate wide use of planetary data and to introduce a large community to the PDS. To meet these objectives the Educational CD-ROM will also contain software to manipulate the data, background discussions about scientific questions that can be addressed with the data, and a suite of exercises that illustrate analysis techniques. Students will also be introduced to the SPICE concept, which is a new way of maintaining geometry and instrument information. The exercises will be presented at the freshman through graduate student levels. With simplification, some of the material should also be of use at the high school level.

Guinness, E. A.↗
NASA NTRS2020

Multibody Based Digital Astronaut Dynamics Simulation

BACKGROUND: This study provides the Software, Robotics, & Simulation Division at the NASA Johnson Space Center with a verification tool for multibody dynamics simulation requiring human motion. The motivation stems from current studies of several Vibration Isolation & Stabilization(VIS)system designs that attenuate the moments and forces which would be transmitted to a spacecraft during an exercise. A multibody dynamics model for a proposed VIS was available previously[1], therefore modeling of the VIS was not needed for this work. The interest here is in creating the multibody dynamics model of an astronaut in motion which may be utilized independently or while attached to a mechanism. An existing simulation [2] that utilizes OpenSim [3,4] and an in-house multibody dynamics package (MBDyn) [5] is used in order to verify the astronaut model. The main advantage this model will have over the existing simulation is that everything will be processed in one tool. METHODS AND RESULTS: Creating the simulation required; estimation of Body Segment Inertial Parameters (BSIP),a multibody model of the human-VIS system, joint acceleration profiles, and input files for MBDyn, which is used for this analysis. The scaling factors provided by Dumas et al. [6] are utilized in estimating the BSIP. Anthropometric data are used for estimating these parameters, the Anthropometric Survey of US Army Personnel (ANSUR II) [7] was the source. The astronaut model consists of 15 bodies, 14 joints and 32 degrees of freedom, with the dynamics topology generated using the center of mass locations and anthropometric data. MBDyn has an option for prescribed joint motion (PJM), which requires joint acceleration data as input. The joint angle data is first obtained from a motion capture system and then processed through code that has been created to generate approximate joint acceleration profiles. The topology tree for the astronaut model begins at the right foot up to the pelvis where there is one branch for going down the left leg and another for the torso. The torso branch leads to branches for the arms and a leaf body for the head/neck segment. For attachment to the VIS, the heel of the right foot is connected to the VIS platform through a fixed joint, resembling a foot restraint. The left foot does not attach to the platform in order to prevent a system with a closed loop. Topology and symmetry of the astronaut model were verified through kinematic analysis. Further verification of the forces and moments transmitted to the VIS were verified against the existing simulation. There was a satisfactory level of agreement when testing a simple motion, for example, rocking back and forth. Full exercise motions are to be tested soon. The main outcome has been a novel application of MBDyn for biomechanics modeling that is now available for dynamic simulations involving human motion. The estimation of BSIP was another useful result of this study, requiring only 15 inputs for generating mass properties of a theoretical astronaut model. Expansion on this work is possible by going through an alternative route in obtaining the joint motion data. Instead of high-tech and often expensive motion capture systems, an individual may watch videos with high focus and at a slow motion for each individual segment in order to determine the initial and final time and angle for that specific degree of freedom. Synthetic trajectories may also be created if there is no video reference available.

F N Matari↗
NASA NTRS2022

Fermi Gamma-ray Space Telescope

The Fermi Gamma-ray Space Telescope, a key mission in multiwavelength and multimessenger studies, has been surveying the γ-ray sky from its low-Earth orbit since 2008. Its two scientific instruments, the Gamma-ray Burst Monitor (GBM) and the Large Area Telescope (LAT), cover 8 orders of magnitude in photon energy. The GBM consists of 12 Sodium Iodide detectors and 2 Bismuth Germinate detectors, covering the 10 keV - 40 MeV energy range, arrayed on two sides of the spacecraft so as to view the entire sky that is not occulted by the Earth. The LAT is a pair production telescope based on silicon strip trackers, a Cesium Iodide calorimeter, and a plastic scintillator anticoincidence system. It covers the energy range from about 20 MeV to more than 500 GeV, with a field of view of about 2.4 steradians. Thanks to their huge fields of view, the instruments can observe the entire sky with a cadence of about an hour for GBM and about three hours for LAT. All γ-ray data from Fermi become public immediately, enabling a broad range of multiwavelength and multimessenger research. Over 3000 γ-ray bursts (GRBs), including GRB 170817A associated with a neutron star merger detected in gravitational waves, and 5000 high-energy sources, including the blazar TXS 0506+056 associated with high-energy neutrinos, have been detected by the Fermi instruments. The Fermi Science Support Center provides a wide array of resources to enable scientific use of the data, including background models, source catalogs, analysis software, documentation, and a Help Desk.

gamma rays↗
NASA NTRS1992

Astronomical data analysis software and systems I; Proceedings of the 1st Annual Conference, Tucson, AZ, Nov. 6-8, 1991

Consideration is given to a definition of a distribution format for X-ray data, the Einstein on-line system, the NASA/IPAC extragalactic database, COBE astronomical databases, Cosmic Background Explorer astronomical databases, the ADAM software environment, the Groningen Image Processing System, search for a common data model for astronomical data analysis systems, deconvolution for real and synthetic apertures, pitfalls in image reconstruction, a direct method for spectral and image restoration, and a discription of a Poisson imagery super resolution algorithm. Also discussed are multivariate statistics on HI and IRAS images, a faint object classification using neural networks, a matched filter for improving SNR of radio maps, automated aperture photometry of CCD images, interactive graphics interpreter, the ROSAT extreme ultra-violet sky survey, a quantitative study of optimal extraction, an automated analysis of spectra, applications of synthetic photometry, an algorithm for extra-solar planet system detection and data reduction facilities for the William Herschel telescope.

Worrall, Diana M.↗
NASA NTRS2007

Software Compensates Electronic-Nose Readings for Humidity

A computer program corrects for the effects of humidity on the readouts of an array of chemical sensors (an "electronic nose"). To enable the use of this program, the array must incorporate an independent humidity sensor in addition to sensors designed to detect analytes other than water vapor. The basic principle of the program was described in "Compensating for Effects of Humidity on Electronic Noses" (NPO-30615), NASA Tech Briefs, Vol. 28, No. 6 (June 2004), page 63. To recapitulate: The output of the humidity sensor is used to generate values that are subtracted from the outputs of the other sensors to correct for contributions of humidity to those readings. Hence, in principle, what remains after corrections are the contributions of the analytes only. The outputs of the non-humidity sensors are then deconvolved to obtain the concentrations of the analytes. In addition, the humidity reading is retained as an analyte reading in its own right. This subtraction of the humidity background increases the ability of the software to identify such events as spills in which contaminants may be present in small concentrations and accompanied by large changes in humidity.

Zhou, Hanying↗