Search NASA⌕ Search

SEARCH · Search NASA

Results for “Hardware/Software Development”

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 127 records · Page 7

A simulator application of a 'hands-on throttle and stick' concept to a transport pilot/autopilot interface

This paper presents the initial experiences garnered in applying a multifunction control strategy, based on the U.S. Air Force's 'Hands-On Throttle-and-Stick' concept for fighter aircraft to a transport aircraft simulator. The multifunction control strategy involves the activation of various flight system/subsystem operations (such as guidance and control, communication, and navigation functions) by use of menu displays and throttle and stick switches. The initial application of this multifunction control (MFC) concept was developed around a pilot/autopilot interface, contrasting a conventional, dedicated autopilot interface to an MFC implementation. The simulator characteristics and autopilot functions, as well as the conventional interface and MFC hardware/software, which were utilized in the application, are described herein. Initial pilot reaction and suggested improvements to this particular implementation are discussed. The paper terminates with a glance at plans for improvements and future applications based on the outcome of this initial study.

Busquets, A. M.↗

Space Generic Open Avionics Architecture (SGOAA) standard specification

This standard establishes the Space Generic Open Avionics Architecture (SGOAA). The SGOAA includes a generic functional model, processing structural model, and an architecture interface model. This standard defines the requirements for applying these models to the development of spacecraft core avionics systems. The purpose of this standard is to provide an umbrella set of requirements for applying the generic architecture models to the design of a specific avionics hardware/software processing system. This standard defines a generic set of system interface points to facilitate identification of critical services and interfaces. It establishes the requirement for applying appropriate low level detailed implementation standards to those interfaces points. The generic core avionics functions and processing structural models provided herein are robustly tailorable to specific system applications and provide a platform upon which the interface model is to be applied.

Wray, Richard B.↗

A Network Contention Model for the Extreme-scale Simulator

The Extreme-scale Simulator (xSim) is a performance investigation toolkit for high-performance computing (HPC) hardware/software co-design. It permits running a HPC application with millions of concurrent execution threads, while observing its performance in a simulated extreme-scale system. This paper details a newly developed network modeling feature for xSim, eliminating the shortcomings of the existing network modeling capabilities. The approach takes a different path for implementing network contention and bandwidth capacity modeling using a less synchronous and accurate enough model design. With the new network modeling feature, xSim is able to simulate on-chip and on-node networks with reasonable accuracy and overheads.

Engelmann, Christian↗

Benchmark Generation and Simulation at Extreme Scale

The path to extreme scale high-performance computing (HPC) poses several challenges related to power, performance, resilience, productivity, programmability, data movement, and data management. Investigating the performance of parallel applications at scale on future architectures and the performance impact of different architectural choices is an important component of HPC hardware/software co-design. Simulations using models of future HPC systems and communication traces from applications running on existing HPC systems can offer an insight into the performance of future architectures. This work targets technology developed for scalable application tracing of communication events. It focuses on extreme-scale simulation of HPC applications and their communication behavior via lightweight parallel discrete event simulation for performance estimation and evaluation. Instead of simply replaying a trace within a simulator, this work promotes the generation of a benchmark from traces. This benchmark is subsequently exposed to simulation using models to reflect the performance characteristics of future-generation HPC systems. This technique provides a number of benefits, such as eliminating the data intensive trace replay and enabling simulations at different scales. The presented work features novel software co-design aspects, combining the ScalaTrace tool to generate scalable trace files, the ScalaBenchGen tool to generate the benchmark, and the xSim tool to assess the benchmark characteristics within a simulator.

Lagadapati, Mahesh↗

EPICS Channel Access Server for LabVIEW

