Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “software training plan”

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 199 records · Page 11

Report on activities and findings under DOE grant “Collaborative research. An Interactive Multi-Model for Consensus on Climate Change”

The project takes a hierarchical approach. The supermodeling scheme was first studied exhaustively with simple systems of ordinary differential equations. Results were described in detail in the previous report. The principal findings were that 1) for highly non-linear systems, such as Lorenz-63, including systems which describe phenomena on very different (atmosphere/ocean) times scales, supermodeling is far superior to any form of output-averaging; 2) negative coefficients can be used to advantage in situations where all models err in the same way, but to different degrees; 3) an interesting variant of supermodeling, “weighted supermodeling”, is the limiting case where inter-model nudging coefficients in the originally conceived “connected supermodel” become infinite, but with fixed ratios, corresponding to a direct combination of the tendencies that appear in corresponding equations for the alternative models; 4) noise is useful for avoiding local optima in training the inter-model coefficients in the supermodel. The supermodeling scheme was then investigated with simple quasigeostrophic (QG) models. As described in the previous report, it was found that QG models on a sphere can be coupled most efficaciously by working in a basis which captures the most variance, rather than the most instability, a somewhat unexpected result that still deserves scrutiny in a broader context. Further studies (since the last report) with QG channel models addressed the central question of when supermodeling is superior to output averaging in situations where nonlinearites are less extreme than with the ODEs initially studied. It was found that for realistic variations in a parameter in the QG model, output averaging is sufficient to capture all but the most subtle quantitative and qualitative behavior. Supermodeling helps when qualitative differences between the models result from unrealistically large parameter differences, or when very detailed spatial structure of the modes of variability are of interest. Therefore, the scheme may still be useful in the case of full climate models with qualitatively different parametrization schemes. A supermodel was constructed from the intermediate-complexity SPEEDO model, a primitive equation model with ocean and land. Versions defined by different parameter choices, in a realistic range, were connected and the coefficients trained. Some improvement was found as compared to output averaging. The learning algorithm used thus far gives sub-optimal, but still useful results when the CO 2 level and other parameters are varied. Spatial structure remains to be studied. The first use of supermodeling with full climate models has been with variants of the ECHAM model that use different convection schemes. As yet the models are only connected at the ocean-atmosphere interface, where weighted combinations of fluxes from the two atmospheres are passed to a common ocean, and the weights adapted during a training period. The supermodel was surprisingly successful at avoiding unrealistic features such as the double-ITCZ (Intertropical Convergence Zone), a problem that arises in both of the two models run separately. The supermodels constructed thus far have not identified dynamical regime shifts in future climate. Thus the planned connection with the work of Tsonis on the relationship between regime shifts and synchronization/de-synchronization among the major climate modes (see U. Wisconsin report) has not yet been made. However the network analysis of the climate system, in observations and models, that was done in conjunction with that study, shows that models differ strongly from one another and from observations in regard to the dynamical structure described by correlation networks [Steinhaeuser and Tsonis 2013], providing a further justification for supermodeling. Toward a general software framework for supermodeling, three versions of CAM (the Community Atmosphere Model) at NCAR were configured for inter-model nudging using the DART (Data Assimilation Research Testbed) capability to stop and re-start models in synchrony. It was clearly established that the inter-model nudging adds almost no computational burden to the runs, but there appears to be a problem with the re-initialization software that is still being debugged. Publications: Several papers were published on the basic idea of the interactive multi-model (supermodel) including demonstrations with low-order ODEs. The last of these, a semi-philosophical review paper on the relevance of synchronization generally, encountered considerable resistance but was finally published in Entropy [Duane 2015]. A paper on the ECHAM/COSMOS supermodel, containing the most promising results so far [Shen et al. 2015] is presently under review.

58 GEOSCIENCES↗

The Deep Space Network

