SEARCH · Engineering Papers
Results for “GDS”
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.
Comparing Circuit Connectivity Between All-Metal GDS Layouts.
Abstract not provided.
Comparing Circuit Connectivity Between All-Metal GDS Layouts.
Abstract not provided.
Renaissance architecture for Ground Data Systems
The Mission Operations and Data Systems Directorate (MO&DSD) has embarked on a new approach for developing and operating Ground Data Systems (GDS) for flight mission support. This approach is driven by the goals of minimizing cost and maximizing customer satisfaction. Achievement of these goals is realized through the use of a standard set of capabilities which can be modified to meet specific user needs. This approach, which is called the Renaissance architecture, stresses the engineering of integrated systems, based upon workstation/local area network (LAN)/fileserver technology and reusable hardware and software components called 'building blocks.' These building blocks are integrated with mission specific capabilities to build the GDS for each individual mission. The building block approach is key to the reduction of development costs and schedules. Also, the Renaissance approach allows the integration of GDS functions that were previously provided via separate multi-mission facilities. With the Renaissance architecture, the GDS can be developed by the MO&DSD or all, or part, of the GDS can be operated by the user at their facility. Flexibility in operation configuration allows both selection of a cost-effective operations approach and the capability for customizing operations to user needs. Thus the focus of the MO&DSD is shifted from operating systems that we have built to building systems and, optionally, operations as separate services. Renaissance is actually a continuous process. Both the building blocks and the system architecture will evolve as user needs and technology change. Providing GDS on a per user basis enables this continuous refinement of the development process and product and allows the MO&DSD to remain a customer-focused organization. This paper will present the activities and results of the MO&DSD initial efforts toward the establishment of the Renaissance approach for the development of GDS, with a particular focus on both the technical and process implications posed by Renaissance to the MO&DSD.
Joint Test Plan for Gas Dynamic Spray Technology Demonstration
Air Force Space Command (AFSPC) and NASA have similar missions, facilities, and structures located in similar harsh environments. Both are responsible for a number of facilities/structures with metallic structural and non-structural components in highly and moderately corrosive environments. Regardless of the corrosivity of the environment, all metals require periodic maintenance activity to guard against the insidious effects of corrosion and thus ensure that structures meet or exceed design or performance life. The standard practice for protecting metallic substrates in atmospheric environments is the use of an applied coating system. Current coating systems used across AFSPC and NASA contain volatile organic compounds (VOCs) and hazardous air pollutants (HAPs). These coatings are subject to environmental regulations at the Federal and State levels that limit their usage. In addition, these coatings often cannot withstand the high temperatures and exhaust that may be experienced by AFSPC and NASA structures. In response to these concerns, AFSPC and NASA have approved the use of thermal spray coatings (TSCs). Thermal spray coatings are extremely durable and environmentally friendly coating alternatives, but utilize large cumbersome equipment for application that make the coatings difficult and time consuming to repair. Other concerns include difficulties coating complex geometries and the cost of equipment, training, and materials. Gas Dynamic Spray (GDS) technology (also known as Cold Spray) will be evaluated as a smaller, more maneuverable repair method as well as for areas where thermal spray techniques are not as effective. The technology can result in reduced maintenance and thus reduced hazardous materials/wastes associated with current processes. Thermal spray and GDS coatings also have no VOCs and are environmentally preferable coatings. To achieve a condition suitable for the application of a coating system, including GDS coatings, the substrate must undergo some type of surface preparation and/or depainting operation to ensure adhesion of the new coating system. The GDS unit selected for demonstration has a powder feeding system that can be used for surface preparation or coating application. The surface preparation feature will also be examined. The primary objective of this effort is to demonstrate GDS technology as a repair method for TSCs. The project will also determine the optimal GDS coating thickness for acceptable performance. Successful completion of this project will result in approval of GDS technology as a repair method for TSCs at AFSPC and NASA installations and will improve corrosion protection at critical systems, facilitate easier maintenance activity, extend maintenance cycles, eliminate flight hardware contamination, and reduce the amount of hazardous waste generated.
The Mars 2020 Ground Data System Architecture
The Mars 2020 Mission’s primary objective is to collect 20 geographically unique samples during its prime mission of one and a quarter Martian years, or just over 2 Earth years. Mission planners determined the project needed to develop a system that would enable the operations team to analyze engineering and science data, make science decisions, select viable rover targets at a millimeter resolution and validate an uplink bundle for a car sized rover with more complex science instruments than any previous Mars surface mission. All this had to be done within a five hour time frame. Doing this with a small team would be a challenge, but this had to be accomplished by a large team of engineers and scientists located across North America and Europe. Achieving this level of operational efficiency was unheard of in the prime mission. In addition, the mission had another set of requirements that had nothing to do with surface operations; the Mars 2020 Ground Data System (GDS) was also expected to comply with a new set of security requirements to keep up with the ever changing cybersecurity landscape. The Mars 2020 Ground Data System (GDS) is a re-architected version of the Mars Science Laboratory GDS. The primary goal was to integrate the lessons learned from previous Mars surface missions, accommodate a set of new requirements and capabilities required to ensure mission success, and comply with a new set of cybersecurity controls. The new architecture includes several unique qualities including a data lake, language-agnostic system-wide event-based operations, containerization, automated deployment, network segmentation, infrastructure-as-code, API-driven interfaces, and the first Mars surface GDS to operate primarily in the cloud. The new architecture enabled greater access to the system’s data, tighter integration with the operations team, and a higher level of traceability. The availability of the data also enabled a new set of capabilities previously not possible on surface missions. These new capabilities include an autonomous data to information, pipeline for downlink analysis, horizontal scaling of science data processing capabilities, autonomous round trip data tracking of science and engineering data, integration of flight system state into the tactical planning cycle, high fidelity targeting utilizing kinematic data, and hierarchical image and 3d meshes data representations. This paper will introduce the requirements for the Mars 2020 Mission, the heritage architecture, and the rationale for the changes to achieve the new architecture. The paper will continue to describe the fundamental changes made to the GDS architecture, how these changes enabled a more tightly integrated GDS, and the new capabilities that were enabled by the new architecture. The paper will conclude with the lessons learned from the process of rearchitecting a heritage GDS system and from the first 200 days of operations supporting over 800 users from around the world.
GPU Direct I/O with HDF5
Exascale HPC systems are being designed with accelerators, such as GPUs, to accelerate parts of applications. In machine learning workloads as well as large-scale simulations that use GPUs as accelerators, the CPU (or host) memory is currently used as a buffer for data transfers between GPU (or device) memory and the file system. If the CPU does not need to operate on the data, then this is sub-optimal because it wastes host memory by reserving space for duplicated data. Furthermore, this “bounce buffer” approach wastes CPU cycles spent on transferring data. A new technique, NVIDIA GPUDirect Storage (GDS), can eliminate the need to use the host memory as a bounce buffer. Thereby, it becomes possible to transfer data directly between the device memory and the file system. This direct data path shortens latency by omitting the extra copy and enables higher-bandwidth. To take full advantage of GDS in existing applications, it is necessary to provide support with existing I/O libraries, such as HDF5 and MPI-IO, which are heavily used in applications. In this paper, we describe our effort of integrating GDS with HDF5, the top I/O library at NERSC and at DOE leadership computing facilities. We design and implement this integration using a HDF5 Virtual File Driver (VFD). The GDS VFD provides a file system abstraction to the application that allows HDF5 applications to perform I/O without the need to move data between CPUs and GPUs explicitly. We compare performance of the HDF5 GDS VFD with explicit data movement approaches and demonstrate superior performance with the GDS method.
Cost-Effective Telemetry and Command Ground Systems Automation Strategy for the Soil Moisture Active Passive (SMAP) Mission
Soil Moisture Active Passive (SMAP) is an Earth-orbiting, remote-sensing NASA mission slated for launch in 2014. The ground data system (GDS) being developed for SMAP is composed of many heterogeneous subsystems, ranging from those that support planning and sequencing to those used for real-time operations, and even further to those that enable science data exchange. A full end-to-end automation of the GDS may result in cost savings during mission operations, but it would require a significant upfront investment to develop such a comprehensive automation. As demonstrated by the Jason-1 and Wide-field Infrared Survey Explorer (WISE) missions, a measure of "lights-out" automation for routine, orbital pass, ground operations can still reduce mission costs through smaller staffing of operators and limiting their working hours. The challenge, then, for the SMAP GDS engineering team, is to formulate an automated operations strategy--and corresponding system architecture -- to minimize operator intervention during routine operations, while balancing the development costs associated with the scope and complexity of automation. This paper discusses the automated operations approach being developed for the SMAP GDS. The focus is on automating the activities involved in routine passes, which limits the scope to real-time operations. A key subsystem of the SMAP GDS -- NASA's AMMOS Mission Data Processing and Control System (AMPCS) -- provides a set of capabilities that enable such automation. Also discussed are the lights-out pass automations of the Jason-1 and WISE missions and how they informed the automation strategy for SMAP. The paper aims to provide insights into what is necessary in automating the GDS operations for Earth satellite missions.
Cost-Effective Telemetry and Command Ground Systems Automation Strategy for the Soil Moisture Active Passive (SMAP) Mission
Soil Moisture Active Passive (SMAP) is an Earth-orbiting, remote-sensing NASA mission slated for launch in 2014.[double dagger] The ground data system (GDS) being developed for SMAP is composed of many heterogeneous subsystems, ranging from those that support planning and sequencing to those used for real-time operations, and even further to those that enable science data exchange. A full end-to-end automation of the GDS may result in cost savings during mission operations, but it would require a significant upfront investment to develop such comprehensive automation. As demonstrated by the Jason-1 and Wide-field Infrared Survey Explorer (WISE) missions, a measure of "lights-out" automation for routine, orbital pass ground operations can still reduce mission cost through smaller staffing of operators and limited work hours. The challenge, then, for the SMAP GDS engineering team is to formulate an automated operations strategy--and corresponding system architecture--to minimize operator intervention during operations, while balancing the development cost associated with the scope and complexity of automation. This paper discusses the automated operations approach being developed for the SMAP GDS. The focus is on automating the activities involved in routine passes, which limits the scope to real-time operations. A key subsystem of the SMAP GDS--NASA's AMMOS Mission Data Processing and Control System (AMPCS)--provides a set of capabilities that enable such automation. Also discussed are the lights-out pass automations of the Jason-1 and WISE missions and how they informed the automation strategy for SMAP. The paper aims to provide insights into what is necessary in automating the GDS operations for Earth satellite missions.
Real-Time Coupling of Geographically Distributed Research Infrastructures: Taxonomy, Overview, and Real-World Smart Grid Applications
Novel concepts enabling a resilient future power system and their subsequent experimental evaluation are experiencing a steadily growing challenge: large scale complexity and questionable scalability. The requirements on a research infrastructure (RI) to cope with the trends of such a dynamic system therefore grow in size, diversity and costs, making the feasibility of rigorous advancements questionable by a single RI. Analysis of large scale system complexity has been made possible by the real-time coupling of geographically separated RIs undertaking geographically distributed simulations (GDS), the concept of which brings the equipment, models and expertise of independent RIs, in combination, to optimally address the challenge. This article presents the outputs of IEEE PES Task Force on Interfacing Techniques for Simulation Tools towards standardization of GDS as a concept. First, the taxonomy for setups utilized for GDS is established followed by a comprehensive overview of the advancements in real-time couplings reported in literature. The overview encompasses fundamental technological design considerations for GDS. The article further presents four application oriented case studies (real-world implementations) where GDS setups have been utilized, demonstrating their practicality and potential in enabling the analysis of future complex power systems.
Moving Away from Ones and Zeros, Designing a Ground Data System Based on Higher Levels of Abstraction
Previous JPL ground systems have been designed with the Ground Data System (GDS) engineer in mind. The focus on these systems has been on packaging and delivery of low level information (frames, packets, telemetry values) to the end user. It was not that long ago when project teams would be huddled over a workstation, examining crude displays of telemetry bits organized in various ways, trying to determine the status of a spacecraft. Understanding the data often required additional levels of GDS expertise, or worse, transformation of the raw data into alternative formats followed by ingestion into other tools so that the data became meaningful. The primary focus was often to answer these types of questions: "Why did this particular frame fail Reed-Solomon decode? Why did this packet get marked as invalid? Why am I missing a block of telemetry from my query?" -- which are completely valid questions to ask from a GDS Engineer's point of view, and large families of tools have been designed to help answer these questions. But these are not the questions that most users care about - which are more like: "Why is the battery state of charge trending down? Show me a summary image report for the last traverse to the target. Show me a data accountability summary for the last DSN pass." Answers to these questions, which are what users are looking for, requires a higher level of abstraction and supporting tools than mining through ones and zeros. JPL has created a next generation capability called the Mission Data Processing and Control System (MPCS) which is designed to support this higher level of abstraction by providing customizable views of the ground system combining collections of lower level information into more meaningful ways. Instead of examining frames, packets, and individual telemetry data points -- MPCS is capable of providing comprehensive summary reports, product status, overall flight/ground event status, as well as payload health summaries. Based on these higher level views, end users can make tactical or strategic decisions, or drop into detailed analysis as needed. System designers need to continue building systems that support low level GDS troubleshooting - but the basic design of a GDS should be geared towards what end users actually need to see. This paper will describe the capabilities of MPCS that directly support these higher levels of abstraction, and which are being used today in missions such as the Mars Science Laboratory and other NASA missions.
Toward More Realistic Simulation and Prediction of Dust Storms on Mars
Major (regional and global)dust storms dominate weather and climate variability on present-day Mars. Absorption and scattering of visible and IR radiation by dust strongly affect the thermal state of the thin Mars atmosphere, while dust provides condensation nuclei for water and CO2 cloud particles, which also affect radiative fluxes. Global dust storms (GDS) occur ~three times per Mars decade and to date have been observed in only northern fall and winter,when the global circulation is strongest. Tenfold increases in column dust opacity are typical during GDS, with intense vertical motions transporting dust to far higher altitudes than usual. The key processes and feedbacks that produce GDS remain poorly understood, hence current atmospheric models fail to self-consistently simulate observed dust storm activity. This means we have no predictive capability for when GDS may occur, either now or in Mars’s past. And crucially, due to the huge impact of GDS on the atmosphere and surface, our lack of ability to simulate realistic dust storms has major implications for Mars science and exploration: from understanding the present climate (§2.1),to modeling past climates and water cycles (§2.2), to exploring how wind, water, and dust cycles varied over time to interpret geology and assess potential habitability(§2.3), to quantifying and mitigating risks posed to Mars missions (§2.4)
From Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge
The Dawn GDS Team met the SC Sim integration challenge in eight months. The GDS System Engineering approach in response to the SC Simintegration challenge, focused on a set of key practices: decomposition of project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; risk management thru management of expectations; and aggregation of intermediate products into a final product. By maintaining a a system-level focus, the overall systems engineering process unified team GDS Team members with a common goal: the success of the ground system as a whole and not just the success of their individual expert contributions. Incorporation of Agile-type development efforts were aligned with a risk strategy based on team-oriented principles and expectations management, thus achieving a more stable baseline solution without compromising the integrity of the GDS design.
Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange
The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.
The Interim: Until You Achieve an Operationally Responsive Ground System
Everyone wants to achieve a 'Responsive' Ground Data System (GDS), but that takes time. What do you do in the interim? Our group, called the Integration, Test and Deployment Team (ITD), is a group of responsive engineers whose primary focus is to assist JPL projects to successfully adapt, test, integrate and deploy their ground data system. The team configures and adapts the GDS for a project, so that analysts, engineers and scientist do not need to be experts in the GDS to operate it. The team has developed a human interface to accommodate all types of users. It provides Graphical User Interfaces (GUI's) for those that want GUI's, command line interfaces for those that want control, and selection button interfaces for other users. The cornerstone of a responsive Ground Data System is responsive people. Without individuals who can be aware of a project's changing needs and requirements, how can the GDS become responsive?.
The Interim : until you achieve an operationally responsive ground system
Everyone wants to achieve a 'Responsive' Ground Data System (GDS), but that takes time. What do you do in the interim? Our group, called the Integration, Test and Deployment Team (ITD), is a group of responsive engineers whose primary focus is to assist JPL projects to successfully adapt, test, integrate and deploy their ground data system. The team configures and adapts the GDS for a project, so that analysts, engineers and scientist do not need to be experts in the GDS to operate it. The team has developed a human interface to accommodate all types of users. It provides Graphical User Interfaces (GUI's) for those that want GUI's, command line interfaces for those that want control, and selection button interfaces for other users. The cornerstone of a responsive Ground Data System is responsive people. Without individuals who can be aware of a project's changing needs and requirements, how can the GDS become responsive
Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge
The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.
Optimizing fused silica debris shield use in the National Ignition Facility
The National Ignition Facility (NIF) deliberately and routinely operates with its final optics exposed to fluences likely to induce and grow damage. This choice has enabled the NIF to operate at energies previously unachievable at the expense of limitations to delivered power and energy contingent on the ability to repair damage on the final optics. Prior to the introduction of the fused silica debris shield (FSDS), the grating debris shield (GDS) was the optic type on the NIF most prone to damage and hence a primary limiter to the delivered energy. The introduction of the FSDS has reduced the damage initiation rate on the GDS by about two orders of magnitude to date. Despite the FSDS being a disposable optic, it is important to understand how the FSDS damages and when its damage requires it to be exchanged to maximize the FSDS lifetime while still protecting the GDS from damage. We will define the FSDS exchange criteria and evaluate the damage initiation mechanisms of the FSDS. The surface damage morphologies provide insight into the impact of the various damage mechanisms that limit the FSDS lifetime. These results are utilized in our analysis to optimize the FSDS exchange criteria to further extend the GDS lifetime.