Search NASA⌕ Search

SEARCH · Search NASA

Results for “software based”

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 343 records · Page 19
All sourcesNASA NTRSDOE OSTI
NASA NTRS2023

UAM Instrument Flight Procedure Design and Evaluation in the Joby Flight Simulator

NASA’s Advanced Air Mobility (AAM) National Campaign (NC) partnered with Joby Aviation to test and evaluate different developmental candidate Urban Air Mobility (UAM) Instrument Flight Procedure (IFP) designs including new departure, enroute, approach and missed approach architectures using Joby’s high-fidelity engineering aircraft simulator. In conjunction with the simulator testing, this effort also evaluated related aspects such as charting, coding, and adherence to flight planning criteria. The test objectives were to assess the safety, efficiency, passenger comfort and noise of the different variations of the developmental IFPs. Safety-related measures include clearance from terrain and vertical obstructions, procedure flyability, and flight path conformance. Efficiency-related measures included time required, airspace volume required, and battery energy required. Passenger comfort and ride quality measures include roll/pitch angles, roll/pitch attitude change rates, and airspeeds prior to aggressive maneuvers, subjective pilot/passenger responses and acceleration forces. The noise impacts of the different IFPs will be interpolated/extrapolated using data from the simulator fed into a separate Joby acoustic software-based tool. Overall, several tradeoffs were identified and characterized between the different variations of the developmental IFP profiles. No single version of the developmental IFP structure scored highest across all measures listed above; rather, different IFP variations proved optimal for different measures, confirming that the best IFP depends on which specific measures are prioritized for a given aircraft, location and operation.

National Campaign↗
NASA NTRS2022

Metrics for Flight Operations: Application to Europa Clipper Tour Selection

Objective measures are ubiquitous in the formulation, design and implementation of deep space missions. Tour durations, flyby altitudes, propellant budgets, power consumption, and other metrics are essential to developing and managing NASA missions. But beyond the simple metrics of cost and workforce, it has been difficult to identify objective, quantitative measures that assist in evaluating choices made during formulation or implementation phases in terms of their impact on flight operations. As part of the development of the Europa Clipper Mission system, a set of operations metrics have been defined along with the necessary design information and software tooling to calculate them. We have applied these methods and metrics to help assess the impact to the flight team on the six options for the Clipper Tour that are currently being vetted for selection in the fall of 2021. To generate these metrics, the Clipper MOS team first designed the set of essential processes by which flight operations will be conducted, using a standard approach and template to identify (among other aspects) timelines for each process, along with their time constraints (e.g., uplinks for sequence execution). Each of the resulting 50 processes is documented in a common format and concurred by stakeholders. Process timelines were converted into generic schedules and workforce-loaded using COTS scheduling software, based on the inputs of the process authors and domain experts. Custom code was generated to create an operations schedule for a specific portion of Clipper's prime mission, with instances of a given process scheduled based on specific timing rules (e.g., process X starts once per week on Thursdays) or relative to mission events (e.g., sequence generation process begins on a Monday, at least three weeks before each Europa closest approach). Over a 5-month period, and for each of six Clipper candidate tours, the result was a 20,000+ line, workforce-loaded schedule that documents all of the process-driven work effort at the level of individual roles, along with a significant portion of the level-of-effort work. Post-processing code calculated the absolute and relative number of work hours during a nominal 5 day / 40 hour work week, the work effort during 2nd and 3rd shift, as well as 1st shift on weekends. The resultant schedules and shift tables were used to generate objective measures that can be related to both human factors and to operational risk and showed that Clipper tours which utilize 6:1 resonant (21.25 day) orbits instead of 4:1 resonant (14.17 day) orbits during the first dozen or so Europa flybys are advantageous to flight operations. A similar approach can be extended to assist missions in more objective assessments of a number of mission issues and trades, including tour selection and spacecraft design for operability.

Sarrel, Marc↗
NASA NTRSDate not supplied

Enhancing Testing Capability in the V7012 Chamber

