SEARCH · Search NASA
Results for “Applicability”
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.
Testing and Application of Commercial Thermodynamics Software for Solid-Gas Equilibria in Planetary Science Applications
The ability to calculate chemical equilibria from thermochemical constants (e.g., H, S, Cp) or other experimental data is a tool widely employed by scientists. However, phase equilibria for planetary science problems is limited by easy access to libraries of thermochemical data, as well as the software to invert that data. Many academic software packages are focused on specific types of problems (e.g., aqueous solutions or melting and crystallization of magmas). This focus makes them excellent tools for specific uses, but poorer tools for other scenarios, especially those involving elements or chemical species that are less well-studied in that specific scientific field (e.g. NaCl vapor). Amongst the more general thermodynamic software tools, there are closed academic software packages, open-source options, as well as commercial software. We have explored the extent to which commercial chemistry/chemical engineering software may be able to satisfy the need for thermochemical modeling packages that can accommodate the diverse species and conditions of planetary science problems. Here we compare the output of software package HSC Chemistry™ (Metso Outotec) to published vapor-solid phase diagrams for a variety of major and minor elements. HSC Chemistry™ has been used in several recent geochemical studies of terrestrial volcanic systems [2- 4]. However, it has not to our knowledge been benchmarked against peer-reviewed model results for the conditions and compositions relevant to planetary science. We present one such comparison here, the low- pressure environment of the solar nebula, using literature data. In short, we find excellent agreement between HSC Chemistry™ and the well-regarded academic software package CONDOR. These preliminary results suggest that at least some commercial software packages are capable of robust thermochemical calculations for planetary science.
AIRS Applications Overview & Status, with upcoming plans for Drought Prediction & Volcanic Plume Detection Applications
No abstract provided
Revisiting Satellite Sounder Applications – Reimagining How to Connect Complex Products to Stakeholder Applications and Decision Making
Explore the source record for details and available documents.
On the Application of Model-based Parameter Estimation For Mitigating Corrupted Data in Radar Applications.
Abstract not provided.
Suitable low Global Warming Potential (GWP) refrigerants for two-speed Heat Pumps for residential applications based on speed Heat Pumps for residential applications based on simulated performance simulated performance
Cold climate Heat Pumps (CCHPs) using single-speed compressors in tandem have been successfully built and tested to reach its performance metrics with outdoor temperatures as low as -25°C. CCHPs must be designed to alleviate the problems of too high discharge temperatures, low suction pressure and high-pressure ratio at low ambient conditions and insufficient heating capacity relative to the heating capacity at 8.3°C. In this paper we recognize those concerns. Low-GWP refrigerants are screened based on the shape of their T-S saturation boundary. Simulations of the performance of low-GWP refrigerants (R32, R454B, R466A, and R452B) relative to R410A is done using the DOE/ORNL Heat Pump Design Model at the component level. Systemic inefficiency, the root cause of lost work, is addressed by component-level exergy analysis to refine design options. CCHPs using low-GWP refrigerants addresses issues of reducing energy consumption, lowering carbon footprint, and enabling environmentally sustainability. The CCHP was designed to meet a HSPF > 11.0 and SEER > 15.0 having adequate heat pump heating capacity down to -25°C. It is estimated that at least 2.6 million U.S homes using electric furnaces and heat pumps in cold or very old climates with an annual energy consumption of 0.17EJ would benefit by CCHPs.
Phase II FINAL Research Performance Progress Report for Award DE-SC0019695, "A Platform for Scientific Application Dissemination and Community Engagement" (The “SciDAX” Application Exchange)
Explore the source record for details and available documents.
Bridging the Gap from Networking Technologies to Applications: Workshop Report
The objective of the Next Generation Internet (NGI) Federal program is threefold, encompassing development of networking technologies, high-performance network testbeds, and revolutionary applications. There have been notable advances in emerging network technologies and several nationwide testbeds have been established, but the integration of emerging technologies into applications is lagging. To help bridge this gap between developers of NGI networking technologies and developers of NGI applications, the NASA Research and Education Network (NREN) project hosted a two-day workshop at NASA Ames Research Center in August 1999. This paper presents a summary of the results of this workshop and also describes some of the challenges NREN is facing while incorporating new technologies into HPCC and other NASA applications. The workshop focused on three technologies - Quality of Service (QoS), advanced multicast, and security-and five major NGI application areas - telemedicine, digital earth, digital video, distributed data-intensive applications, and computational infrastructure applications. Network technology experts, application developers, and NGI testbed representatives came together at the workshop to promote cross-fertilization between the groups. Presentations on the first day, including an overview of the three technologies, application case studies and testbed status reports, laid the foundation for discussions on the second day. The objective of these latter discussions, held within smaller breakout groups, was to establish a coherent picture of the current status of the various pieces of each of the three technologies, to create a roadmap outlining future technology development, and to offer technological guidance to application developers. In this paper we first present a brief overview of the NGI applications that were represented at the workshop, focusing on the identification of technological advances that have successfully been incorporated in each application and technological challenges that remain. Next we present the technology roadmaps that were created at the workshop, summarizing the status of various mechanisms that are currently under development and forecasting when various advances are likely to occur within the next one-to-three-year time span. Then we identify issues that were raised at the workshop that might hinder technology development or that might impede integration into NGI applications. We also report some specific guidelines that were offered at the workshop to enable application developers to integrate and effectively use emerging NGI technology building blocks. Finally, we describe NREN activities to incorporate emerging technologies into NASA applications. These activities include support for other NASA High-Performance Computing and Communications Program areas such as IPG (Information Power Grid), support for NASA science enterprises such as Earth science and Mars program prototyping activities, support for satellite/terrestrial networking applications such as the TransAtlantic and TransPacific demonstrations and the Interplanetary Internet, support for NASA telemedicine applications such as the Virtual Collaborative Clinic, and participation in NGI advanced technology testbed initiatives such as the QBone and the NTON/Supernet. For each activity we highlight the primary technological challenge that is associated with it.
Simple, Secure, Internet Delivery of MOOSE-based Applications
Application packaging and distribution are the final steps for delivering software to end-users; both are frequently neglected when creating scientific software. Commercial businesses rely on electronic distribution systems that have rendered disk drives obsolete. Still, national laboratories continue to rely heavily on removable media to distribute and limit access to controlled applications. With increasing concerns of unauthorized copying of sensitive applications, a modern distribution system that utilizes cryptographically secure communication and authentication protocols has been developed. This new distribution system will secure the chain of custody for nuclear software while simultaneously simplifying access to these tools. This report summarizes four primary advancements made toward the secure distribution of Nuclear Energy Advanced Modeling and Simulation (NEAMS)-developed, Multiphysics Object Oriented Simulation Environment (MOOSE)-based applications: application installation, package distribution, automated package building, and distribution of documentation. NEAMS is currently developing more than ten separate applications based on the open-source MOOSE Framework. Distribution of these applications has primarily been accomplished by distributing source code, with end-users compiling the applications themselves. This work created a mechanism where MOOSE applications can be installed in a similar way to any other software. This allows both administrators and end-users simplified access to runnable executables. With this new installation capability, it was then possible to rethink distribution. A new, secure capability for delivering MOOSE-based applications over the internet has been created. This system requires unique cryptographic tokens for authentication, greatly securing the custody chain for software. Once granted access, installation of any NEAMS code can be accomplished with these terminal commands: "conda install ncrc" "ncrc install ncrc-bison." After these two commands (and authenticating) the BISON application will be securely down- loaded from Idaho National Laboratory (INL)’s servers, installed, and ready to use. To enable this new distribution capability to be successful, the open-source Continuous Integration, Verification, Enhancement, and Testing (CIVET) Continuous Integration (CI) capability was augmented to add Continuous Delivery (CD). CD enables the automated building and packaging of MOOSE-based applications as they are modified by development teams, ensuring that our customers can obtain up-to-date versions of the software at any time. The need for instruction on how to use these applications was addressed through modifications to the MOOSE documentation system. The MooseDocs capability, which enables robust documentation of MOOSE-based applications, has been extended to allow both for the installation of documentation and the packaging of documentation with installed applications. Together, these enhancements form the core of a new, secure distribution mechanism for nuclear simulation tools. In concert with the Nuclear Computational Resource Center (NCRC), NEAMS- developed applications will now be straightforward to obtain securely.
Proxy Applications for Converged Workloads: DMC LDRD Initiative
Modern scientific applications are complicated and require coordination of several components. Proxy application driven software-hardware co-design plays a vital role in driving innovation among the developments of applications, software infrastructure and hardware architecture. Proxy applications are self-contained and simplified codes that are intended to model the performance-critical computations within applications. Applications executing on modern High Performance Computing (HPC) systems are susceptible to network congestion, insufficient memory bandwidth within and across compute nodes, and inadvertent loss of performance due to bugs and unoptimized programming models. Modern numerical simulations and machine learning models play a critical role in studying physical phenomenon under myriad uncertainties. Such applications often exhibit irregular computation and memory accesses at specific regions of the application code, which can contribute to various performance bottlenecks at scale. To mitigate such issues and prepare the next generation hardware for a variety of computation and data movement contingencies, a well-known practice is to consider "proxy" applications as representative motifs for various classes of scientific applications. While there is disagreement in the HPC community on the mechanisms of construction of the proxy applications, there is a strong consensus on their positive impact in co-design. Proxy Applications for Converged Workloads (PACER) is about facilitating software-hardware co-design through proxy applications with the goal of improving the performance of converged science workflows on heterogeneous systems.
Accelerating Parallel Applications in Cloud Platforms via Adaptive Time-Slice Control
Cloud platforms can provide flexible and cost-effective environments for parallel applications. However, the resource over-commitment issues, i.e., cloud providers often provide much more executable virtual CPUs than available physical CPUs, still impede the synchronization operations of parallel applications, causing severe performance degradation. Existing methods optimize parallel applications by promoting the priorities of involved VMs. They cannot fully explore the performance of parallel applications, because they ignore the time-slice requirements of different phases of parallel applications. Furthermore, non-parallel applications experience unsatisfied performance because of low scheduling priorities. Given empirical analysis on time-slices of virtual machines (VMs), we find that shortening time-slices can mitigate synchronization overhead which incurs during communication phases, while over-short time-slices cause frequent cache misses in computation phases. Accordingly, we propose an Adaptive Time-slice Control (ATC) mechanism. ATC first detects the phases of parallel applications based on lock latency or cache misses. Then, ATC shortens time-slices during communication phases and prolongs time-slices during computation phases for parallel applications, and sets a uniform time-slice for non-parallel applications. Finally, we evaluate ATC using seven well-known benchmarks with 25+ applications. Experiments show that ATC obtains 1.5-75x performance gain for running parallel applications than state-of-the-art solutions, with nearly unaffected impact on non-parallel applications.
Marshall Application Realignment System (MARS) Architecture
The Marshall Application Realignment System (MARS) Architecture project was established to meet the certification requirements of the Department of Defense Architecture Framework (DoDAF) V2.0 Federal Enterprise Architecture Certification (FEAC) Institute program and to provide added value to the Marshall Space Flight Center (MSFC) Application Portfolio Management process. The MARS Architecture aims to: (1) address the NASA MSFC Chief Information Officer (CIO) strategic initiative to improve Application Portfolio Management (APM) by optimizing investments and improving portfolio performance, and (2) develop a decision-aiding capability by which applications registered within the MSFC application portfolio can be analyzed and considered for retirement or decommission. The MARS Architecture describes a to-be target capability that supports application portfolio analysis against scoring measures (based on value) and overall portfolio performance objectives (based on enterprise needs and policies). This scoring and decision-aiding capability supports the process by which MSFC application investments are realigned or retired from the application portfolio. The MARS Architecture is a multi-phase effort to: (1) conduct strategic architecture planning and knowledge development based on the DoDAF V2.0 six-step methodology, (2) describe one architecture through multiple viewpoints, (3) conduct portfolio analyses based on a defined operational concept, and (4) enable a new capability to support the MSFC enterprise IT management mission, vision, and goals. This report documents Phase 1 (Strategy and Design), which includes discovery, planning, and development of initial architecture viewpoints. Phase 2 will move forward the process of building the architecture, widening the scope to include application realignment (in addition to application retirement), and validating the underlying architecture logic before moving into Phase 3. The MARS Architecture key stakeholders are most interested in Phase 3 because this is where the data analysis, scoring, and recommendation capability is realized. Stakeholders want to see the benefits derived from reducing the steady-state application base and identify opportunities for portfolio performance improvement and application realignment.
Engineering of Data Acquiring Mobile Software and Sustainable End-User Applications
The criteria for which data acquiring software and its supporting infrastructure should be designed should take the following two points into account: the reusability and organization of stored online and remote data and content, and an assessment on whether abandoning a platform optimized design in favor for a multi-platform solution significantly reduces the performance of an end-user application. Furthermore, in-house applications that control or process instrument acquired data for end-users should be designed with a communication and control interface such that the application's modules can be reused as plug-in modular components in greater software systems. The application of the above mentioned is applied using two loosely related projects: a mobile application, and a website containing live and simulated data. For the intelligent devices mobile application AIDM, the end-user interface have a platform and data type optimized design, while the database and back-end applications store this information in an organized manner and manage access to that data to only to authorized user end application(s). Finally, the content for the website was derived from a database such that the content can be included and uniform to all applications accessing the content. With these projects being ongoing, I have concluded from my research that the applicable methods presented are feasible for both projects, and that a multi-platform design for the mobile application only marginally drop the performance of the mobile application.
Proposed guidance for preparing and reviewing a molten salt non-power production or utilization facility application
Development of non-power molten salt reactors (MSRs) are under consideration to further establish an MSR experience base, support the requirements of Title 10 of the Code of Federal Regulations (10 CFR) Section 50.43(e), and provide any additional analyses needed for development of a full-scale MSR. Guidance provided in this report is based on MSRs operating with liquid fuel (i.e., fuel dissolved within a molten salt). These reactors, unless owned by the DOE or DOD, will require licensing by the US Nuclear Regulatory Commission (NRC) staff. Standard review plan (SRP) guidance for large light water reactors (LWRs) is available in NUREG-0800, Standard Review Plan for the Review of Safety Analysis Reports for Nuclear Power Plants; Light Water Reactor (LWR) Edition. However, NRC staff observed that NUREG-0800 is very cumbersome to apply to non-power reactors “because of the great differences in complexity and hazards between non-power reactors and nuclear power plants.” Therefore, a program to develop performance-based guidance applicable to non-power reactors was initiated. In 1996, NUREG-1537, Parts 1 and 2, Guidelines for Preparing and Reviewing Applications for the Licensing of Non-Power Reactors, was published. Part 1, the format and content guide, suggests a uniform format for presenting information in non-power reactor applications that is acceptable to the NRC staff, but conformance with the format and content is not required. Part 2, the SRP, ensures the quality and uniformity of the staff review of an application. Unfortunately, the application guidelines and SRP do not provide adequate guidance for all advanced non-LWR technologies and applications. This discrepancy eventually led to the 2012 development of interim staff guidance (ISG) for NUREG-1537, which includes criteria for describing and reviewing aqueous homogeneous reactors (AHRs). Specifically, NUREG-1537 ISG, 2012 expanded the original document to address three areas: 1. updated criteria for heterogeneous non-power reactors, 2. criteria for licensing AHRs, and 3. criteria for licensing a Part 50-licensed isotope production facility. In 2015, the US Department of Energy (DOE) opted to build on the AHR NUREG-1537 ISG experience by performing a gap analysis of the guidance that would be used to license a non-power MSR. MSRs represent one of the advanced non-LWR technologies selected by DOE for development through a multiyear cost share award with Southern Company Services. Under this Advanced Reactor Concepts 2015 (DOE Advanced Reactor Concepts [ARC] 15) award program, the DOE tasked Oak Ridge National Laboratory (ORNL) to evaluate the guidance changes that the NRC may need to consider when licensing an MSR non-power reactor. ORNL staff, with support from Boston Government Services, LLC, focused on five system-related chapters in NUREG-1537 that were considered most relevant to inform the effort that would be required for a non-power MSR applicant. ORNL documented this review in a technical report, ORNL/TM-2018/834, Proposed Guidance for Preparing and Reviewing Molten Salt Non-Power Reactor License Applications (NUREG-1537). The report was subsequently shared with industry and the NRC. The 2018 review was limited in scope, focusing on key system chapters based on the expected significance of each chapter relative to expected differences in addressing advanced non-LWR technologies, specifically non-power MSRs, compared with heterogeneously fueled non-power reactors. In the ORNL report, proposed generic adaptations were suggested for the following NUREG-1537 chapters: Chapter 4, “Reactor Description”; Chapter 5, “Reactor Coolant Systems”; Chapter 6, “Engineered Safety Features”; Chapter 9, “Auxiliary Systems”; Chapter 11, “Radiation Protection Program and Waste Management” The inclusion of Chapter 11 in the previous review effort was intended to provide guidance for categorizing the waste-handling process for an MSR operating with homogenous fuel. The introductions from Parts 1 and 2 of the 2012 NUREG-1537 ISG provide guidance for the application and review of production facilities. After a period of operation, non-power MSRs with homogenous fuel will include gaseous and soluble fission products. The gaseous fission products will be collected and held for decay in an off-gas system. There might also be an initiative to polish or filter the soluble fission products in the fuel salt by some mechanical or chemical means. The treatment and handling of fission products in the non-power MSR fuel salt and the description of this process in the safety analysis report (SAR) must be very precise to avoid the waste treatment facility being construed as a co-located special nuclear material (SNM) fuel cycle facility (see Section 2.3 of this report). Subsequent to the release of ORNL/TM-2018/834, NRC staff expressed a desire to continue the regulatory gap analysis that was begun in that report. This would provide additional clarity and information addressed in certain sections of the original report, while also providing new guidance on certain topics not addressed in the original report. This revision would benefit the NRC staff reviewing applications involving non-power MSR designs and would help developers understand how the NRC staff might approach the review of such applications. The focus of this report is to provide infrastructure support to the NRC staff for the regulatory review of non-power MSRs.
Characterization and identification of HPC applications at leadership computing facility
High Performance Computing (HPC) is an important method for scientific discovery via large-scale simulation, data analysis, or artificial intelligence. Leadership-class supercomputers are expensive, but essential to run large HPC applications. The Petascale era of supercomputers began in 2008, with the first machines achieving performance in excess of one petaflops, and with the advent of new supercomputers in 2021 (e.g., Aurora, Frontier), the Exascale era will soon begin. However, the high theoretical computing capability (i.e., peak FLOPS) of a machine is not the only meaningful target when designing a supercomputer, as the resources demand of applications varies. A deep understanding of the characterization of applications that run on a leadership supercomputer is one of the most important ways for planning its design, development and operation. In order to improve our understanding of HPC applications, user demands and resource usage characteristics, we perform correlative analysis of various logs for different subsystems of a leadership supercomputer. This analysis reveals surprising, sometimes counter-intuitive patterns, which, in some cases, conflicts with existing assumptions, and have important implications for future system designs as well as supercomputer operations. For example, our analysis shows that while the applications spend significant time on MPI, most applications spend very little time on file I/O. Combined analysis of hardware event logs and task failure logs show that the probability of a hardware FATAL event causing task failure is low. Combined analysis of control system logs and file I/O logs reveals that pure POSIX I/O is used more widely than higher level parallel I/O. Based on holistic insights of the application gained through combined and co-analysis of multiple logs from different perspectives and general intuition, we engineer features to "fingerprint" HPC applications. We use t-SNE (a machine learning technique for dimensionality reduction) to validate the explainability of our features and finally train machine learning models to identify HPC applications or group those with similar characteristic. To the best of our knowledge, this is the first work that combines logs on file I/O, computing, and inter-node communication for insightful analysis of HPC applications in production.
Beyond Like-for-Like: A User-centered Approach to Modernizing Legacy Applications
When modernizing a legacy application, it is easy to fall back on a like-for-like replica with new tools and updated design stylings, but this is an opportunity to explore making a more intuitive application that supports user tasks and efficiency. Rather than having a blank canvas-unburdened by legacy tech debt-to create a new application, you are working with an existing application that is integral to accelerator operations and one that expert users are already familiar with. Due to this, you might assume people will prefer the like-for-like, but you could be carrying forward the pain points, processes that are inefficient, and ultimately wind up with an application that no one wants to use because it doesn't solve existing problems. Getting users involved can make all the difference in your approach to modernizing a legacy application that caters to both newer and expert users. It also can bridge the gap between like-for-like and introducing new GUI design. Having a legacy application doesn't have to make the modernized one difficult to develop, as the existing application is a tool in how you move forward with the new application. It provides insight into areas that an application with a clean slate doesn't give you.