Search NASA⌕ Search

SEARCH · Search NASA

Results for “software differences”

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 487 records · Page 27

Software dependability in the Tandem GUARDIAN system

Based on extensive field failure data for Tandem's GUARDIAN operating system this paper discusses evaluation of the dependability of operational software. Software faults considered are major defects that result in processor failures and invoke backup processes to take over. The paper categorizes the underlying causes of software failures and evaluates the effectiveness of the process pair technique in tolerating software faults. A model to describe the impact of software faults on the reliability of an overall system is proposed. The model is used to evaluate the significance of key factors that determine software dependability and to identify areas for improvement. An analysis of the data shows that about 77% of processor failures that are initially considered due to software are confirmed as software problems. The analysis shows that the use of process pairs to provide checkpointing and restart (originally intended for tolerating hardware faults) allows the system to tolerate about 75% of reported software faults that result in processor failures. The loose coupling between processors, which results in the backup execution (the processor state and the sequence of events) being different from the original execution, is a major reason for the measured software fault tolerance. Over two-thirds (72%) of measured software failures are recurrences of previously reported faults. Modeling, based on the data, shows that, in addition to reducing the number of software faults, software dependability can be enhanced by reducing the recurrence rate.

Lee, Inhwan↗

Software Engineering Technology Infusion Within NASA

Abstract technology transfer is of crucial concern to both government and industry today. In this paper, several software engineering technologies used within NASA are studied, and the mechanisms, schedules, and efforts at transferring these technologies are investigated. The goals of this study are: 1) to understand the difference between technology transfer (the adoption of a new method by large segments of an industry) as an industry-wide phenomenon and the adoption of a new technology by an individual organization (called technology infusion); and 2) to see if software engineering technology transfer differs from other engineering disciplines. While there is great interest today in developing technology transfer models for industry, it is the technology infusion process that actually causes changes in the current state of the practice.

Zelkowitz, Marvin V.↗

Aerosol and Surface Parameter Retrievals for a Multi-Angle, Multiband Spectrometer

This software retrieves the surface and atmosphere parameters of multi-angle, multiband spectra. The synthetic spectra are generated by applying the modified Rahman-Pinty-Verstraete Bidirectional Reflectance Distribution Function (BRDF) model, and a single-scattering dominated atmosphere model to surface reflectance data from Multiangle Imaging SpectroRadiometer (MISR). The aerosol physical model uses a single scattering approximation using Rayleigh scattering molecules, and Henyey-Greenstein aerosols. The surface and atmosphere parameters of the models are retrieved using the Lavenberg-Marquardt algorithm. The software can retrieve the surface and atmosphere parameters with two different scales. The surface parameters are retrieved pixel-by-pixel while the atmosphere parameters are retrieved for a group of pixels where the same atmosphere model parameters are applied. This two-scale approach allows one to select the natural scale of the atmosphere properties relative to surface properties. The software also takes advantage of an intelligent initial condition given by the solution of the neighbor pixels.

Broderick, Daniel↗

Quality Attributes for Mission Flight Software: A Reference for Architects

In the international standards for architecture descriptions in systems and software engineering (ISO/IEC/IEEE 42010), "concern" is a primary concept that often manifests itself in relation to the quality attributes or "ilities" that a system is expected to exhibit - qualities such as reliability, security and modifiability. One of the main uses of an architecture description is to serve as a basis for analyzing how well the architecture achieves its quality attributes, and that requires architects to be as precise as possible about what they mean in claiming, for example, that an architecture supports "modifiability." This paper describes a table, generated by NASA's Software Architecture Review Board, which lists fourteen key quality attributes, identifies different important aspects of each quality attribute and considers each aspect in terms of requirements, rationale, evidence, and tactics to achieve the aspect. This quality attribute table is intended to serve as a guide to software architects, software developers, and software architecture reviewers in the domain of mission-critical real-time embedded systems, such as space mission flight software.

Software architecture↗

pvplr-python: Python package implementation of PVplr for Performance Loss Rate (PLR) analysis