This report presents DSN progress in flight project support, tracking and data acquisition (TDA) research and technology, network engineering, hardware and software implementation, and operations. Each issue presents material in some, but not all, of the following categories in the order indicated. - Description of the DSN - Mission Support Ongoing Planetary/Interplanetary Flight Projects Advanced Flight Projects - Radio Science - Special Projects - Supporting Research and Technology Tracking and Ground-Based Navigation Communications--Spacecraft/Ground Station Control and Operations Technology Network Control and Data Processing - Network and Facility Engineering and Implementation Network Network Operations Control Center Ground Communications Deep Space Stations - Operations Network Operations Network Operations Control Center Ground Communications Deep Space Stations - Program Planning TDA Planning Quality Assurance In each issue, the part entitled "Description of the DSN" describes the functions and facilities of the DSN and may report the current configuration of one of the five DSN systems (Tracking, Telemetry, Command, Monitor & Control, and Test & Training). The work described in this report series is either performed or managed by the Tracking and Data Acquisition organization of JPL for NASA.

Tracking and Data Acquisition organization↗

Fuzzy/Neural Software Estimates Costs of Rocket-Engine Tests

The Highly Accurate Cost Estimating Model (HACEM) is a software system for estimating the costs of testing rocket engines and components at Stennis Space Center. HACEM is built on a foundation of adaptive-network-based fuzzy inference systems (ANFIS) a hybrid software concept that combines the adaptive capabilities of neural networks with the ease of development and additional benefits of fuzzy-logic-based systems. In ANFIS, fuzzy inference systems are trained by use of neural networks. HACEM includes selectable subsystems that utilize various numbers and types of inputs, various numbers of fuzzy membership functions, and various input-preprocessing techniques. The inputs to HACEM are parameters of specific tests or series of tests. These parameters include test type (component or engine test), number and duration of tests, and thrust level(s) (in the case of engine tests). The ANFIS in HACEM are trained by use of sets of these parameters, along with costs of past tests. Thereafter, the user feeds HACEM a simple input text file that contains the parameters of a planned test or series of tests, the user selects the desired HACEM subsystem, and the subsystem processes the parameters into an estimate of cost(s).

Douglas, Freddie↗

National plan to enhance aviation safety through human factors improvements

The purpose of this section of the plan is to establish a development and implementation strategy plan for improving safety and efficiency in the Air Traffic Control (ATC) system. These improvements will be achieved through the proper applications of human factors considerations to the present and future systems. The program will have four basic goals: (1) prepare for the future system through proper hiring and training; (2) develop a controller work station team concept (managing human errors); (3) understand and address the human factors implications of negative system results; and (4) define the proper division of responsibilities and interactions between the human and the machine in ATC systems. This plan addresses six program elements which together address the overall purpose. The six program elements are: (1) determine principles of human-centered automation that will enhance aviation safety and the efficiency of the air traffic controller; (2) provide new and/or enhanced methods and techniques to measure, assess, and improve human performance in the ATC environment; (3) determine system needs and methods for information transfer between and within controller teams and between controller teams and the cockpit; (4) determine how new controller work station technology can optimally be applied and integrated to enhance safety and efficiency; (5) assess training needs and develop improved techniques and strategies for selection, training, and evaluation of controllers; and (6) develop standards, methods, and procedures for the certification and validation of human engineering in the design, testing, and implementation of any hardware or software system element which affects information flow to or from the human.

Foushee, Clay↗

Supporting ARPA-E Power Grid Optimization (Final Report)