The NASA Marshal Space Flight Center (MSFC) is involved in developing a variety of propulsion technologies, including small thrusters using green propellant, for in-space propulsion. Better understanding of these propulsion technologies for space applications is vital to NASA’s mission to the Moon, Mars, and beyond. This project focuses on developing a three-dimensional diagnostic positioning system for use in propulsion testing in the 4205/101 9-foot diameter vacuum chamber at the Marshal Space Flight Center. It will permit rapid and precise positioning of plasma diagnostics (e.g. Faraday probe, Langmuir probe) for measuring properties in a thruster’s plume. This system will be computer controlled and will use either proprietary software (based on acquired hardware) or other available programs such as LABVIEW (National Instruments, Inc.). The pressure inside the 9-ft chamber during testing ranges from 10-3 to 10-6 Torr. The expected outcome of this effort will be an enhanced capability for propulsion testing. The results of this project will provide insight into the understanding of automated motion, control systems, and the principles of aerospace mechanical design.

Diagnostics↗
NASA NTRS1999

Flight Software Design Choices Based on Criticality

This slide presentation reviews the rationale behind flight software design as a function of criticality. The requirements of human rated systems implies a high criticality for the flight support software. Human life is dependent on correct operation of the software. Flexibility should be permitted when the consequences of software failure are not life threatening. This is also relevant for selecting Commercial Off the Shelf (COTS) software.

Lee, Earl↗
NASA NTRS1980

Orbit determination software development for microprocessor based systems: Evaluation and recommendations

A guide is presented for National Aeronautics and Space Administration management personnel who stand to benefit from the lessons learned in developing microprocessor-based flight dynamics software systems. The essential functional characteristics of microprocessors are presented. The relevant areas of system support software are examined, as are the distinguishing characteristics of flight dynamics software. Design examples are provided to illustrate the major points presented, and actual development experience obtained in this area is provided as evidence to support the conclusions reached.

Shenitz, C. M.↗
NASA NTRS1987

Investigation into the development of computer aided design software for space based sensors

The described effort is phase one of the development of a Computer Aided Design (CAD) software to be used to perform radiometric sensor design. The software package will be referred to as SCAD and is directed toward the preliminary phase of the design of space based sensor system. The approach being followed is to develop a modern, graphic intensive, user friendly software package using existing software as building blocks. The emphasis will be directed toward the development of a shell containing menus, smart defaults, and interfaces, which can accommodate a wide variety of existing application software packages. The shell will offer expected utilities such as graphics, tailored menus, and a variety of drivers for I/O devices. Following the development of the shell, the development of SCAD is planned as chiefly selection and integration of appropriate building blocks. The phase one development activities have included: the selection of hardware which will be used with SCAD; the determination of the scope of SCAD; the preliminary evaluation of a number of software packages for applicability to SCAD; determination of a method for achieving required capabilities where voids exist; and then establishing a strategy for binding the software modules into an easy to use tool kit.

Pender, C. W.↗
NASA NTRS2019

Model Based Engineering for Software Assurance

NASA's successful development of next generation space vehicles, habitats, and robotic systems will require reliable hardware and software systems. The aim of this initiative is to develop modeling methodology and tools to support Model-Based Systems Engineering (MBSE) for software assurance and reliability analysis. This effort expands the Unified Modeling Language (UML) software design models to include fault data for the extraction of Failure Modes and Effects Criticality Analysis (FMECA) and Fault Tree Analysis (FTA) for software. We explored different modeling approaches to integrate the UML software design models with the Systems Modeling Language (SysML) system models to generate an integrated model and reliability tools that take into account software and hardware interfaces.The benefits of this concept directly affect the safety community with quick turnarounds to produce software assurance and reliability analysis artifacts and the ability to visualize failure effects, both hardware and software. The result is enhanced system design integrity and early identification of system risks. This initiative will enable software assurance activities early in the system design lifecycle, facilitating the discovery of design weaknesses and enhancing the capability to produce safe, hazard-free systems

Wang, Lui↗
NASA NTRS1987

A measurement-based model of software reliability in a production environment