Due to software fragmentation, PV system modeling teams can be limited to language specific packages, preventing cross-sectional analysis of different modeling techniques and workflows. To this end, PVplr, a popular PV performance modeling R software package, has been ported to the Python programming language. To verify and test the robustness of the port, NSRDB data has been used to simulated PV installations at native resolution (~2 million Sites), with a variety of degradation rates, degradation patterns, and modules. Performance Ratios were calculated using the ported functions from pvplr-python and compared against Rdtools YoY values. Due to the complicated nature of degradation, a new metric has been proposed to quantify the performance loss of a system. The cumulative production loss, is the total amount of energy lost due to the degrading performance of the system. Cumulative production loss alleviates the problems with fitting linear functions to non-linear degradation. Cumulative Production loss was shown to better estimate the total lost revenue for non-linear degradation patterns. $XbX + UTC$ was found to most accurately predict the total lost revenue in simulated systems.

Kumar, Suraj↗

A toolbox and record for scientific models

Computational science presents a host of challenges for the field of knowledge-based software design. Scientific computation models are difficult to construct. Models constructed by one scientist are easily misapplied by other scientists to problems for which they are not well-suited. Finally, models constructed by one scientist are difficult for others to modify or extend to handle new types of problems. Construction of scientific models actually involves much more than the mechanics of building a single computational model. In the course of developing a model, a scientist will often test a candidate model against experimental data or against a priori expectations. Test results often lead to revisions of the model and a consequent need for additional testing. During a single model development session, a scientist typically examines a whole series of alternative models, each using different simplifying assumptions or modeling techniques. A useful scientific software design tool must support these aspects of the model development process as well. In particular, it should propose and carry out tests of candidate models. It should analyze test results and identify models and parts of models that must be changed. It should determine what types of changes can potentially cure a given negative test result. It should organize candidate models, test data, and test results into a coherent record of the development process. Finally, it should exploit the development record for two purposes: (1) automatically determining the applicability of a scientific model to a given problem; (2) supporting revision of a scientific model to handle a new type of problem. Existing knowledge-based software design tools must be extended in order to provide these facilities.

Ellman, Thomas↗

Development of a methodology for assessing the safety of embedded software systems

A Dynamic Flowgraph Methodology (DFM) based on an integrated approach to modeling and analyzing the behavior of software-driven embedded systems for assessing and verifying reliability and safety is discussed. DFM is based on an extension of the Logic Flowgraph Methodology to incorporate state transition models. System models which express the logic of the system in terms of causal relationships between physical variables and temporal characteristics of software modules are analyzed to determine how a certain state can be reached. This is done by developing timed fault trees which take the form of logical combinations of static trees relating the system parameters at different point in time. The resulting information concerning the hardware and software states can be used to eliminate unsafe execution paths and identify testing criteria for safety critical software functions.

Garrett, C. J.↗

GlennICE Simulation of 24, 28 and 36 Inch Diameter eVTOL Propellers in Forward Flight

Flow solutions and water collection results are presented for three different propeller sizes. Flow solutions were generated using the NASA FUN3D software, and water collection was simulated using NASA GlennICE software. The geometries considered represent experimental articles that have been tested in the NASA Icing Research Tunnel. Each configuration has four blades. For the experiment, the same spinner centerbody is used for each propeller size. The different sized blades are similar for radii larger than about 40% of total span. Operating conditions were chosen to match operating points where experimental data was collected. Results are presented for both single bin simulations, as well as 7-bin Langmuir D distributions. For 80 microns MVD the Langmuir D distribution showed small differences compared to the single bin. For 15 microns MVD the Langmuir D distribution had a larger impact, especially on the spinner. In the experiment, the centerbody was unchanged as propeller size was changed. In this paper, additional simulations were completed with the 36 inch case perfectly scaled down to 24 and 28 inch. The perfect geometric scaling allows for an assessment of the effect of constant centerbody size on the results. While slight differences in pressure distribution on the propeller are visible between scaled and non-scaled centerbody, the effect seems quite minimal regarding water collection. All simulations were run very cold to ensure rime ice, since handling runback water in the non-inertial frame is beyond the scope of the present work. Ice shapes were generated using a single time step growth. The total mass on the blade and spinner was generally underpredicted for 15 microns MVD, and overpredicted for 80 microns MVD. When comparing ice shapes at operating conditions the numerical results produce very similar ice shapes.

Aircraft Icing↗

GlennICE Simulation of 24, 28 and 36 Inch Diameter eVTOL Propellers in Forward Flight