It can be challenging to interface National Instruments LabVIEW (http://www.ni.com/labview/) with EPICS (http://www.aps.anl.gov/epics/). Such interface is required when an instrument control program was developed in LabVIEW but it also has to be part of global control system. This is frequently useful in big accelerator facilities. The Channel Access Server is written in LabVIEW, so it works on any hardware/software platform where LabVIEW is available. It provides full server functionality, so any EPICS client can communicate with it.

Zhukov, AlexanderP.↗

Simulation Control Graphical User Interface Logging Report

One of the many tasks of my project was to revise the code of the Simulation Control Graphical User Interface (SIM GUI) to enable logging functionality to a file. I was also tasked with developing a script that directed the startup and initialization flow of the various LCS software components. This makes sure that a software component will not spin up until all the appropriate dependencies have been configured properly. Also I was able to assist hardware modelers in verifying the configuration of models after they have been upgraded to a new software version. I developed some code that analyzes the MDL files to determine if any error were generated due to the upgrade process. Another one of the projects assigned to me was supporting the End-to-End Hardware/Software Daily Tag-up meeting.

Hewling, Karl B., Jr.↗

Tools for Simulation and Benchmark Generation at Exascale

The path to exascale high-performance computing (HPC) poses several challenges related to power, performance, resilience, productivity, programmability, data movement, and data management. Investigating the performance of parallel applications at scale on future architectures and the performance impact of different architecture choices is an important component of HPC hardware/software co-design. Simulations using models of future HPC systems and communication traces from applications running on existing HPC systems can offer an insight into the performance of future architectures. This work targets technology developed for scalable application tracing of communication events and memory profiles, but can be extended to other areas, such as I/O, control flow, and data flow. It further focuses on extreme-scale simulation of millions of Message Passing Interface (MPI) ranks using a lightweight parallel discrete event simulation (PDES) toolkit for performance evaluation. Instead of simply replaying a trace within a simulation, the approach is to generate a benchmark from it and to run this benchmark within a simulation using models to reflect the performance characteristics of future-generation HPC systems. This provides a number of benefits, such as eliminating the data intensive trace replay and enabling simulations at different scales. The presented work utilizes the ScalaTrace tool to generate scalable trace files, the ScalaBenchGen tool to generate the benchmark, and the xSim tool to run the benchmark within a simulation.

Lagadapati, Mahesh↗

EPICS Channel Access Server for LabVIEW

It can be challenging to interface National Instruments LabVIEW (http://www.ni.com/labview/) with EPICS (http://www.aps.anl.gov/epics/). Such interface is required when an instrument control program was developed in LabVIEW but it also has to be part of global control system. This is frequently useful in big accelerator facilities. The Channel Access Server is written in LabVIEW, so it works on any hardware/software platform where LabVIEW is available. It provides full server functionality, so any EPICS client can communicate with it.

Zhukov, Alexander P.↗

Intelligent systems technology infrastructure for integrated systems

A system infrastructure must be properly designed and integrated from the conceptual development phase to accommodate evolutionary intelligent technologies. Several technology development activities were identified that may have application to rendezvous and capture systems. Optical correlators in conjunction with fuzzy logic control might be used for the identification, tracking, and capture of either cooperative or non-cooperative targets without the intensive computational requirements associated with vision processing. A hybrid digital/analog system was developed and tested with a robotic arm. An aircraft refueling application demonstration is planned within two years. Initially this demonstration will be ground based with a follow-on air based demonstration. System dependability measurement and modeling techniques are being developed for fault management applications. This involves usage of incremental solution/evaluation techniques and modularized systems to facilitate reuse and to take advantage of natural partitions in system models. Though not yet commercially available and currently subject to accuracy limitations, technology is being developed to perform optical matrix operations to enhance computational speed. Optical terrain recognition using camera image sequencing processed with optical correlators is being developed to determine position and velocity in support of lander guidance. The system is planned for testing in conjunction with Dryden Flight Research Facility. Advanced architecture technology is defining open architecture design constraints, test bed concepts (processors, multiple hardware/software and multi-dimensional user support, knowledge/tool sharing infrastructure), and software engineering interface issues.

Lum, Henry↗

Combined effect of noise and vibration on passenger acceptance

An extensive research program conducted at NASA Langley Research Center to develop a comprehensive model of passenger comfort response to combined noise and vibration environments has been completed. This model was developed for use in the prediction and/or assessment of vehicle ride quality and as a ride quality design tool. The model has the unique capability to transform individual elements of vehicle interior noise and vibration into subjective units and combining the subjective units to produce a total subjective discomfort index as well as the other useful subjective indices. This paper summarizes the basic approach used in the development of the NASA ride comfort model, presents some of the more fundamental results obtained, describes several application of the model to operational vehicles, and discusses a portable, self-contained ride quality meter system that is a direct hardware/software implementation of the NASA comfort algorithm.

Leatherwood, J. D.↗

Logic in Memory Emulator

Logic in Memory Emulator (LiME) is a hardware/software tool specially designed for memory system evaluation and experiment. Emerging memories display a wide range of bandwidths, latencies, and capacities, making it challenging for the computer architect to navigate the design space of potential memory configurations, and for the application developer to assess performance implications of using such memories. With the LiME framework, architectural ideas can be prototyped in great detail yet with sufficient performance to support realistic evaluation on long running applications. LiME consists of two fundamental components: 1) the hardware and OS infrastructure for the emulator, and 2) a suite of benchmark applications to assist in characterizing the performance of current and future computer architectures. Some of the applications have been collected from other open source projects. Uses: Logging, replay and analysis of an application's memory behavior Evaluate impact of emerging memory technology on application performance. Emulate complex memory interactions in whole applications orders of magnitude faster than software simulation. Emulate acceleration hardware co-located with the memory subsystem. Features: Capture and log external memory accesses to a separate off-chip memory device without affecting application execution. Memory traces include the address, length, timestamp, and optionally the data for each transaction. Captured trace data can be saved to an SD card for off-line analysis. Configure a wide range of memory latencies in sub-nanosecond increments that encompass highbandwidth and storage class memories. Specify regions of interest (ROI) in applications to reduce the amount of trace data captured for analysis. Currently supports execution on Xilinx Zynq SoC which integrates an ARM processor with FPGA logic on a single device. Applications can be run under Linux or in bare metal mode on the ARM cores.