In this paper, a semi-Markov model is built to describe the software error and recovery process in a large mainframe system. The model is based on low-level error data from the MVS operating system running on an IBM 3081 machine. The semi-Markov model developed provides a quantification of system error characteristics and the interaction between different types of errors. As an example, a detailed model is provided, and an analysis is made of multiple errors, which constitute approximately an 17 percent of all software errors and result in considerable recovery overhead.

Hsueh, M. C.↗
NASA NTRS1992

Neural network-based retrieval from software reuse repositories

A significant hurdle confronts the software reuser attempting to select candidate components from a software repository - discriminating between those components without resorting to inspection of the implementation(s). We outline an approach to this problem based upon neural networks which avoids requiring the repository administrators to define a conceptual closeness graph for the classification vocabulary.

Eichmann, David A.↗
NASA NTRS2012

The Virtual Climate Data Server (vCDS): An iRODS-Based Data Management Software Appliance Supporting Climate Data Services and Virtualization-as-a-Service in the NASA Center for Climate Simulation

Scientific data services are becoming an important part of the NASA Center for Climate Simulation's mission. Our technological response to this expanding role is built around the concept of a Virtual Climate Data Server (vCDS), repetitive provisioning, image-based deployment and distribution, and virtualization-as-a-service. The vCDS is an iRODS-based data server specialized to the needs of a particular data-centric application. We use RPM scripts to build vCDS images in our local computing environment, our local Virtual Machine Environment, NASA s Nebula Cloud Services, and Amazon's Elastic Compute Cloud. Once provisioned into one or more of these virtualized resource classes, vCDSs can use iRODS s federation capabilities to create an integrated ecosystem of managed collections that is scalable and adaptable to changing resource requirements. This approach enables platform- or software-asa- service deployment of vCDS and allows the NCCS to offer virtualization-as-a-service: a capacity to respond in an agile way to new customer requests for data services.

Schnase, John L.↗
NASA NTRS2005

Achieving control and interoperability through unified model-based systems and software engineering

Control and interoperation of complex systems is one of the most difficult challenges facing NASA's Exploration Systems Mission Directorate. An integrated but diverse array of vehicles, habitats, and supporting facilities, evolving over the long course of the enterprise, must perform ever more complex tasks while moving steadily away from the sphere of ground support and intervention.

control↗
NASA NTRS1994

TDRSS Onboard Navigation System (TONS) flight qualification experiment

The National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) is currently developing an operational Tracking and Data Relay Satellite (TDRS) System (TDRSS) Onboard Navigation System (TONS) to provide realtime, autonomous, high-accuracy navigation products to users of TDRSS. A TONS experiment was implemented on the Explorer Platform/Extreme Ultraviolet Explorer (EP/EUVE) spacecraft, launched June 7, 1992, to flight qualify the TONS operational system using TDRSS forward-link communications services. This paper provides a detailed evaluation of the flight hardware, an ultrastable oscillator (USO) and Doppler extractor (DE) card in one of the TDRSS user transponders and the ground-based prototype flight software performance, based on the 1 year of TONS experiment operation. The TONS experiment results are used to project the expected performance of the TONS 1 operational system. TONS 1 processes Doppler data derived from scheduled forward-link S-band services using a sequential estimation algorithm enhanced by a sophisticated process noise model to provide onboard orbit and frequency determination and time maintenance. TONS 1 will be the prime navigation system on the Earth Observing System (EOS)-AM1 spacecraft, currently scheduled for launch in 1998. Inflight evaluation of the USO and DE short-term and long-term stability indicates that the performance is excellent. Analysis of the TONS prototype flight software performance indicates that realtime onboard position accuracies of better than 25 meters root-mean-square are achievable with one tracking contact every one to two orbits for the EP/EUVE 525-kilometer altitude, 28.5 degree inclination orbit. The success of the TONS experiment demonstrates the flight readiness of TONS to support the EOS-AM1 mission.

Gramling, C. J.↗
NASA NTRS1975