Flow solutions and water collection results are presented for three different propeller sizes. Flow solutions were generated using the NASA FUN3D software, and water collection was simulated using NASA GlennICE software. The geometries considered represent experimental articles that have been tested in the NASA Icing Research Tunnel. Each configuration has four blades. For the experiment, the same spinner centerbody is used for each propeller size. The different sized blades are similar for radii larger than about 40% of total span. Operating conditions were chosen to match operating points where experimental data was collected. Results are presented for both single bin simulations, as well as 7-bin Langmuir D distributions. For 80 microns MVD the Langmuir D distribution showed small differences compared to the single bin. For 15 microns MVD the Langmuir D distribution had a larger impact, especially on the spinner. In the experiment, the centerbody was unchanged as propeller size was changed. In this paper, additional simulations were completed with the 36 inch case perfectly scaled down to 24 and 28 inch. The perfect geometric scaling allows for an assessment of the effect of constant centerbody size on the results. While slight differences in pressure distribution on the propeller are visible between scaled and non-scaled centerbody, the effect seems quite minimal regarding water collection. All simulations were run very cold to ensure rime ice, since handling runback water in the non-inertial frame is beyond the scope of the present work. Ice shapes were generated using a single time step growth. The total mass on the blade and spinner was generally underpredicted for 15 microns MVD, and overpredicted for 80 microns MVD. When comparing ice shapes at operating conditions the numerical results produce very similar ice shapes.

Aircraft Icing↗

Implementation of Stochastic Gradient Descent in an Automated Glow Peak Identification Software for Multiple Thermoluminescent Dosimeter Types

A glow-curve analysis code was previously developed in C++ to analyze thermoluminescent dosimeter glow curves using automated peak detection while applying a first-order kinetics model. A newer version of this code was implemented to improve the automated peak detection and curve fitting models. The Stochastic Gradient Descent Algorithm was introduced to replace the prior approach of taking first and second-order derivatives for peak detection. Additionally, early stopping mechanisms were invoked to improve the previously used Levenberg-Marquardt Algorithm employed for curve fitting. The two software versions were compared through glow curve analysis of different thermoluminescent dosimeter materials and calculation of the corresponding figures of merit. Altogether improvements were shown, namely an increase in the number of peaks detected and a reduction of the mean figure of merit by approximately 46%.

137Cs↗

GammaCore: The Compton Observatory research environment

The Compton Observatory Science Support Center (COSSC) is developing a coherent analysis environment for the analysis of Compton and other gamma-ray astronomy data. This environment, GammaCore, allows the astronomer to access the data analysis systems developed at the Principal Investigator (PI) sites for the four Compton Observatory instruments. In addition users have access to standard astronomical tools such as IRAF, IDL, and XANADU. The user interface of GammaCore is the AGCL (AnswerGarden Command Language), developed at the AXAF Science Center. The parameter interface supported by the AGCL allows GammaCore to access all PI software systems in a uniform fashion. These systems are quite different, having been developed independently on heterogeneous systems without much concern for general portability. The data kibitzer concept, where a window running in a specific PI environment is controlled by the AGCL, has been used extensively. Users can choose to view what is going on in the native environment, to use the window to control PI software directly, or to ignore the PI systems entirely and to work only through the homogeneous AGCL interface. Software developed at the COSSC is also integrated within GammaCore. Extensive facilities for conversions of PI data formats to and from FITS have been developed. Access to the Compton data archive and catalogs will also be completely integrated with the GammaCore. Users can retrieve any publicly available Compton data. This paper examines the issues that have arisen in attempting to meld these widely diverse systems. The advantages and limitations of the parameter interface and the kibitzer are discussed along with issues of data portability, documentation, and the feasibility of multi-instrument analysis. Limited capabilities are now available within GammaCore with significant enhancements planned over the coming year. An implementation including all PI systems will be available within that time. Instructions on how to access GammaCore and how to get more information are given.

Mcglynn, T. A.↗

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IV&V) Program, with Software Assurance Research Program support, extracted FM architectures across the IV&V portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IV&V projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management. The identification of particular FM architectures, visibility, and associated IV&V techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. Additionally, the role FM has with regard to strengthened security requirements, with potential to advance overall asset protection of flight software systems, is being addressed with the development of an adverse conditions database encompassing flight software vulnerabilities. Capitalizing on the established framework, this TR suite provides assurance capability for a variety of FM architectures and varied development approaches. Research results are being disseminated across NASA, other agencies, and the software community. This paper discusses the findings and TR suite informing the FM domain in best practices for FM architectural design, visibility observations, and methods employed for IV&V and mission assurance.

Fitz, Rhonda↗