Pacific Northwest National Laboratory (PNNL), Arizona State University (ASU), Georgia Institute of Technology (Georgia Tech), Los Alamos National Laboratory (LANL), National Renewable Energy Laboratory (NREL), Texas A&M University (TAMU), The University of Texas at Austin (UT), and the University of Wisconsin-Madison (UW-M) supported the ARPA-E Grid Optimization (GO) Competition by providing a common problem formulation, data format, datasets, evaluation mechanism, scoring, rules, and results that resulted in the awarding of $\$9.24$ million dollars to teams from academia, industry, and national labs for solving three sets of increasingly difficult non-linear, security- constrained AC Optimal Powerflow (AC-OPF) optimization problems in order to increase the efficiency of the US Electric Grid. It is estimated that a 1% increase in efficiency can save $\$1$ billion. Current industry practices typically use a linear DC model (DC-OPF) in order solve the OPF problem within the time constraints of the operation schedule. The GO Competition challenges the best power engineers, mathematicians, and computer scientists to make possible operational decisions based on accurate physical models. To accomplish this, the GO Competition created a series of Challenges and funded teams to produce the best solver. Challenge 1 was to solve the security constrained Alternating Current Optimal Power Flow (ACOPF) problem. Challenge 2 extended that to by adding adjustable transformer tap ratios, phase shifting transformers, switchable shunts, price-responsive demand, ramp rate constrained generators and loads, and fast-start unit commitment (UC). Furthermore, Challenge 2 was a maximization problem while Challenge 1 was a minimization problem. While Challenge 3 was being developed, the entrants were invited to find better solutions to the Challenge 2 synthetic datasets with no restrictions on time, hardware, or algorithms. The Challenge 2 solutions turned out to be very good. Challenge 3 expanded the Challenge 2 problem further by using multiperiod dynamic markets, including advisory models for extreme weather events, day-ahead markets, and the real-time markets with an extended look-ahead. These problems included active bid-in demand and topology optimization. Together the Challenges used nearly 30 million CPU hours. Since each team was working on the same problem, using the same data, and running on the same hardware, fair comparisons could be drawn as to the best solver. The datasets were varied enough, however, that the best solver for one dataset was not necessarily the best at another, so cumulative scores were used. The process was managed by the PNNL maintained website https://GOCompetition.energy.gov, where Entrants could find information about the problem, the data, the rules, submit their solver for evaluation, and see the scores of all the competing teams on a Leaderboard. Interest was world-wide but only American teams were eligible for prizes. The Competition has produced 34 journal articles 115 papers and been cited over 500 times in the literature, including 12 dissertations (4 from foreign countries; Columbia (2), Germany, and Italy) and 3 from the DOE ExaScale project. Software developed by Pearl Street Technologies for Challenges 1 and 2 is now deployed by Southwest Power Pool (SPP) and Midcontinent Independent Service Operator (MISO). Other teams have received inquiries from venture capitalists. Google DeepMind has thanked the Competition for making the datasets developed for the Competition public. They are using it to train machine learning models. The larger datasets have billions of unknowns to be solved for, but only a small percent matter in the final solution. Knowing what unknowns are important can dramatically speedup the solution.

24 POWER TRANSMISSION AND DISTRIBUTION↗

Full Life-Cycle Defect Management Assessment: Initial Inspection Data Collection Results and Research Questions for Further Study

It is often the case in software projects that when schedule and budget resources are limited, the Verification and Validation (V&V) activities suffer. Fewer V&V activities can be afforded and moreover, short-term challenges can result in V&V activities being scaled back or dropped altogether. As a result, too often the default solution is to save activities for improving software quality until too late in the life-cycle, relying on late-term code inspections followed by thorough testing activities to reduce defect counts to acceptable levels. As many project managers realize, however, this is a resource-intensive way of achieving the required quality for software. The Full Life-cycle Defect Management Assessment Initiative, funded by NASA s Office of Safety and Mission Assurance under the Software Assurance Research Program, aims to address these problems by: Improving the effectiveness of early life-cycle V&V activities to make their benefits more attractive to team leads. Specifically, we focus on software inspection, a proven method that can be applied to any software work product, long before executable code has been developed; Better communicating this effectiveness to software development teams, along with suggestions for parameters to improve in the future to increase effectiveness; Analyzing the impact of early life-cycle V&V on the effectiveness and cost required for late life-cycle V&V activities, such as testing, in order to make the tradeoffs more apparent. This white paper reports on an initial milestone in this work, the development of a preliminary model of inspection effectiveness across multiple NASA Centers. This model contributes toward reaching our project goals by: Allowing an examination of inspection parameters, across different types of projects and different work products, for an analysis of factors that impact defect detection effectiveness. Allowing a comparison of this NASA-specific model to existing recommendations in the literature regarding how to plan effective inspections. Forming a baseline model which can be extended to incorporate factors describing: the numbers and types of defects that are missed by inspections; how such defects flow downstream through software development phases; how effectively they can be caught by testing activities in the late stages of development. The model has been implemented in a prototype web-enabled decision-support tool which allows developers to enter their inspection data and receive feedback based on a comparison against the model. The tool also allows users to access reusable materials (such as checklists) from projects included in the baseline. Both the tool itself and the model underlying it will continue to be extended throughout the remainder of this initiative. As results of analyzing inspection effectiveness for defect containment are determined, they can be shared via the tool and also via updates to existing training courses on metrics and software inspections. Moreover, the tool will help satisfy key CMMI requirements for the NASA Centers, as it will enable NASA to take a global view across peer review results for various types of projects to identify systemic problems. This analysis can result in continuous improvements to the approach to verification.