Commonality Study of the Pressure-Volume-Temperature Based Propellant Gaging Software Modules for the Auxiliary Power Unit, Reaction Control System, and Orbital Maneuvering System

Computer storage requirements can be reduced if areas of commonality exist in two or more programs placed in the same computer and identical code can be used by more than one program. The pressure-volume-temperature (P-V-T) relationship for the propellant tank pressurant agent is utilized as the basis for either a primary of a backup propellant gaging program for the auxiliary power unit (APU), the reaction control system (RCS), and the orbital maneuvering system (OMS). These three propellant gaging programs were investigated. It was revealed that a very limited degree of software commonality exits among them. An examination of this common software indicated that only the computation of the helium compressibility factor in an external function subprogram accessible to both the RCS and OMS propellant gaging programs appears to offer a savings in computer storage requirements.

Duhon, D. D.↗
NASA NTRS1992

A neural net-based approach to software metrics

Software metrics provide an effective method for characterizing software. Metrics have traditionally been composed through the definition of an equation. This approach is limited by the fact that all the interrelationships among all the parameters be fully understood. This paper explores an alternative, neural network approach to modeling metrics. Experiments performed on two widely accepted metrics, McCabe and Halstead, indicate that the approach is sound, thus serving as the groundwork for further exploration into the analysis and design of software metrics.

Boetticher, G.↗
NASA NTRS1993

Software synthesis using generic architectures

A framework for synthesizing software systems based on abstracting software system designs and the design process is described. The result of such an abstraction process is a generic architecture and the process knowledge for customizing the architecture. The customization process knowledge is used to assist a designer in customizing the architecture as opposed to completely automating the design of systems. Our approach using an implemented example of a generic tracking architecture which was customized in two different domains is illustrated. How the designs produced using KASE compare to the original designs of the two systems, and current work and plans for extending KASE to other application areas are described.

Bhansali, Sanjay↗
NASA NTRS1998

Developing Information Power Grid Based Algorithms and Software

This was an exploratory study to enhance our understanding of problems involved in developing large scale applications in a heterogeneous distributed environment. It is likely that the large scale applications of the future will be built by coupling specialized computational modules together. For example, efforts now exist to couple ocean and atmospheric prediction codes to simulate a more complete climate system. These two applications differ in many respects. They have different grids, the data is in different unit systems and the algorithms for inte,-rating in time are different. In addition the code for each application is likely to have been developed on different architectures and tend to have poor performance when run on an architecture for which the code was not designed, if it runs at all. Architectural differences may also induce differences in data representation which effect precision and convergence criteria as well as data transfer issues. In order to couple such dissimilar codes some form of translation must be present. This translation should be able to handle interpolation from one grid to another as well as construction of the correct data field in the correct units from available data. Even if a code is to be developed from scratch, a modular approach will likely be followed in that standard scientific packages will be used to do the more mundane tasks such as linear algebra or Fourier transform operations. This approach allows the developers to concentrate on their science rather than becoming experts in linear algebra or signal processing. Problems associated with this development approach include difficulties associated with data extraction and translation from one module to another, module performance on different nodal architectures, and others. In addition to these data and software issues there exists operational issues such as platform stability and resource management.

Dongarra, Jack↗
NASA NTRS1998

Developing Information Power Grid Based Algorithms and Software

This exploratory study initiated our effort to understand performance modeling on parallel systems. The basic goal of performance modeling is to understand and predict the performance of a computer program or set of programs on a computer system. Performance modeling has numerous applications, including evaluation of algorithms, optimization of code implementations, parallel library development, comparison of system architectures, parallel system design, and procurement of new systems. Our work lays the basis for the construction of parallel libraries that allow for the reconstruction of application codes on several distinct architectures so as to assure performance portability. Following our strategy, once the requirements of applications are well understood, one can then construct a library in a layered fashion. The top level of this library will consist of architecture-independent geometric, numerical, and symbolic algorithms that are needed by the sample of applications. These routines should be written in a language that is portable across the targeted architectures.

Dongarra, Jack↗