Link Analysis in the Mission Planning Lab

The legacy communications link analysis software currently used at Wallops Flight Facility involves processes that are different for command destruct, radar, and telemetry. There is a clear advantage to developing an easy-to-use tool that combines all the processes in one application. Link Analysis in the Mission Planning Lab (MPL) uses custom software and algorithms integrated with Analytical Graphics Inc. Satellite Toolkit (AGI STK). The MPL link analysis tool uses pre/post-mission data to conduct a dynamic link analysis between ground assets and the launch vehicle. Just as the legacy methods do, the MPL link analysis tool calculates signal strength and signal- to-noise according to the accepted processes for command destruct, radar, and telemetry assets. Graphs and other custom data are generated rapidly in formats for reports and presentations. STK is used for analysis as well as to depict plume angles and antenna gain patterns in 3D. The MPL has developed two interfaces with the STK software (see figure). The first interface is an HTML utility, which was developed in Visual Basic to enhance analysis for plume modeling and to offer a more user friendly, flexible tool. A graphical user interface (GUI) written in MATLAB (see figure upper right-hand corner) is also used to quickly depict link budget information for multiple ground assets. This new method yields a dramatic decrease in the time it takes to provide launch managers with the required link budgets to make critical pre-mission decisions. The software code used for these two custom utilities is a product of NASA's MPL.

McCarthy, Jessica A.↗

Implementation of J-A Methodology Elastic-Plastic Crack Instability Analysis Capability into the WARP-3D Code

Characterization of the near crack-tip stress/strain fields is the foundation of fracture mechanics. The description of the near tip stress field and the prediction of when fracture occurs is well established for brittle materials that exhibit linear elastic behavior. However, in ductile materials or conditions that violate linear elastic assumptions (Aluminum alloys, Al 2024-T3, Al 2024- T351 etc.), the elastic-plastic crack-tip stress fields are characterized by the Hutchison-Rice-Rosengren (HRR) field. The J-integral is commonly used to characterize amplitude of the HRR field under elastic-plastic conditions. The J-integral has been demonstrated for crack-tip fields that are under high constraint conditions (i.e., small-scale plasticity where the J-dominance is maintained). However, as the external load increases, yielding changes from small- to largescale plasticity and usually a loss of constraint (i.e., reduction in the triaxial stress field along the crack front). The loss of constraint leads to the deviation of the crack-tip stress fields from that given by the HRR field. Hence, the J-dominance will be gradually lost and additional parameter(s) are required to quantify the crack-tip stress fields and predict fracture behavior. The assessment objectives were to: 1) implement a two-parameter (i.e., J-A) fracture criterion into an elastic-plastic three-dimensional (3D) finite element analysis (FEA), 2) validate the implementation by comparison with the A parameter from literature data, 3) conduct material characterization tests to quantify the material behavior and provide fracture data for validation of the J-A fracture criteria, and (4) perform evaluations to establish if the J-A criteria can be used to predict fracture in a ductile metallic material (e.g., aluminum alloys). The A parameter in these criteria is the second parameter in a three-term elastic-plastic asymptotic expansion of the neartip stress behavior. A series of extensive FEAs were performed using WARP3D software package to obtain solutions for the A parameter for different specimen configurations. The methodology needed for the estimation of the A parameter in the asymptotic expansion was developed and implemented using Matlab®. A user material (UMAT) routine was used to model the material stress-strain response using a Ramberg-Osgood power law with a hardening exponent (n) and a material coefficient (alpha). This UMAT routine was successfully implemented in WARP3D software and validated through comparison with the experimental data. Three configurations were extracted from published results: 1) center cracked plate (CCP), 2) single edge-cracked plate (SECP), and 3) double edge-cracked plate (DECP). These configurations and four other configurations (three-hole tension (THT)), three-point bend (3PTB), three-hole compact tension (3PCT), and compact tension (CT)) were analyzed to verify the methodology that was developed and implemented into WARP3D. Solutions of the A parameter were obtained for remote tension loading conditions that started with small-scale yielding and continued into the large-scale plasticity regime. The results indicate that the methodology developed can be used to calculate the elastic-plastic J-A parameters for test specimens with a range of crack geometries, material strain hardening behaviors, and loading conditions. The J-A parameters were implemented as fracture criteria and used to predict the test results. For comparison, other fracture criteria were used to predict the same test results. Major findings include: The A constraint parameter A varies with specimen type and applied load thus accurate determination is crucial in predicting the failure load, and the A parameter is asymptotic as the failure load is approached, making an accurate determination difficult (i.e., small differences in the A parameter can cause large variations in failure load) for materials exhibiting elastic-plastic behavior. The failure predictions from J-A methodology were more accurate than the traditionally used KC and J methods, and have comparable scatter to that observed when using the crack-tip opening angle (CTOA) method. However, the J-A methodology requires considerable effort (expertise level and labor) to implement and to evaluate the A parameter for different specimen types and materials, or to apply this methodology to part-through crack (e.g., 3D problems) structural applications.