Shull, Forrest↗

Enabling Assurance in the MBSE Environment

A number of specific benefits that fit within the hallmarks of effective development are realized with implementation of model-based approaches to systems and assurance. Model Based Systems Engineering (MBSE) enabled by standardized modeling languages (e.g., SysML®) is at the core. These benefits in the context of spaceflight system challenges can include [1]: • Improved management of complex development • Reduced risk in the development process • Improved cost management • Improved design decisions With appropriate modeling techniques the assurance community also can improve early oversight and insight into project development. NASA has shown the basic constructs of SysML in an MBSE environment offer several key advantages, within a Model Based Mission Assurance (MBMA) initiative [2, 3]. These include the following: • Model viewpoints that promote rapid and systematic assessment of requirements coverage, hazard tagging and risk management • Embedded safety assessments for launch vehicles • Deployment of model assisted development of reliability products - Failure Modes and Effects Analyses (FMEAs) and Fault Trees • Test Planning • Validation and Verification of complex functions • Support of Assurance Case development for complex systems In addition, while there are benefits to be harvested, there is a realization that these do not come without effort and cost. Enabling model-based approaches requires structure, not only in an organizational context, but in a modeling context as well. There can be a steep learning curve and costs associated to train skilled modelers. But, on the other hand, not all of the assurance community need to be modelers. Models themselves must conform to ontologies that enable assurance. This places constraints upon the models and modelers. Optimums have yet to be developed where resources and constraints on modeling must be traded off in the organization and modeling efforts for projects. A number of barriers need to be overcome, as well, which pose challenges to the developers of the software that supports MBSE/MBMA. Information and data must be made to flow seamlessly through the life cycle. Because there is a wide variety of tools used in the community, to avoid the problems of the past of silos, delays, and diverging interests, information should flow among these tools to support the “single source of truth” paradigm of MBSE. This will greatly facilitate MBMA and advancement of assurance functions.

Evans, John W.↗

Electron Cloud Measurements in Fermilab Booster

Fermilab Booster synchrotron requires an intensity upgrade from 4.5x1012 to 6.5x1012 protons per pulse as a part of Fermilab's Proton Improvement Plan-II (PIP-II). One of the factors which may limit the high-intensity performance is the fast transverse instabilities caused by electron cloud effects. According to the experience in the Recycler, the electron cloud gradually builds up over multiple turns inside the combined function magnets and can reach final intensities orders of magnitude greater than in a pure dipole. Since the Booster synchrotron also incorporates combined function magnets, it is important to measure the presence of electron cloud. The presence or apparent absence of the electron cloud was investigated using two different methods: measuring bunch-by-bunch tune shift by changing the bunch train structure at different intensities and propagating a microwave carrier signal through the beampipe and analyzing the phase modulation of the signal. This paper presents the results of the two methods and corresponding simulation results conducted using PyECLOUD software.

43 PARTICLE ACCELERATORS↗

MRI-alone radiation therapy planning for prostate cancer: Automatic fiducial marker detection

