SEARCH · Search NASA
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.
System indicates status of computers and controls operational modes. Two matrices are used - one relating to permissible system states, the other relating to requested system states. Concept is useful to designers of digital data transmission systems and time shared computer systems.
A handbook was developed to provide information and support to the spaceborne remote sensing and frequency management communities: to guide sensor developers in the choice of frequencies; to advise regulators on sensor technology needs and sharing potential; to present sharing analysis models and, through example, methods for determining sensor sharing feasibility; to introduce developers to the regulatory process; to create awareness of proper assignment procedures; to present sensor allocations; and to provide guidelines on the use and limitations of allocated bands. Controlling physical factors and user requirements and the regulatory environment are discussed. Sensor frequency allocation achievable performance and usefulness are reviewed. Procedures for national and international registration, the use of non-allocated bands and steps for obtaining new frequency allocations, and procedures for reporting interference are also discussed.
Efficiently maintaining and controlling a single schedule database in an Integrated Product Team environment is a significant challenge. It's accomplished effectively with the right combination of tools, skills, strategy, creativity, and teamwork. We'll share our lessons learned maintaining a 20,000 plus task network on a 36 month project.
The simple biochemistry of H2 is critical to a large number of microbial processes, affecting the interaction of organisms with each other and with the environment. The sensitivity of these many processes to H2 can be described quantitatively, at a basic thermodynamic level. This shared dependence on H2 may provide a means for interpreting the ecology and system-level biogeochemistry of widely variant microbial ecosystems on a common (and quantitative) level. Understanding the factors that control H2 itself is a critical prerequisite. Here, we examine two ecosystems that vary widely with respect to H2 cycling. In anoxic, 'organotrophic' sediments from Cape Lookout Bight (North Carolina, USA), H2 partial pressures are strictly maintained at low, steady-state levels by H2-consuming organisms, in a fashion that can be quantitatively predicted by simple thermodynamic calculations. In phototrophic microbial mats from Baja, Mexico, H2 partial pressures are instead controlled by the activity of light-sensitive H2-producing organisms. In consequence, H2 partial pressures within the system fluctuate by orders of magnitude on hour-long time scales. The differences in H2 cycling subsequently impact H2-sensitive microbial processes, such as methanogenesis. For example, the presence of sulfate in the organotrophic system always yielded low levels of H2 that were inhibitory to methanogenesis; however, the elevated levels of H2 in the phototrophic system favored methane production at significant levels, even in the presence of high sulfate concentrations. The myriad of other H2-sensitive microbial processes are expected to exhibit similar behavior.
The "Grid" is an emerging infrastructure for coordinating access across autonomous organizations to distributed, heterogeneous computation and data resources. Data grids are being built around the world as the next generation data handling systems for sharing, publishing, and preserving data residing on storage systems located in multiple administrative domains. A data grid provides logical namespaces for users, digital entities and storage resources to create persistent identifiers for controlling access, enabling discovery, and managing wide area latencies. This paper introduces data grids and describes data grid use cases. The relevance of data grids to digital libraries and persistent archives is demonstrated, and research issues in data grids and grid dataflow management systems are discussed.
Software safety analysis for a large software intensive system is always a challenge. Software safety practitioners need to ensure that software related hazards are completely identified, controlled, and tracked. This paper discusses in detail how to incorporate the traditional reliability techniques into the entire software safety analysis process. In addition, this paper addresses how information can be effectively shared between the various practitioners involved in the software safety analyses. The author has successfully applied the approach to several aerospace applications. Examples are provided to illustrate the key steps of the proposed approach.
The Galileo Probe, Pioneer-Venus probes, and SPRITE concept all share a number of common characteristics. They all follow a similar entry and descent sequence, using an aeroshell to protect against entry environments, and parachutes to aid in extrusion and descent speed control of the descent vehicle containing the science instruments. The descent vehicles all contained similar instruments (e.g. mass spectrometers and atmosphere structure sensors), and data was either relayed back to a carrier spacecraft (Galileo Probe, SPRITE) or transmitted direct to Earth (Pioneer-Venus). Based on these similar characteristics, NASA initiated a study to investigate a “common probe' that might be designed to perform similar science in a variety of planetary environments. This concept would leverage a common aeroshell design, and descent vehicle designs that could be made as similar as possible (the primary exception being that Venus will require a pressure vessel due to the extreme pressures and temperatures seen in the lower portion of the descent). To support the Common Probe study, GSFC and JPL performed a series of interplanetary trajectory analyses to help develop the mission designs for Venus, Jupiter, Saturn, Uranus, and Neptune. Primary considerations in the trajectory modeling included: a maximum of 12-year time of flight (for outer planet destinations), generation of both steep and shallow entry trajectories to each destination (where steep and shallow resulted in approximately 150 g and 50 g peak deceleration during entry at each location), and consideration of the data relay. Gravity assists and trajectories with low delta-V requirements (typically much less than 500 m/s) were also incorporated into the design process to enable launch on existing vehicles such as the Atlas V.
Synchrophasor technology is widely deployed in the energy management system to monitor the grid health at micro level and perform necessary corrective actions in real time; however, integrated phasor devices and data aggregators are exposed to several cybersecurity threats. This paper proposes a federated ML(FML)-based ADS to detect several data integrity attacks in the synchrophasor network. The proposed approach integrates the horizontal FML technique and consists of substation-based local models and a control center-based global model. The proposed methodology includes training local models using heterogeneous data sets that include network and grid information and updating the global model through multiple iterations by sharing model gradients. Finally, the trained global model is applied to identify cyberattacks, normal operation, and physical events. To validate the proof of concept, we used synthetic data sets generated by Mississippi State University and Oak Ridge National Laboratory for training and testing the classification models using the National Renewable Energy Laboratory's high performance computing resources. Our experimental results, computed through several performance measures, reveal that the proposed approach shows consistent performance during the binary, three-class, and multiclass classifications while ensuring privacy of synchrophasor data.
CG-Kit is a new Code Generation tool-Kit that we have developed as a part of the solution for portability and maintainability for multiphysics computing applications. The development of CG-Kit is rooted in the urgent need created by the shifting landscape of high-performance computing platforms and the algorithmic complexities of a particular large-scale multiphysics application: Flash-X. To efficiently use computing resources on a heterogeneous node, an application must have a map of computation to resources and a mechanism to move the data and computation to the resources according to the map. Most existing performance portability solutions are focussed on abstracting the expression of computations so that a unified source code can be specialized to run on different resources. However, such an approach is insufficient for a code like Flash-X, which has a multitude of code components that can be assembled in various permutations and combinations to form different instances of applications. Similar challenges apply to any code that has composability, where a single specified way of apportioning work among devices may not be optimal. Additionally, use cases arise where the optimal control flow of computation may differ for different devices while the underlying numerics remain identical. This combination leads to unique challenges including handling an existing large code base in Fortran and/or C/C++, subdivision of code into a great variety of units supporting a wide range of physics and numerical methods, different parallelization techniques for distributed and shared memory systems and accelerator devices, and heterogeneity of computing platforms requiring coexisting variants of parallel algorithms. All of these challenges demand that scientific software developers apply existing knowledge about domain applications, algorithms, and computing platforms to determine custom abstractions and granularity for code generation. There is a critical lack of tools to tackle those problems. CG-Kit is designed to fill this gap by providing a user with the ability to express their desired control flow and computation-to-resource map in the form a pseudocode-like recipe. It consists of standalone tools that can be combined into highly specific and, we argue, highly effective portability and maintainability toolchains. Here we present the design of our new tools: parametrized source trees, control flow graphs, and recipes. The tools are implemented in Python. They are agnostic to the programming language of the source code targeted for code generation. In conclusion, we demonstrate the capabilities of the toolkit with two examples, first, multithreaded variants of the basic AXPY operation, and second, variants of parallel algorithms within a hydrodynamics solver, called Spark, from Flash-X that operates on block-structured adaptive meshes.
The challenging range of landing sites for which the Mars Science Laboratory Rover was designed, requires a rover thermal management system that is capable of keeping temperatures controlled across a wide variety of environmental conditions. On the Martian surface where temperatures can be as cold as -123 C and as warm as 38 C, the rover relies upon a Mechanically Pumped Fluid Loop (MPFL) Rover Heat Rejection System (RHRS) and external radiators to maintain the temperature of sensitive electronics and science instruments within a -40 C to 50 C range. The RHRS harnesses some of the waste heat generated from the rover power source, known as the Multi Mission Radioisotope Thermoelectric Generator (MMRTG), for use as survival heat for the rover during cold conditions. The MMRTG produces 110 W of electrical power while generating waste heat equivalent to approximately 2000 W. Heat exchanger plates (hot plates) positioned close to the MMRTG pick up this survival heat from it by radiative heat transfer. Winds on Mars can be as fast as 15 m/s for extended periods. They can lead to significant heat loss from the MMRTG and the hot plates due to convective heat pick up from these surfaces. Estimation of this convective heat loss cannot be accurately and adequately achieved by simple textbook based calculations because of the very complicated flow fields around these surfaces, which are a function of wind direction and speed. Accurate calculations necessitated the employment of sophisticated Computational Fluid Dynamics (CFD) computer codes. This paper describes the methodology and results of these CFD calculations. Additionally, these results are compared to simple textbook based calculations that served as benchmarks and sanity checks for them. And finally, the overall RHRS system performance predictions will be shared to show how these results affected the overall rover thermal performance.
GlideinWMS is a workload manager provisioning resources for many experiments including CMS and DUNE. The software is distributed both as native packages and specialized production containers. Following an approach used in other communities like web development we built our workspaces, system-like containers to ease development and testing. Developers can change the source tree or check out a different branch and quickly reconfigure the services to see the effect of their changes. In this paper, we’ll talk about what differentiates workspaces from other containers. We’ll describe our base system composed of three containers. A one-node cluster including a compute element and a batch system. A GlideinWMS Factory controlling pilot jobs. And a scheduler and Frontend, to submit jobs and provision resources. Additional containers can be used for optional components. This system can easily run on a laptop and we’ll share our evaluation of different container runtimes, with an eye for ease of use and performance. Finally, we’ll talk about our experience as developers and with students. The GlideinWMS workspaces are easily integrated with IDEs like VS Code, simplifying debugging and allowing development and testing of the system also when offline. They simplified the training and onboarding of new team members and Summer interns. And they were useful in workshops where students could have first-hand experience with the mechanisms and components that, in production, run millions of jobs.
The Open Charge Point Interface (OCPI) is an open protocol that enables electric vehicle (EV) charging systems to work together across networks. It supports communication and data sharing between Charge Point Operators (CPOs), who manage charging stations, and e-Mobility Service Providers (eMSPs), who provide charging services to EV drivers. OCPI facilitates functions like user authorization, remote charge point control, charging session data exchange, and billing through Charge Detail Records (CDRs). This allows EV roaming, so drivers can charge at different networks without multiple accounts. As the EV market grows due to increased adoption and technological advancements, OCPI faces higher demands. This has revealed issues with CDR format consistency, timestamp standardization across regions, transmission of EV-side error codes for troubleshooting, and support for new use cases. These challenges can affect operations and user experience, particularly as the industry starts considering Vehicle-to-Grid (V2G) systems, where EVs supply energy to the grid, and Vehicle-to-Everything (V2X) technologies for broader energy interactions. Using feedback from the ChargeX Diagnostics taskforce discussions, industry 1-on-1 meetings, technical standards, and OCPI’s evolution through versions (e.g., OCPI 2.1.1, 2.2, and 2.2.1), this report identifies these issues and suggests practical recommendations. These aim to improve interoperability, streamline operations, and prepare OCPI for future trends in the EV charging ecosystem.
GlideinWMS is a workload manager provisioning resources for many experiments, including CMS and DUNE. The software is distributed both as native packages and specialized production containers. Following an approach used in other communities like web development, we built our workspaces, system-like containers to ease development and testing. Developers can change the source tree or check out a different branch and quickly reconfigure the services to see the effect of their changes. In this paper, we will talk about what differentiates workspaces from other containers. We will describe our base system, composed of three containers: a one-node cluster including a compute element and a batch system, a GlideinWMS Factory controlling pilot jobs, and a scheduler and Frontend to submit jobs and provision resources. Additional containers can be used for optional components. This system can easily run on a laptop, and we will share our evaluation of different container runtimes, with an eye for ease of use and performance. Finally, we will talk about our experience as developers and with students. The GlideinWMS workspaces are easily integrated with IDEs like VS Code, simplifying debugging and allowing development and testing of the system even when offline. They simplified the training and onboarding of new team members and summer interns. And they were useful in workshops where students could have first-hand experience with the mechanisms and components that, in production, run millions of jobs.
This paper presents the design of derived virtual devices (DVDs). DVDs are the mechanism used by the Netstation Project to provide secure shared access to network-attached peripherals distributed in an untrusted network environment. DVDs improve Input/Output efficiency by allowing user processes to perform I/O operations directly from devices without intermediate transfer through the controlling operating system kernel. The security enforced at the device through the DVD mechanism includes resource boundary checking, user authentication, and restricted operations, e.g., read-only access. To illustrate the application of DVDs, we present the interactions between a network-attached disk and a file system designed to exploit the DVD abstraction. We further discuss third-party transfer as a mechanism intended to provide for efficient data transfer in a typical NAP environment. We show how DVDs facilitate third-party transfer, and provide the security required in a more open network environment.
Under an Army Small Business Innovation Research (SBIR) grant, Symbiotics, Inc. developed a software system that permits users to upgrade products from standalone applications so they can communicate in a distributed computing environment. Under a subsequent NASA SBIR grant, Symbiotics added additional tools to the SOCIAL product to enable NASA to coordinate conventional systems for planning Shuttle launch support operations. Using SOCIAL, data may be shared among applications in a computer network even when the applications are written in different programming languages. The product was introduced to the commercial market in 1993 and is used to monitor and control equipment for operation support and to integrate financial networks. The SBIR program was established to increase small business participation in federal R&D activities and to transfer government research to industry. InQuisiX is a reuse library providing high performance classification, cataloging, searching, browsing, retrieval and synthesis capabilities. These form the foundation for software reuse, producing higher quality software at lower cost and in less time. Software Productivity Solutions, Inc. developed the technology under Small Business Innovation Research (SBIR) projects funded by NASA and the Army and is marketing InQuisiX in conjunction with Science Applications International Corporation (SAIC). The SBIR program was established to increase small business participation in federal R&D activities and to transfer government research to industry.
It is widely held that identifiable 'convective regimes' exist in nature, although precise definitions of these are elusive. Examples include land / Ocean distinctions, break / monsoon beahvior, seasonal differences in the Amazon (SON vs DJF), etc. These regimes are often described by differences in the realized local convective spectra, and measured by various metrics of convective intensity, depth, areal coverage and rainfall amount. Objective regime identification may be valuable in several ways: regimes may serve as natural 'branch points' in satellite retrieval algorithms or data assimilation efforts; one example might be objective identification of regions that 'should' share a similar 2-R relationship. Similarly, objectively defined regimes may provide guidance on optimal siting of ground validation efforts. Objectively defined regimes could also serve as natural (rather than arbitrary geographic) domain 'controls' in studies of convective response to environmental forcing. Quantification of convective vertical structure has traditionally involved parametric study of prescribed quantities thought to be important to convective dynamics: maximum radar reflectivity, cloud top height, 30-35 dBZ echo top height, rain rate, etc. Individually, these parameters are somewhat deficient as their interpretation is often nonunique (the same metric value may signify different physics in different storm realizations). Individual metrics also fail to capture the coherence and interrelationships between vertical levels available in full 3-D radar datasets. An alternative approach is discovery of natural partitions of vertical structure in a globally representative dataset, or 'archetypal' reflectivity profiles. In this study, this is accomplished through cluster analysis of a very large sample (0[107) of TRMM-PR reflectivity columns. Once achieved, the rainconditional and unconditional 'mix' of archetypal profile types in a given location and/or season provides a description of the local convective spectrum which retains vertical structure information. A further cluster analysis of these 'mixes' can identify recurrent convective spectra. These are a first step towards objective identification of convective regimes, and towards answering the question: 'What are the most convectively similar locations in the world?'
System safety analysis techniques are well established and are used extensively during the design of safety-critical systems. Despite this, most of the techniques are highly subjective and dependent on the skill of the practitioner. Since these analyses are usually based on an informal system model, it is unlikely that they will be complete, consistent, and error free. In fact, the lack of precise models of the system architecture and its failure modes often forces the safety analysts to devote much of their effort to gathering architectural details about the system behavior from several sources and embedding this information in the safety artifacts such as the fault trees. This report describes Model-Based Safety Analysis, an approach in which the system and safety engineers share a common system model created using a model-based development process. By extending the system model with a fault model as well as relevant portions of the physical system to be controlled, automated support can be provided for much of the safety analysis. We believe that by using a common model for both system and safety engineering and automating parts of the safety analysis, we can both reduce the cost and improve the quality of the safety analysis. Here we present our vision of model-based safety analysis and discuss the advantages and challenges in making this approach practical.
A blackboard system consists of a set of knowledge sources, a blackboard data structure, and a control strategy used to activate the knowledge sources. The blackboard model of problem solving is best described by Dr. H. Penny Nii of the Stanford University AI Laboratory: "A Blackboard System can be viewed as a collection of intelligent agents who are gathered around a blackboard, looking at pieces of information written on it, thinking about the current state of the solution, and writing their conclusions on the blackboard as they generate them. " The blackboard is a centralized global data structure, often partitioned in a hierarchical manner, used to represent the problem domain. The blackboard is also used to allow inter-knowledge source communication and acts as a shared memory visible to all of the knowledge sources. A knowledge source is a highly specialized, highly independent process that takes inputs from the blackboard data structure, performs a computation, and places the results of the computation in the blackboard data structure. This design allows for an opportunistic control strategy. The opportunistic problem-solving technique allows a knowledge source to contribute towards the solution of the current problem without knowing which of the other knowledge sources will use the information. The use of opportunistic problem-solving allows the data transfers on the blackboard to determine which processes are active at a given time. Designing and developing blackboard systems is a difficult process. The designer is trying to balance several conflicting goals and achieve a high degree of concurrent knowledge source execution while maintaining both knowledge and semantic consistency on the blackboard. Blackboard systems have not attained their apparent potential because there are no established tools or methods to guide in their construction or analyze their performance.