Hamm, Kenneth R., Jr.↗

New literal approximations for the longitudinal dynamic characteristics of flexible flight vehicles

The goal of the literal approximation method is to obtain simple literal (analytical) approximations for key dynamic characteristics of flexible flight vehicles. A basic question regarding the method is its usefulness as an additional design tool for existing design and simulation procedures. Two aspects of this question are: (1) ease of derivation and use of the literal approximations, and (2) the suitability of one set of literal approximations to describe the dynamics of a large set of significantly different vehicles. These issues are addressed by incorporating symbolic manipulation software into the literal approximation method for the analysis of a fifth order model of the longitudinal dynamics of a flexible flight vehicle. The automated literal approximation generated in this fashion reduces the manual derivation time by an approximate factor of four. A single set of literal approximations is shown to provide adequate approximations for the dynamics of significantly different flight vehicles configurations, such as an aircraft, a missile, and a hypersonic vehicle.

Livneh, Rafael↗

A Systematic Comparison for Consistent Scenario Development Using Microscopic Simulation Software

This study aims to explore a methodology that enables the development of consistent traffic micro simulation for emerging traffic and vehicle control technologies for improved mobility and energy efficiency across different modeling platforms. Researchers might study the same application on different platforms and have the need to benchmark across platforms. However, there lacks a systematic study on simulation software comparison, especially for emerging mobility and energy efficiency applications. For this, a systematic scenario development and evaluation approach is presented and demonstrated to compare scenarios generated in different traffic microsimulation platforms. Network-level and vehicle-level trip performance results of the traffic scenario are evaluated in three microscopic simulation platforms - VISSIM, AIMSUN, and SUMO. The results indicate that the network-level performance is consistent among the three software suites except when the demand is high, where the energy consumption performance varies.

Saroj, Abhilasha [ORNL] (ORCID:0000000191178063)↗

ELISA, a demonstrator environment for information systems architecture design

This paper describes an approach of reusability of software engineering technology in the area of ground space system design. System engineers have lots of needs similar to software developers: sharing of a common data base, capitalization of knowledge, definition of a common design process, communication between different technical domains. Moreover system designers need to simulate dynamically their system as early as possible. Software development environments, methods and tools now become operational and widely used. Their architecture is based on a unique object base, a set of common management services and they host a family of tools for each life cycle activity. In late '92, CNES decided to develop a demonstrative software environment supporting some system activities. The design of ground space data processing systems was chosen as the application domain. ELISA (Integrated Software Environment for Architectures Specification) was specified as a 'demonstrator', i.e. a sufficient basis for demonstrations, evaluation and future operational enhancements. A process with three phases was implemented: system requirements definition, design of system architectures models, and selection of physical architectures. Each phase is composed of several activities that can be performed in parallel, with the provision of Commercial Off the Shelves Tools. ELISA has been delivered to CNES in January 94, currently used for demonstrations and evaluations on real projects (e.g. SPOT4 Satellite Control Center). It is on the way of new evolutions.

Panem, Chantal↗

The need for a comprehensive expert system development methodology

In a traditional software development environment, the introduction of standardized approaches has led to higher quality, maintainable products on the technical side and greater visibility into the status of the effort on the management side. This study examined expert system development to determine whether it differed enough from traditional systems to warrant a reevaluation of current software development methodologies. Its purpose was to identify areas of similarity with traditional software development and areas requiring tailoring to the unique needs of expert systems. A second purpose was to determine whether existing expert system development methodologies meet the needs of expert system development, management, and maintenance personnel. The study consisted of a literature search and personal interviews. It was determined that existing methodologies and approaches to developing expert systems are not comprehensive nor are they easily applied, especially to cradle to grave system development. As a result, requirements were derived for an expert system development methodology and an initial annotated outline derived for such a methodology.

Baumert, John↗