Purpose: The feasibility of radiation therapy treatment planning using substitute computed tomography (sCT) generated from magnetic resonance images (MRIs) has been demonstrated by a number of research groups. One challenge with an MRI-alone workflow is the accurate identification of intraprostatic gold fiducial markers, which are frequently used for prostate localization prior to each dose delivery fraction. This paper investigates a template-matching approach for the detection of these seeds in MRI. Methods: Two different gradient echo T1 and T2* weighted MRI sequences were acquired from fifteen prostate cancer patients and evaluated for seed detection. For training, seed templates from manual contours were selected in a spectral clustering manifold learning framework. This aids in clustering “similar” gold fiducial markers together. The marker with the minimum distance to a cluster centroid was selected as the representative template of that cluster during training. During testing, Gaussian mixture modeling followed by a Markovian model was used in automatic detection of the probable candidates. The probable candidates were rigidly registered to the templates identified from spectral clustering, and a similarity metric is computed for ranking and detection. Results: A fiducial detection accuracy of 95% was obtained compared to manual observations. Expert radiation therapist observers were able to correctly identify all three implanted seeds on 11 of the 15 scans (the proposed method correctly identified all seeds on 10 of the 15). Conclusions: An novel automatic framework for gold fiducial marker detection in MRI is proposed and evaluated with detection accuracies comparable to manual detection. When radiation therapists are unable to determine the seed location in MRI, they refer back to the planning CT (only available in the existing clinical framework); similarly, an automatic quality control is built into the automatic software to ensure that all gold seeds are either correctly detected or a warning is raised for further manual intervention.

60 APPLIED LIFE SCIENCES↗

Earthbound applications for NASA's physician workstation

The dream of a space probe to Mars or an astronaut colony on the moon persists. Despite years of setbacks and delays, NASA continues to lay the foundation for a new frontier in space. The necessity of a self contained health maintenance facility is an integral part of this stellar venture. As a subsystem of this health maintenance facility, the physician or astronaut workstation was envisioned as the vehicle of interface between the computer resources of the space station and the care provider. Our efforts to define and build this interface have resulted in a series of programs which can now be tested and refined using earth-based applications. The modules which have dual-use application from the NASA workstation include: patient scheduling and master patient index, pharmacy, laboratory, medical library, problem list/progress notes, and digital medical records. Our current plan is to develop these tools as objects that can be assembled in a variety of configurations. This will allow the technology to be used by the private sector where each doctor can select the starting point of his outpatient office system and add modules as he makes progress in system integration and training.

NASA Discipline Number 70-30↗

Trades, Architecture, and Design of the Joint Augmented Reality Visual Informatics (Joint AR) Product

Future expeditions will enable exploration and study of the planetary surfaces of the Moon and Mars by performing extravehicular activity (EVA) operations. Present-day International Space Station (ISS) EVA operations require an intricate and tight choreography of crew, space suits, tools, systems, and flight teams to plan, train, and execute with limited advanced informatics. Additionally, EVA operations, aside from the Apollo Lunar surface missions, have predominately focused on maintenance and construction tasks where success criteria are clearly measurable. However, future exploration missions expect to enable crew to carry out scientific objectives in increasingly Earth-independent ways. In this paper, the Joint Augmented Reality Visual Informatics System (Joint AR) characterizes the design space for developing a modular augmented reality (AR) device for a spacesuit form factor that can support crew decision-making for EVA. This paper highlights the project’s experience with a product-focused management style and use-case centered systems engineering approach to iteratively design, build, and test. The Joint AR product features were defined via trade studies and market analysis of previous EVA display efforts, various AR components such as optics, commercial AR systems, light engines, data interfaces, graphics engine software and analog test beds. We outline the defining architectural design decisions, including safety criticality considerations, suit mounting interfaces, computer architectures, and partnership contracting mechanisms. The outcomes of these studies, architecture decisions, and management requirements result in a recommended design which is the Joint AR product. We discuss the evolution, development of these system components, and what work remains. We hope to share a unified understanding of various design decisions and how they impact the future of crew members’ access to data during Lunar and Martian EVAs. This ongoing effort can enable a community-wide discovery process toward realizing necessary AR features and capabilities for future missions.