Jain, AbhishekK↗

SU-E-I-10: Automatic Monitoring of Accumulated Dose Indices From DICOM RDSR to Improve Radiation Safety in X-Ray Angiography

Purpose: To investigate the potential benefits of automatic monitoring of accumulated patient and staff dose indicators, i.e., CAK and KAP, from DICOM Radiation Dose Structured Reports (RDSR) in x-ray angiography (XA). Methods: Recently RDSR has enabled the convenient aggregation of dose indices and technique parameters for XA procedures. The information contained in RDSR objects for three XA systems, dedicated to different types of clinical procedures, has been collected and aggregated in a database for over one year using a system developed with open-source software at the Karolinska University Hospital. Patient weight was complemented to the RDSR data via an interface with the Hospital Information System (HIS). Results: The linearly approximated trend in KAP over a time period of a year for cerebrovascular, pelvic/peripheral vascular, and cardiovascular procedures showed a decrease of 12%, 20%, and 14%, respectively. The decrease was mainly due to hardware/software upgrades and new low-dose imaging protocols, and partially due to ongoing systematic radiation safety education of the clinical staff. The CAK was in excess of 3 Gy for 15 procedures, and exceeded 5 Gy for 3 procedures. The dose indices have also shown a significant dependence on patient weight for cardiovascular and pelvic/peripheral vascular procedures; a 10 kg shift in mean patient weight can result in a dose index increase of 25%. Conclusion: Automatic monitoring of accumulated dose indices can be utilized to notify the clinical staff and medical physicists when the dose index has exceeded a predetermined action level. This allows for convenient and systematic follow-up of patients in risk of developing deterministic skin injuries. Furthermore, trend analyses of dose indices over time is a valuable resource for the identification of potential positive or negative effects (dose increase/decrease) from changes in hardware, software, and clinical work habits.

60 APPLIED LIFE SCIENCES↗

PPOD Programmable pilot-oriented display

A general-purpose low cost research microprocessor system for general aviation was developed. This system is intended to be the vehicle for individual research efforts in low cost airborne hardware and software as well as advanced microprocessor based navigation systems and techniques. Two such research projects were undertaken, yielding results in the areas of micro hardware/software design, cost and performance, and pilot/computer interface. Low-cost flight software reliability and a time-difference based Loran approach procedure that eliminates the need for propagation corrections and latitude/longitude transformations are also discussed.

Elias, A. L.↗

Ground Software Technologies – Embracing Change: Mission Drivers and Technology Opportunities to Enable Long Lived Missions

