Final guidance software package for digital flight control and landing system
Guidance software package for digital flight control and landing system of CH-46C helicopter
Source record↗
SEARCH · Engineering Papers
Results for “system 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.
Computer-Aided System Engineering and Analysis (CASE/A) Programmer's Manual, Version 5.0
The Computer Aided System Engineering and Analysis (CASE/A) Version 5.0 Programmer's Manual provides the programmer and user with information regarding the internal structure of the CASE/A 5.0 software system. CASE/A 5.0 is a trade study tool that provides modeling/simulation capabilities for analyzing environmental control and life support systems and active thermal control systems. CASE/A has been successfully used in studies such as the evaluation of carbon dioxide removal in the space station. CASE/A modeling provides a graphical and command-driven interface for the user. This interface allows the user to construct a model by placing equipment components in a graphical layout of the system hardware, then connect the components via flow streams and define their operating parameters. Once the equipment is placed, the simulation time and other control parameters can be set to run the simulation based on the model constructed. After completion of the simulation, graphical plots or text files can be obtained for evaluation of the simulation results over time. Additionally, users have the capability to control the simulation and extract information at various times in the simulation (e.g., control equipment operating parameters over the simulation time or extract plot data) by using "User Operations (OPS) Code." This OPS code is written in FORTRAN with a canned set of utility subroutines for performing common tasks. CASE/A version 5.0 software runs under the VAX VMS(Trademark) environment. It utilizes the Tektronics 4014(Trademark) graphics display system and the VTIOO(Trademark) text manipulation/display system.
Knox, J. C.↗
Data from: "Soil moisture mediates alpine life form and community productivity responses to warming"
This dataset contains values that were used to support conclusions drawn in the publication “Soil moisture mediates alpine life form and community productivity responses to warming”, originally published in 2016 by Winkler et al. All data were collected in the alpine site of the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, in the Front Range of the Colorado Rocky Mountains, USA. The file types in this archive include comma-separated-values (.csv) files, and two types of geospatial files: .kml and shapefiles (.shp). The csv files can be opened by R, Microsoft Excel, or any simple text editor software. The geospatial files can be opened by Google Earth/Google Maps, and the ESRI shapefiles can be opened by geographic information systems softwares that can read shapefiles, including ESRI’s ArcGIS Desktop suite, and QGIS.Climate warming is expected to alter primary production and community composition in alpine systems around the globe. Whether production will increase in response to warming in the absence of additional precipitation remains underexplored. We experimentally warmed an alpine plant community on Niwot Ridge, Colorado to test whether warming increases or decreases productivity of multiple plant life form groups and the entire plant community. We also provided supplemental water to a subset of plots to alleviate potential drying effects of warming. We predicted alpine community above-ground productivity would increase in response to warming only when combined with supplemental water to limit soil drying. We also predicted plant life form groups would vary in their responses and would like buffer changes in community productivity.
54 ENVIRONMENTAL SCIENCES↗
Assessing Requirements Quality through Requirements Coverage
In model-based development, the development effort is centered around a formal description of the proposed software system the model. This model is derived from some high-level requirements describing the expected behavior of the software. For validation and verification purposes, this model can then be subjected to various types of analysis, for example, completeness and consistency analysis [6], model checking [3], theorem proving [1], and test-case generation [4, 7]. This development paradigm is making rapid inroads in certain industries, e.g., automotive, avionics, space applications, and medical technology. This shift towards model-based development naturally leads to changes in the verification and validation (V&V) process. The model validation problem determining that the model accurately captures the customer's high-level requirements has received little attention and the sufficiency of the validation activities has been largely determined through ad-hoc methods. Since the model serves as the central artifact, its correctness with respect to the users needs is absolutely crucial. In our investigation, we attempt to answer the following two questions with respect to validation (1) Are the requirements sufficiently defined for the system? and (2) How well does the model implement the behaviors specified by the requirements? The second question can be addressed using formal verification. Nevertheless, the size and complexity of many industrial systems make formal verification infeasible even if we have a formal model and formalized requirements. Thus, presently, there is no objective way of answering these two questions. To this end, we propose an approach based on testing that, when given a set of formal requirements, explores the relationship between requirements-based structural test-adequacy coverage and model-based structural test-adequacy coverage. The proposed technique uses requirements coverage metrics defined in [9] on formal high-level software requirements and existing model coverage metrics such as the Modified Condition and Decision Coverage (MC/DC) used when testing highly critical software in the avionics industry [8]. Our work is related to Chockler et al. [2], but we base our work on traditional testing techniques as opposed to verification techniques.
Rajan, Ajitha↗
Application Modernization at LLNL and the Sierra Center of Excellence
We repport that in 2014, Lawrence Livermore National Laboratory began acquisition of Sierra, a pre-exascale system from IBM and Nvidia. It marks a significant shift in direction for LLNL by introducing the concept of heterogeneous computing via GPUs. LLNL’s mission requires application teams to prepare for this paradigm shift. Thus, the Sierra procurement required a proposed Center of Excellence that would align the expertise of the chosen vendors with laboratory personnel that represent the application developers, system software, and tool providers in a concentrated effort to prepare the laboratory’s codes in advance of the system transitioning to production in 2018. Finally, this article presents LLNL’s overall application strategy, with a focus on how LLNL is collaborating with IBM and Nvidia to ensure a successful transition of its mission-oriented applications into the exascale era.
97 MATHEMATICS AND COMPUTING↗
Enabling Scalable and Extensible Memory-mapped Datastores in Userspace
Exascale workloads are expected to incorporate data-intensive processing in close coordination with traditional physics simulations. These emerging scientific, data-analytics and machine learning applications need to access a wide variety of datastores in flat files and structured databases. Programmer productivity is greatly enhanced by mapping datastores into the application process's virtual memory space to provide a unified “in-memory” interface. Currently, memory mapping is provided by system software primarily designed for generality and reliability. However, scalability at high concurrency is a formidable challenge on exascale systems. Also, there is a need for extensibility to support new datastores potentially requiring HPC data transfer services. In this article, we present UMap , a scalable and extensible userspace service for memory-mapping datastores. Furthermore, through decoupled queue management, concurrency aware adaptation, and dynamic load balancing, UMap enables application performance to scale even at high concurrency. We evaluate UMap in data-intensive applications, including sorting, graph traversal, database operations, and metagenomic analytics. Our results show that UMap as a userspace service outperforms an optimized kernel-based service across a wide range of intra-node concurrency by 1.22-1.9 × . We performed two case studies to demonstrate UMap 's extensibility. First, a new datastore residing in remote memory is incorporated into UMap as an application-specific plugin. Second, we present a persistent memory allocator Metall built atop UMap for unified storage/memory.
97 MATHEMATICS AND COMPUTING↗
IoT-Based Comfort Control and Fault Diagnostics System for Energy-Efficient Homes
This project studies an Internet of Things (IoT)-based comfort control and fault diagnostics system (referred as iComfort in this report) for energy-efficient homes. The system delivers an occupant-comfort-oriented thermal environment adaptive to fault scenarios and achieves HVAC energy savings in a cost-effective and straightforward way. This smart iComfort home system consists of the following key features. 1) Cost-effectiveness and scalability of the entire hardware and software system: The system includes low-cost temperature, humidity, and airflow sensors, and a Raspberry Pi-based local hub that interfaces with the cloud and IoT-enabled devices. The cost is low, not only for sensors, but also the costs associated with sensor installation, system setup and commissioning, data communication and storage, and data analytics (e.g., the development of automated fault detection and diagnosis (AFDD), as well as adaptive control strategies that are both computationally efficient and practical to implement). 2) Energy performance and user satisfaction: The system delivers user satisfaction and energy savings. This includes a) ease of use, b) optimal occupant thermal comfort, and c) accurate system feedback (e.g., low false alarm of AFDD strategies). 3) Favorable demonstrated prototype performance: The prototype tested at the Pacific Northwest National Laboratory (PNNL) Lab Homes demonstrates the accuracy of fault detections and diagnoses and shows thermal comfort improvement and energy savings through adaptive and optimal HVAC operations.
32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
Code Coverage Status of the ARC Code RCT
The Argonne Reactor Code (ARC) software system supports users in their fast reactor design goals by providing neutronic, thermal-hydraulic, and structural analysis capabilities. REBUS plays a pivotal role in the ARC system as the primary fuel cycle analysis capability for fast reactor problems. Over its 60 year history, ARC software usage with REBUS has been applied to numerous fast and thermal spectrum reactor analysis projects with good to excellent comparison against experiments. The RCT code is a later addition and uses the REBUS restart files to define its input. The RCT code was built to provide pin depletion details on EBR-II models and thus many features of RCT were specifically tailored to the needs of EBR-II models. Additional approximations were invoked which are likely only valid for the EBR-II reactor and the particular fuel management that was done for it. The purpose of the present work is to identify a set of test problems for RCT and assess the code coverage for those test problems. The goal is to document what parts of the existing RCT code are touched by the set of test problems and which are not. Because no detailed verification work has been done on RCT, the existing regression testing suite was chosen for the code coverage assessment. The code coverage analysis of RCT was performed with the Code Coverage Tool of the Intel Fortran compiler which requires modifications to the compilation of RCT. The detailed coverage tables are given for each part of RCT. As will be discussed and shown, some parts of the RCT capability that are known to be used by the EBR-II analysis work are not tested by the regression testing suite. These aspects should be resolved before major source code changes are taken for the RCT software. Because REBUS and DIF3D are not subroutines of RCT, the coverage changes in both of those codes is not altered by RCT. The same is true for all of the modules of DIF3D that are used by RCT such as SYSLIB and SEGLIB.
22 GENERAL STUDIES OF NUCLEAR REACTORS↗
Computer transformation of partial differential equations into any coordinate system
The use of tensors to provide a compact way of writing partial differential equations in a form valid in all coordinate systems is discussed. In order to find solutions to the equations with their boundary conditions they must be expressed in terms of the coordinate system under consideration. The process of arriving at these expressions from the tensor formulation was automated by a software system, TENSR. An allied system that analyzes the resulting expressions term by term and drops those that are negligible is also described.
Sullivan, R. D.↗
Integrated analysis of large space systems
Based on the belief that actual flight hardware development of large space systems will necessitate a formalized method of integrating the various engineering discipline analyses, an efficient highly user oriented software system capable of performing interdisciplinary design analyses with tolerable solution turnaround time is planned Specific analysis capability goals were set forth with initial emphasis given to sequential and quasi-static thermal/structural analysis and fully coupled structural/control system analysis. Subsequently, the IAC would be expanded to include a fully coupled thermal/structural/control system, electromagnetic radiation, and optical performance analyses.
Young, J. P.↗
A high order approach to flight software development and testing
The use of a software development facility is discussed as a means of producing a reliable and maintainable ECS software system, and as a means of providing efficient use of the ECS hardware test facility. Principles applied to software design are given, including modularity, abstraction, hiding, and uniformity. The general objectives of each phase of the software life cycle are also given, including testing, maintenance, code development, and requirement specifications. Software development facility tools are summarized, and tool deficiencies recognized in the code development and testing phases are considered. Due to limited lab resources, the functional simulation capabilities may be indispensable in the testing phase.
Steinbacher, J.↗
Design and validation of fault-tolerant flight systems
Flight systems must be validated to show that they are consistent with the requirements of their intended applications. While high reliability is difficult to validate, the additional complexity of fault tolerance further compounds the validation problem. The objective of NASA’s research is to develop a methodology for designing validatable fault-tolerant systems. Under the design-for-validation philosophy, emphasis is placed on developing validation methods that can be incorporated into the design process right from the start and design methods and guidance which, while incorporating fault tolerance, can assure validatability. This paper examines the statistical issues of validating highly reliable, fault tolerant system. There are many problems associated with traditional methods of designing and validating these potentially complex hardware and software systems. Useful design-for-validation methods, which include structured specification and design methodologies, mathematical proof techniques, analytical modeling, simulation and emulation, and physical testing, are discussed. Important design issues associated with fault tolerance are presented along with the related validation concerns which must be addressed. Experience has shown that synchronization and Byzantine resilience must accompany fault tolerance. Other design attributes associated with fault tolerance may be used by a designer on the basis of cost, weight, performance, and validation considerations.
Computer systems↗
Applications of different design methodologies in navigation systems and development at JPL
The NASA/JPL deep space navigation system consists of a complex array of measurement systems, data processing systems, and support facilities, with components located both on the ground and on-board interplanetary spacecraft. From its beginings nearly 30 years ago, this system has steadily evolved and grown to meet the demands for ever-increasing navigation accuracy placed on it by a succession of unmanned planetary missions. Principal characteristics of this system are its capabilities and great complexity. Three examples in the design and development of interplanetary space navigation systems are examined in order to make a brief assessment of the usefulness of three basic design theories, known as normative, rational, and heuristic. Evaluation of the examples indicates that a heuristic approach, coupled with rational-based mathematical and computational analysis methods, is used most often in problems such as orbit determination strategy development and mission navigation system design, while normative methods have seen only limited use is such applications as the development of large software systems and in the design of certain operational navigation subsystems.
Thurman, S. W.↗
An autonomous fault detection, isolation, and recovery system for a 20-kHz electric power distribution test bed
Future space explorations will require long term human presence in space. Space environments that provide working and living quarters for manned missions are becoming increasingly larger and more sophisticated. Monitor and control of the space environment subsystems by expert system software, which emulate human reasoning processes, could maintain the health of the subsystems and help reduce the human workload. The autonomous power expert (APEX) system was developed to emulate a human expert's reasoning processes used to diagnose fault conditions in the domain of space power distribution. APEX is a fault detection, isolation, and recovery (FDIR) system, capable of autonomous monitoring and control of the power distribution system. APEX consists of a knowledge base, a data base, an inference engine, and various support and interface software. APEX provides the user with an easy-to-use interactive interface. When a fault is detected, APEX will inform the user of the detection. The user can direct APEX to isolate the probable cause of the fault. Once a fault has been isolated, the user can ask APEX to justify its fault isolation and to recommend actions to correct the fault. APEX implementation and capabilities are discussed.
Quinn, Todd M.↗
Autonomous reconfigurable GPS/INS navigation and pointing system for rendezvous and docking
This paper describes the results of an integrated navigation and pointing system software development effort sponsored by the NASA MSFC through a SBIR Phase 2 Program. The integrated Global Positioning System (GPS)/Inertial Navigation System (INS) implements an autonomous navigation filter that is reconfigurable in real-time to accommodate mission contingencies. An onboard expert system monitors the spacecraft status and reconfigures the navigation filter accordingly, to optimize the system performance. The navigation filter is a multi-mode Kalman filter to estimate the spacecraft position, velocity, and attitude. Three different GPS-based attitude determination techniques, namely, velocity vector matching, attitude vector matching, and interferometric processing, are implemented to encompass different mission contingencies. The integrated GPS/INS navigation filter will use any of these techniques depending on the mission phase and the state of the sensors. The first technique, velocity vector matching, uses the GPS velocity measurement to estimate the INS velocity errors and exploits the correlation between INS velocity and attitude errors to estimate the attitude. The second technique, attitude vector matching, uses INS gyro measurements and GPS carrier phase (integrated Doppler) measurements during a spacecraft rotation maneuver to determine the attitude. Both of these techniques require only one GPS antenna onboard to determine the spacecraft attitude. The third technique, interferometric processing, requires use of multiple GPS antennae. In order to determine 3-axis body attitude, three GPS antennae (2 no-coplanor baselines) are required.
Upadhyay, Triveni N.↗
Description of the Experimental Avionics Systems Integration Laboratory (EASILY)
The Experimental Avionics Systems Integration Laboratory (EASILY) is a comprehensive facility used for development, integration, and preflight validation of hardware and software systems for the Terminal Area Productivity (TAP) Program's Transport Systems Research Vehicle (TSRV) experimental transport aircraft. This report describes the history, capabilities, and subsystems of EASILY. A functional description of the many subsystems is provided to give potential users the necessary knowledge of the capabilities of this facility.
Outlaw, Bruce K. E.↗
Computational Investigation of a Boundary-Layer Ingesting Propulsion System for the Common Research Model
The present paper examines potential propulsive and aerodynamic benefits of integrating a Boundary-Layer Ingestion (BLI) propulsion system into a typical commercial aircraft using the Common Research Model (CRM) geometry and the NASA Tetrahedral Unstructured Software System (TetrUSS). The Numerical Propulsion System Simulation (NPSS) environment is used to generate engine conditions for CFD analysis. Improvements to the BLI geometry are made using the Constrained Direct Iterative Surface Curvature (CDISC) design method. Previous studies have shown reductions of up to 25% in terms of propulsive power required for cruise for other axisymmetric geometries using the BLI concept. An analysis of engine power requirements, drag, and lift coefficients using the baseline and BLI geometries coupled with the NPSS model are shown. Potential benefits of the BLI system relating to cruise propulsive power are quantified using a power balance method, and a comparison to the baseline case is made. Iterations of the BLI geometric design are shown and any improvements between subsequent BLI designs presented. Simulations are conducted for a cruise flight condition of Mach 0.85 at an altitude of 38,500 feet and an angle of attack of 2 deg for all geometries. A comparison between available wind tunnel data, previous computational results, and the original CRM model is presented for model verification purposes along with full results for BLI power savings. Results indicate a 14.4% reduction in engine power requirements at cruise for the BLI configuration over the baseline geometry. Minor shaping of the aft portion of the fuselage using CDISC has been shown to increase the benefit from Boundary-Layer Ingestion further, resulting in a 15.6% reduction in power requirements for cruise as well as a drag reduction of eighteen counts over the baseline geometry.
Blumenthal, Brennan T.↗
What Machines Need to Learn to Support Human Problem-Solving
In the development of intelligent systems that interact with humans, there is often confusion between how the system functions with respect to the humans it interacts with and how it interfaces with those humans. The former is a much deeper challenge than the latter it requires a system-level understanding of evolving human roles as well as an understanding of what humans need to know (and when) in order to perform their tasks. This talk will focus on some of the challenges in getting this right as well as on the type of research and development that results in successful human-autonomy teaming. Brief Bio: Dr. Alonso Vera is Chief of the Human Systems Integration Division at NASA Ames Research Center. His expertise is in human-computer interaction, information systems, artificial intelligence, and computational human performance modeling. He has led the design, development and deployment of mission software systems across NASA robotic and human space flight missions, including Mars Exploration Rovers, Phoenix Mars Lander, ISS, Constellation, and Exploration Systems. Dr. Vera received a Bachelor of Science with First Class Honors from McGill University in 1985 and a Ph.D. from Cornell University in 1991. He went on to a Post-Doctoral Fellowship in the School of Computer Science at Carnegie Mellon University from 1990-93.
intelligent systems↗