Augmented Reality↗

Spacecraft Software Maintenance: An Effective Approach to Reducing Costs and Increasing Science Return

Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.

Shell, Elaine M.↗

NASA Goddard Space Flight Center

The NASA SLR Operational Center is responsible for: 1) NASA SLR network control, sustaining engineering, and logistics; 2) ILRS mission operations; and 3) ILRS and NASA SLR data operations. NASA SLR network control and sustaining engineering tasks include technical support, daily system performance monitoring, system scheduling, operator training, station status reporting, system relocation, logistics and support of the ILRS Networks and Engineering Working Group. These activities ensure the NASA SLR systems are meeting ILRS and NASA mission support requirements. ILRS mission operations tasks include mission planning, mission analysis, mission coordination, development of mission support plans, and support of the ILRS Missions Working Group. These activities ensure than new mission and campaign requirements are coordinated with the ILRS. Global Normal Points (NP) data, NASA SLR FullRate (FR) data, and satellite predictions are managed as part of data operations. Part of this operation includes supporting the ILRS Data Formats and Procedures Working Group. Global NP data operations consist of receipt, format and data integrity verification, archiving and merging. This activity culminates in the daily electronic transmission of NP files to the CDDIS. Currently of all these functions are automated. However, to ensure the timely and accurate flow of data, regular monitoring and maintenance of the operational software systems, computer systems and computer networking are performed. Tracking statistics between the stations and the data centers are compared periodically to eliminate lost data. Future activities in this area include sub-daily (i.e., hourly) NP data management, more stringent data integrity tests, and automatic station notification of format and data integrity issues.

Carter, David↗

Software Quality Assurance Metrics

Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.

McRae, Kalindra A.↗

Mars Reconnaissance Orbiter, Ground Data System, Receivables and Deliverables (REC/DELs)

This paper presents one JPL element manager's approach to describe a complex Ground Data System (GDS) with its receivables and deliverables (REC/DEL). The Mars Reconnaissance Orbiter (MRO) Ground Data System is the integrated set of ground software, hardware, facilities and networks that support mission operation. REC/DEL is a powerful tool for specifying hierarchy of commitments among systems and teams. Receivable of a system is a deliverable of another system. Focusing on tangible products enables the manager to objectively measure progress in a schedule. Jet Propulsion Laboratory mandates the use of REC/DEL for flight projects. Tutorial and training is provided for managers to create integrated REC/DEL database using automated systems. Project schedules are based on REC/DELs. This paper is not focusing on the mechanics of REC/DEL database creation, but it provides a guideline how one systematically creates categories of deliverables and receivables for ground data system components.

guidelines↗

Communication Research in Aviation and Space Operations: Symptoms and Strategies of Crew Coordination