Mission lifecycles have proven to extend well beyond their original design. The benefits to this are countless but introduce challenges in today’s rapidly changing ground infrastructure and software technologies used to enable mission success. What remains constant is the risk posture missions maintain when accepting change and the use of new technologies. Larger missions are ready for change in early lifecycle development but near launch and especially in operations, few continue to evolve beyond what is set in place in phase C. This paper will discuss how the Advance Multi-Mission Operations System (AMMOS) intends to address, three driving missions concerns: Maintaining functionality (hardware/software) for decades, rapidly responding to security vulnerabilities in software, and finally the ability to quickly evolve infrastructure and software changes. These driving concerns are briefly described below: 1. Maintaining functionality (hardware/software) for decades. Hardware updates considerably faster than 10 years ago. Expectations that a system can remain in place for more than 10 years is no longer valid. Expecting to find hardware replacements for a system older than 5 years will increasingly become more and more challenging. How than do missions plan for hardware changes for long lived missions? Principle Objective: Provide abstraction by virtualizing and containerizing software abstract away any hardware dependencies and package up the application lightweight units. 2. Rapidly responding to security vulnerabilities in software. Cost is often the main impediment and largely driven by the revalidation and testing of system that undergo change. In todays, environment security updates are a major diver demanding systems remain up to date. How then do missions accept these changes and avoid large testing efforts? Principle Objective: Help reduce the cost of re-testing by automation of testing, deployment, and compartmentalizing change. 3. Ability to quickly evolve infrastructure and software changes. Responding quickly to change is similar to the second concern in this paper regarding security vulnerabilities. In this case, it address broader concerns of updating software and infrastructure on a more realistic timeline. How do missions stay up to date with the most recent versions of software and allowing for improved functionality? Principle Objective: Use continuous integration techniques at the system level to ensure rapid turnaround. This paper explores each of these concerns in more detail. It focuses the AMMOS’s current plans, challenges and current roadmap.

Giovannoni, Brian J.↗

A Leak Monitor for Industry

GenCorp Aerojet Industrial Products, Lewis Research Center, Marshall Space Flight Center, and Case Western Reserve University developed a gas leak detection system, originally for use with the Space Shuttle propulsion system and reusable launch vehicles. The Model HG200 Automated Gas Leak Detection System has miniaturized sensors that can identify extremely low concentrations of hydrogen without requiring oxygen. A microprocessor-based hardware/software system monitors the sensors and displays the source and magnitude of hydrogen leaks in real time. The system detects trace hydrogen around pipes, connectors, flanges and pressure tanks, and has been used by Ford Motor Company in the production of a natural gas-powered car.

Source record↗

Development of KSC program for investigating and generating field failure rates. Volume 1: Summary and overview

A summary of the KSC program for investigating the reliability aspects of the ground support activities is presented. An analysis of unsatisfactory condition reports (RC), and the generation of reliability assessment of components based on the URC are discussed along with the design considerations for attaining reliable real time hardware/software configurations.

Bean, E. E.↗

Fly-by-light technology development plan

The driving factors and developments which make a fly-by-light (FBL) viable are discussed. Documentation, analyses, and recommendations are provided on the major issues pertinent to facilitating the U.S. implementation of commercial FBL aircraft before the turn of the century. Areas of particular concern include ultra-reliable computing (hardware/software); electromagnetic environment (EME); verification and validation; optical techniques; life-cycle maintenance; and basis and procedures for certification.

Todd, J. R.↗

Combining In-situ Diagnostics and Data Analytics for Discovery of Process-Structure-Property Relationships in AM parts – A Step Toward Digital Twins

In-situ additive manufacturing (AM) diagnostic tools (e.g., optical/infrared imaging, acoustic, etc.) already exist to correlate process anomalies to printed part defects. This current work aimed to augment existing capabilities by: 1) Incorporating in-situ imaging w/ machine learning (ML) image processing software (ORNL- developed "Peregrine") for AM process anomaly detection 2) Synchronizing multiple in-situ sensors for simultaneous analysis of AM build events 3) Correlating in-situ AM process data, generated part defects and part mechanical properties The key R&D question investigated was to determine if these new combined hardware/software tools could be used to successfully quantify defect distributions for parts build via SNL laser powder bed fusion (LPBF) machines, aiming to better understand data-driven process-structure-property- performance relationships. High resolution optical cameras and acoustic microphones were successfully integrated in two LPBF machines and linked to the Peregrine ML software. The software was successfully calibrated on both machines and used to image hundreds of layers of multiple builds to train the ML software in identifying printed part vs powder. The software's validation accuracy to identify this aspect increased from 56% to 98.8% over three builds. Lighting conditions inside the chamber were found to significantly impact ML algorithm predictions from in-situ sensors, so these were tailored to each machine's internal framework. Finally, 3D part reconstructions were successfully generated for a build from the compressed stack of layer-wise images. Resolution differences nearest and furthest from the optical camera were discussed. Future work aims to improve optical resolution, increase process anomalies identified, and integrate more sensor modalities.

36 MATERIALS SCIENCE↗