The day-to-day operators of today's aerospace systems work under increasing pressures to accomplish more with less. They work in operational systems which are complex, technology-based, and high-risk; in which incidents and accidents have far-reaching and costly consequences. For these and other reasons, there is concern that the safety net formerly built upon redundant systems and abundant resources may become overburdened. Although we know that human ingenuity can overcome incredible odds, human nature can also fail in unpredictable ways. Over the last 20 years, a large percentage of aviation accidents and incidents have been attributed to human errors rather than hardware or environmental factors alone. A class of errors have been identified which are not due to a lack of individual, technical competencies. Rather, they are due to the failure of teams to utilize readily available resources or information in a timely fashion. These insights began a training revolution in the aviation industry called Cockpit Resource Management, which later became known as Crew Resource Management (CRM) as its concepts and applications extended to teams beyond the flightdeck. Then, as now, communication has been a cornerstone in CRM training since crew coordination and resource management largely resides within information transfer processes--both within flightcrews, and between flightcrews and the ground operations teams that support them. The research I will describe takes its roots in CRM history as we began to study communication processes in order to discover symptoms of crew coordination problems, as well as strategies of effective crew management. On the one hand, communication is often the means or the tool by which team members manage their resources, solve problems, maintain situational awareness and procedural discipline. Conversely, it is the lack of planning and resource management, loss of vigilance and situational awareness, and non-standard communications that are implicated in accidents and incidents. NASA/Ames Crew Factors researchers have been developing a model of effective crew coordination in order to understand the sources of performance breakdowns, and to develop effective solutions and interventions. Because communication is a primary mechanism by which information is received and transmitted, and because it is observable behavior, we focus on these group processes in order to identify patterns of communication that distinguish effective from less effective crew performance. Since a prime objective is to develop training recommendations for enhancing communication skills, we interpret our findings in the context of relevant task and environmental conditions, role and procedural constraints, and the normal real-time parameters of flight operations. Another research objective is to consider how communication and coordination can be enhanced through design. For example, flight deck and hardware design as well as procedural and software design may greatly influence the efficiency with which crews communicate and coordinate their work. In addition, teams and tasks may be designed, organized, and trained so that team interactions with each other are based upon appropriately shared knowledge, procedures and situation awareness. In short, we are interested in enhancing communication practices through (1) the training of specific communication skills, and (2) the design of equipment, tasks, procedures, and teams that optimize smooth, unambiguous communication processes. Two examples of communication research will be described; one in aviation and one in space operations. The first example is a high-fidelity full mission simulation study which investigates the affect of flightdeck automation on crew coordination and communication (contrasting crew performance in the DC-9 vs. MD88). Additional information is contained in the original extended abstract.

Kanki, Barbara G.↗

TRMM Re-Entry Planning: Attitude Determination and Control During Thruster Modes

The Tropical Rainfall Measuring Mission (TRMM) spacecraft has been undergoing design for a controlled re-entry to Earth. During simulation of the re-entry plan, there was evidence of errors in the attitude determination algorithms during thruster modes. These errors affected the bum efficiency, and thus planning, during re-entry. During thruster modes, the spacecraft attitude is controlled off of integrated Gyro Error Angles that were designed to closely follow the nominal spacecraft pointing frame (Tip Frame). These angles, however, were not exactly mapped to the Tip Frame from the Body Frame. Additionally, in the initial formulation of the thruster mode attitude determination algorithms, several assumptions and approximations were made to conserve processor speed. These errors became noticeable and significant when simulating bums of much longer duration (-10 times) than had been produced in flight. A solution is proposed that uses attitude determination information from a propagated extended Kalman filter that already exists in the TRMM thruster modes. This attitude information is then used to rotate the Gyro Error Angles into the Tip Frame. An error analysis is presented that compares the two formulations. The new algorithm is tested using the TRMM High-Fidelity Simulator and verified with the TRMM Software Testing and Training Facility. Simulation results for both configurations are also presented.

DeWeese, Keith↗

Evaluation of Portable Acceleration Solutions for LArTPC Simulation Using Wire-Cell Toolkit

The Liquid Argon Time Projection Chamber (LArTPC) technology plays an essential role in many current and future neutrino experiments. Accurate and fast simulation is critical to developing efficient analysis algorithms and precise physics model projections. The speed of simulation becomes more important as Deep Learning algorithms are getting more widely used in LArTPC analysis and their training requires a large simulated dataset. Heterogeneous computing is an efficient way to delegate computationally intensive tasks to specialized hardware. However, as the landscape of compute accelerators quickly evolves, it becomes increasingly difficult to manually adapt the code to the latest hardware or software environments. A solution which is portable to multiple hardware architectures without substantially compromising performance would thus be very beneficial, especially for long-term projects such as the LArTPC simulations. In search of a portable, scalable and maintainable software solution for LArTPC simulations, we have started to explore high-level portable programming frameworks that support several hardware backends. In this paper, we present our experience porting the LArTPC simulation code in the Wire-Cell Toolkit to NVIDIA GPUs, first with the CUDA programming model and then with a portable library called Kokkos. Preliminary performance results on NVIDIA V100 GPUs and multi-core CPUs are presented, followed by a discussion of the factors affiecting the performance and plans for future improvements.

Yu, Haiwang↗