Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “applications”

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 829 records · Page 46
All sourcesNASA NTRSDOE OSTI
DOE OSTI2020

Real Time Applications Using Linear State Estimation Technology (RTA/LSE)

Electric Power Group, LLC (EPG) was awarded DOE OE0000849 to design, develop, and demonstrate three real-time applications for monitoring power system stability. The applications use phasor measurements and processing by a linear state estimator (LSE) to improve system visibility and accuracy. These applications leverage the large and expanding phasor measurement systems being deployed by utilities throughout the world, and specifically in the United States. Phasor measurements provide a much more detailed view of the power systems than traditional SCADA systems, so can provide better visibility of events and an early warning of developing problems. These three applications are real-time contingency analysis (RTCA), area angle monitoring (AAM), and a voltage stability index (VSI). The project was fully completed as proposed. All three applications were successfully implemented and demonstrated. There were challenges the caused project delays, however. While the RTCA is based on well-known concepts and readily available tools, its deployment using phasor measurements meant it needed to be adapted to sometimes sparse measurements and limited coverage areas. EPG met these challenges with extensive modeling and testing. The AAM is based on unproven research, so EPG had to deal with a lot of unknowns and develop additional methods for practical implementation. These activities took more time than anticipated, so required extra time for development. In addition, there was difficulty getting adequate measurement locations for successful deployment and utility installation delays. Consequently, the project required a time extension to complete. These three real-time applications, RTCA, AAM, and VSI, use only phasor measurement input. Since they do not require the EMS or other measurement systems, they can serve as a backup and security check for the EMS. Phasor measurements are validated and extended by an LSE. The LSE will always produce an output even when some inputs are impaired, so the RT applications will operate even when the EMS state estimator does not converge and the applications it supports cannot function. Consequently, these RT applications can provide valuable additional reliability for control center operation.

24 POWER TRANSMISSION AND DISTRIBUTION↗
DOE OSTI2018

Engage second wave ECP/CEED applications

The CEED co-design center aims to impact a wide range of ECP application teams through focused 1-to-1 and 1-to many interactions, facilitated by CEED application liaisons, ultimately targeted to provide easy-to-use discretization libraries for high-order FEM-based application simulations. The goal of this milestone was to extend our reach by identifying a second wave of ECP applications that can benefit from the efficient discretization algorithms and software developed in CEED. These applications were added to the list of the CEED first wave ECP applications (ExaSMR and MARBL), which continue to be main targets for our work. As part of the milestone, we also appointed liaisons on the CEED team that will be responsible for engaging each application, identifying its challenging discretization needs, and outlining a plan for interaction with CEED. Working with all CEED thrusts, the liaisons will be ultimately responsible for ensuring the adoption of CEED technologies in each application as well as for demonstrating their benefits. The selected second wave applications and CEED liaisons are: Urban - liaison Aleks Obabko (ANL), ExaWind - liaison Paul Fischer (UIUC), and ExaAM - liaison Tzanio Kolev (LLNL). In addition to details and results from these efforts, in this document we report on other project-wide activities performed in Q1 of FY19, including: engagements with performing scaling on V100 GPUs, collaboration with ECP/MPICH, participation in ECP/ST’s E4S release, the Laghos-2.0 release, papers, presentations, and other outreach efforts.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS1990

Tools for distributed application management

Distributed application management consists of monitoring and controlling an application as it executes in a distributed environment. It encompasses such activities as configuration, initialization, performance monitoring, resource scheduling, and failure response. The Meta system (a collection of tools for constructing distributed application management software) is described. Meta provides the mechanism, while the programmer specifies the policy for application management. The policy is manifested as a control program which is a soft real-time reactive program. The underlying application is instrumented with a variety of built-in and user-defined sensors and actuators. These define the interface between the control program and the application. The control program also has access to a database describing the structure of the application and the characteristics of its environment. Some of the more difficult problems for application management occur when preexisting, nondistributed programs are integrated into a distributed application for which they may not have been intended. Meta allows management functions to be retrofitted to such programs with a minimum of effort.

Marzullo, Keith↗
NASA NTRS1990

Tools for distributed application management

Distributed application management consists of monitoring and controlling an application as it executes in a distributed environment. It encompasses such activities as configuration, initialization, performance monitoring, resource scheduling, and failure response. The Meta system is described: a collection of tools for constructing distributed application management software. Meta provides the mechanism, while the programmer specifies the policy for application management. The policy is manifested as a control program which is a soft real time reactive program. The underlying application is instrumented with a variety of built-in and user defined sensors and actuators. These define the interface between the control program and the application. The control program also has access to a database describing the structure of the application and the characteristics of its environment. Some of the more difficult problems for application management occur when pre-existing, nondistributed programs are integrated into a distributed application for which they may not have been intended. Meta allows management functions to be retrofitted to such programs with a minimum of effort.

Marzullo, Keith↗
NASA NTRS1995

Applied Virtual Reality Research and Applications at NASA/Marshall Space Flight Center

A Virtual Reality (VR) applications program has been under development at NASA/Marshall Space Flight Center (MSFC) since 1989. The objectives of the MSFC VR Applications Program are to develop, assess, validate, and utilize VR in hardware development, operations development and support, mission operations training and science training. Before this technology can be utilized with confidence in these applications, it must be validated for each particular class of application. That is, the precision and reliability with which it maps onto real settings and scenarios, representative of a class, must be calculated and assessed. The approach of the MSFC VR Applications Program is to develop and validate appropriate virtual environments and associated object kinematic and behavior attributes for specific classes of applications. These application-specific environments and associated simulations will be validated, where possible, through empirical comparisons with existing, accepted tools and methodologies. These validated VR analytical tools will then be available for use in the design and development of space systems and operations and in training and mission support systems. Specific validation studies for selected classes of applications have been completed or are currently underway. These include macro-ergonomic "control-room class" design analysis, Spacelab stowage reconfiguration training, a full-body micro-gravity functional reach simulator, and a gross anatomy teaching simulator. This paper describes the MSFC VR Applications Program and the validation studies.

Hale, Joseph P.↗
NASA NTRS1998

MEMS Applications in Aerodynamic Measurement Technology

Microelectromechanical systems (MEMS) embodies the integration of sensors, actuators, and electronics on a single substrate using integrated circuit fabrication techniques and compatible bulk and surface micromachining processes. Silicon and its derivatives form the material base for the MEMS technology. MEMS devices, including microsensors and microactuators, are attractive because they can be made small (characteristic dimension about 100 microns), be produced in large numbers with uniform performance, include electronics for high performance and sophisticated functionality, and be inexpensive. For aerodynamic measurements, it is preferred that sensors be small so as to approximate measurement at a point, and in fact, MEMS pressure sensors, wall shear-stress sensors, heat flux sensors and micromachined hot wires are nearing application. For the envisioned application to wind tunnel models, MEMS sensors can be placed on the surface or in very shallow grooves. MEMS devices have often been fabricated on stiff, flat silicon substrates, about 0.5 mm thick, and therefore were not easily mounted on curved surfaces. However, flexible substrates are now available and heat-flux sensor arrays have been wrapped around a curved turbine blade. Electrical leads can also be built into the flexible substrate. Thus MEMS instrumented wind tunnel models do not require deep spanwise grooves for tubes and leads that compromise the strength of conventionally instrumented models. With MEMS, even the electrical leads can potentially be eliminated if telemetry of the signals to an appropriate receiver can be implemented. While semiconductor silicon is well known for its electronic properties, it is also an excellent mechanical material for MEMS applications. However, silicon electronics are limited to operations below about 200 C, and silicon's mechanical properties start to diminish above 400 C. In recent years, silicon carbide (SiC) has emerged as the leading material candidate for applications in high temperature environments and can be used for high-temperature MEMS applications. With SiC, diodes and more complex electronics have been shown to operate to about 600 C, while the mechanical properties of SiC are maintained to much higher temperatures. Even when MEMS devices show benefits in the laboratory, there are many packaging challenges for any aeronautics application. Incorporating MEMS into these applications requires new approaches to packaging that goes beyond traditional integrated circuit (IC) packaging technologies. MEMS must interact mechanically, as well as electrically with their environment, making most traditional chip packaging and mounting techniques inadequate. Wind tunnels operate over wide temperature ranges in an environment that is far from being a 'clean-room.' In flight, aircraft are exposed to natural elements (e.g. rain, sun, ice, insects and dirt) and operational interferences(e.g. cleaning and deicing fluids, and maintenance crews). In propulsion systems applications, MEMS devices will have to operate in environments containing gases with very high temperatures, abrasive particles and combustion products. Hence deployment and packaging that maintains the integrity of the MEMS system is crucial. This paper presents an overview of MEMS fabrication and materials, descriptions of available sensors with more details on those being developed in our laboratories, and a discussion of sensor deployment options for wind tunnel and flight applications.

Reshotko, E.↗
NASA NTRS1998

Chemical Gas Sensors for Aerospace Applications

Chemical sensors often need to be specifically designed (or tailored) to operate in a given environment. It is often the case that a chemical sensor that meets the needs of one application will not function adequately in another application. The more demanding the environment and specialized the requirement, the greater the need to adapt exiting sensor technologies to meet these requirements or, as necessary, develop new sensor technologies. Aerospace (aeronautic and space) applications are particularly challenging since often these applications have specifications which have not previously been the emphasis of commercial suppliers. Further, the chemical sensing needs of aerospace applications have changed over the years to reflect the changing emphasis of society. Three chemical sensing applications of particular interest to the National Aeronautics and Space Administration (NASA) which illustrate these trends are launch vehicle leak detection, emission monitoring, and fire detection. Each of these applications reflects efforts ongoing throughout NASA. As described in NASA's "Three Pillars for Success", a document which outlines NASA's long term response to achieve the nation's priorities in aerospace transportation, agency wide objectives include: improving safety and decreasing the cost of space travel, significantly decreasing the amount of emissions produced by aeronautic engines, and improving the safety of commercial airline travel. As will be discussed below, chemical sensing in leak detection, emission monitoring, and fire detection will help enable the agency to meet these objectives. Each application has vastly different problems associated with the measurement of chemical species. Nonetheless, the development of a common base technology can address the measurement needs of a number of applications.

Hunter, Gary W.↗
NASA NTRS2000

Developing CORBA-Based Distributed Scientific Applications from Legacy Fortran Programs

Recent progress in distributed object technology has enabled software applications to be developed and deployed easily such that objects or components can work together across the boundaries of the network, different operating systems, and different languages. A distributed object is not necessarily a complete application but rather a reusable, self-contained piece of software that co-operates with other objects in a plug-and-play fashion via a well-defined interface. The Common Object Request Broker Architecture (CORBA), a middleware standard defined by the Object Management Group (OMG), uses the Interface Definition Language (IDL) to specify such an interface for transparent communication between distributed objects. Since IDL can be mapped to any programming language, such as C++, Java, Smalltalk, etc., existing applications can be integrated into a new application and hence the tasks of code re-writing and software maintenance can be reduced. Many scientific applications in aerodynamics and solid mechanics are written in Fortran. Refitting these legacy Fortran codes with CORBA objects can increase the codes reusability. For example, scientists could link their scientific applications to vintage Fortran programs such as Partial Differential Equation(PDE) solvers in a plug-and-play fashion. Unfortunately, CORBA IDL to Fortran mapping has not been proposed and there seems to be no direct method of generating CORBA objects from Fortran without having to resort to manually writing C/C++ wrappers. In this paper, we present an efficient methodology to integrate Fortran legacy programs into a distributed object framework. Issues and strategies regarding the conversion and decomposition of Fortran codes into CORBA objects are discussed. The following diagram shows the conversion and decomposition mechanism we proposed. Our goal is to keep the Fortran codes unmodified. The conversion- aided tool takes the Fortran application program as input and helps programmers generate C/C++ header file and IDL file for wrapping the Fortran code. Programmers need to determine by themselves how to decompose the legacy application into several reusable components based on the cohesion and coupling factors among the functions and subroutines. However, programming effort still can be greatly reduced because function headings and types have been converted to C++ and IDL styles. Most Fortran applications use the COMMON block to facilitate the transfer of large amount of variables among several functions. The COMMON block plays the similar role of global variables used in C. In the CORBA-compliant programming environment, global variables can not be used to pass values between objects. One approach to dealing with this problem is to put the COMMON variables into the parameter list. We do not adopt this approach because it requires modification of the Fortran source code which violates our design consideration. Our approach is to extract the COMMON blocks and convert them into a structure-typed attribute in C++. Through attributes, each component can initialize the variables and return the computation result back to the client. We have tested successfully the proposed conversion methodology based on the f2c converter. Since f2c only translates Fortran to C, we still needed to edit the converted code to meet the C++ and IDL syntax. For example, C++/IDL requires a tag in the structure type, while C does not. In this paper, we identify the necessary changes to the f2c converter in order to directly generate the C++ header and the IDL file. Our future work is to add GUI interface to ease the decomposition task by simply dragging and dropping icons.

Sang, Janche↗
NASA NTRS2000

A Tool for Automatic Data Distribution for CFD Applications on Structured Grids

Development of HPF versions of NPB and ARC3D has shown that HPF provides an efficient, concise way to express parallelism and to organize data traffic. The use of HPF, as noted in the papers, requires an intimate knowledge of the applications and a detailed analysis of data affinity, data movement, and data granularity. To simplify and accelerate the task of developing HPF versions of existing CFD applications we have designed and implemented ADAPT (Automatic Data Alignment and Placement Tool). ADAPT analyzes a CFD application working on a single structured grid and generates HPF TEMPLATE, (RE)DISTRIBUTION, ALIGNMENT, and INDEPENDENT directives. The directives can be generated on the nest level, subroutine level, application level, or on the application interface level. ADAPT annotates an existing CFD FORTRAN application, performing computations on single or multiple grids. On each grid the application is considered as a sequence of operators, each applied to a set of variables defined in a particular grid domain. ADAPT automatically detects implicit operators (i.e., having data dependences) and explicit operators (without data dependences). For parallelization of an explicit operator ADAPT creates a template for the operator domain, aligns arrays used in the operator with the template, distributes the template, and declares the loops over the distributed dimensions as INDEPENDENT. For parallelization of an implicit operator, the distribution of the operator's domain should be consistent with the operator's dependences. Any dependence between sections distributed on different processors would preclude parallelization if the compiler does not have an ability to pipeline computations. If a data distribution is "orthogonal" to the dependences of an implicit operator, then the loop which implements the operator can be declared as INDEPENDENT. ADAPT starts with an analysis of array index expressions of the loop nests. For each pair of arrays referenced in an assignment statement, it generates an arc in the alignment graph and annotates it with an affinity relation. The template, alignment, and distribution directives for a particular loop nest are then derived from a transitive closure of the affinity relation. A compromise of data distributions in different nests and subroutines is achieved by merging annotated alignment graphs for adjacent nests/stibroutine calls in the nest/call graph of the application in the process called distribution lifting. ADAPT has been implemented as a C++ program running in conjunction with a parallelization tool called CAPTools. ADAPT uses the parse tree, interprocedural analysis and application database generated by CAPTools. It also uses the Directed Graph class, initially implemented in p2d2 (parallel debugger oi distributed programs), and some other classes supporting symbolic computations. ADAPT uses data distribution techniques described. ADAPT was tested with ARC3D and the FT benchmark and has demonstrated a code performance within a factor of 1.5 of handwritten versions.

Frumkin, Michael↗
NASA NTRS1999

Automatic Data Distribution for CFD Applications on Structured Grids

Development of HPF versions of NPB and ARC3D showed that HPF has potential to be a high level language for parallelization of CFD applications. The use of HPF requires an intimate knowledge of the applications and a detailed analysis of data affinity, data movement and data granularity. Since HPF hides data movement from the user even with this knowledge it is easy to overlook pieces of the code causing low performance of the application. In order to simplify and accelerate the task of developing HPF versions of existing CFD applications we have designed and partially implemented ADAPT (Automatic Data Distribution and Placement Tool). The ADAPT analyzes a CFD application working on a single structured grid and generates HPF TEMPLATE, (RE)DISTRIBUTION, ALIGNMENT and INDEPENDENT directives. The directives can be generated on the nest level, subroutine level, application level or inter application level. ADAPT is designed to annotate existing CFD FORTRAN application performing computations on single or multiple grids. On each grid the application can considered as a sequence of operators each applied to a set of variables defined in a particular grid domain. The operators can be classified as implicit, having data dependences, and explicit, without data dependences. In order to parallelize an explicit operator it is sufficient to create a template for the domain of the operator, align arrays used in the operator with the template, distribute the template, and declare the loops over the distributed dimensions as INDEPENDENT. In order to parallelize an implicit operator, the distribution of the operator's domain should be consistent with the operator's dependences. Any dependence between sections distributed on different processors would preclude parallelization if compiler does not have an ability to pipeline computations. If a data distribution is "orthogonal" to the dependences of an implicit operator then the loop which implements the operator can be declared as INDEPENDENT.

Frumkin, Michael↗
NASA NTRS2002

Achievements of the DOT-NASA Joint Program on Remote Sensing and Spatial Information Technologies: Application to Multimodal Transportation

This report presents three-year accomplishments from the national program on Commercial Remote Sensing and Geospatial Technology (CRSGT) application to transportation, administered by the U.S. Department of Transportation (U.S. DOT) in collaboration with the National Aeronautics and Space Administration (NASA). The joint program was authorized under Section 5113 of the Transportation Equity Act for the 21st Century (TEA-21). This is the first national program of its type focusing on transportation applications of emerging commercial remote sensing technologies. U.S. DOT's Research and Special Programs Administration manages the program in coordination with NASA's Earth Science Enterprise's application programs. The program focuses on applications of CRSGT products and systems for providing smarter and more efficient transportation operations and services. The program is performed in partnership with four major National Consortia for Remote Sensing in Transportation (NCRST). Each consortium focuses on research and development of products in one of the four priority areas for transportation application, and includes technical application and demonstration projects carried out in partnership with industries and service providers in their respective areas. The report identifies products and accomplishments from each of the four consortia in meeting the goal of providing smarter and more efficient transportation services. The products and results emerging from the program are being implemented in transportation operations and services through state and local agencies. The Environmental Assessment and Application Consortium (NCRST-E) provides leadership for developing and deploying cost effective environmental and transportation planning services, and integrates CRSGT advances for achieving smarter and cost effective corridor planning. The Infrastructure Management Consortium (NCRST-I) provides leadership in technologies that achieve smarter and cheaper ways of managing transportation infrastructure assets, operation, and inspection, and integrates CRSGT advances for achieving infrastructure security. The Traffic Flow Consortium (NCRST-F) provides leadership to develop new tools for regional traffic flow management including heavy vehicles and intermodal flow of freight, and integrates CRSGT advances for complementing and extending the reach of ITS user services. The Safety, Hazards and Disasters (NCRST-H) provides leadership for deploying remote sensing technology to locate transportation hazards and improve disaster recovery, and integrates CRSGT advances for application to protect transportation systems from terrorism. The DOT-NASA team is proud to present this report of accomplishments on products and results emerging from the joint program for application to transportation practice.

Source record↗
NASA NTRS2011

Ruby on Rails Applications

Ruby on Rails is an open source web application framework for the Ruby programming language. The first application I built was a web application to manage and authenticate other applications. One of the main requirements for this application was a single sign-on service. This allowed authentication to be built in one location and be implemented in many different applications. For example, users would be able to login using their existing credentials, and be able to access other NASA applications without authenticating again. The second application I worked on was an internal qualification plan app. Previously, the viewing of employee qualifications was managed through Excel spread sheets. I built a database driven application to streamline the process of managing qualifications. Employees would be able to login securely to view, edit and update their personal qualifications.

Hochstadt, Jake↗
NASA NTRS2014

Development and Testing of Functionally Operative and Visually Appealing Remote Firing Room Displays and Applications

This internship provided an opportunity for an intern to work with NASA's Ground Support Equipment (GSE) for the Spaceport Command and Control System (SCCS) at Kennedy Space Center as a remote display developer, under NASA technical mentor Kurt Leucht. The main focus was on creating remote displays and applications for the hypergolic and high pressure helium subsystem team to help control the filling of the respective tanks. As a remote display and application developer for the GSE hypergolic and high pressure helium subsystem team the intern was responsible for creating and testing graphical remote displays and applications to be used in the Launch Control Center (LCC) on the Firing Room's computers. To become more familiar with the subsystem, the individual attended multiple project meetings and acquired their specific requirements regarding what needed to be included in the software. After receiving the requirements for the displays, the next step was to create displays that had both visual appeal and logical order using the Display Editor, on the Virtual Machine (VM). In doing so, all Compact Unique Identifiers (CUI), which are associated with specific components within the subsystem, were need to be included in each respective display for the system to run properly. Then, once the display was created it was to be tested to ensure that the display runs as intended by using the Test Driver, also found on the VM. This Test Driver is a specific application that checks to make sure all the CUIs in the display are running properly and returning the correct form of information. After creating and locally testing the display it needed to go through further testing and evaluation before deemed suitable for actual use. For the remote applications the intern was responsible for creating a project that focused on channelizing each component included in each display. The core of the application code was created by setting up spreadsheets and having an auto test generator, generate the complete code structure. This application code was then loaded and ran on a testing environment set to ensure the code runs as anticipated. By the end of the semester-long experience at NASA's Kennedy Space Center, the individual should have gained great knowledge and experience in various areas of both display and application development and testing. They were able to demonstrate this new knowledge obtained by creating multiple successful remote displays that will one day be used by the hypergolic and high pressure helium subsystem team in the LCC's firing rooms to service the new Orion spacecraft. The completed display channelization application will be used to receive verification from NASA quality engineers.

Display Devices↗
NASA NTRS2016

Deploying a Route Optimization EFB Application for Commercial Airline Operational Trials

The Traffic Aware Planner (TAP), developed for NASA Langley Research Center to support the Traffic Aware Strategic Aircrew Requests (TASAR) project, is a flight-efficiency software application developed for an Electronic Flight Bag (EFB). Tested in two flight trials and planned for operational testing by two commercial airlines, TAP is a real-time trajectory optimization application that leverages connectivity with onboard avionics and broadband Internet sources to compute and recommend route modifications to flight crews to improve fuel and time performance. The application utilizes a wide range of data, including Automatic Dependent Surveillance Broadcast (ADS-B) traffic, Flight Management System (FMS) guidance and intent, on-board sensors, published winds and weather, and Special Use Airspace (SUA) schedules. This paper discusses the challenges of developing and deploying TAP to various EFB platforms, our solutions to some of these challenges, and lessons learned, to assist commercial software developers and hardware manufacturers in their efforts to implement and extend TAP functionality in their environments. EFB applications (such as TAP) typically access avionics data via an ARINC 834 Simple Text Avionics Protocol (STAP) server hosted by an Aircraft Interface Device (AID) or other installed hardware. While the protocol is standardized, the data sources, content, and transmission rates can vary from aircraft to aircraft. Additionally, the method of communicating with the AID may vary depending on EFB hardware and/or the availability of onboard networking services, such as Ethernet, WIFI, Bluetooth, or other mechanisms. EFBs with portable and installed components can be implemented using a variety of operating systems, and cockpits are increasingly incorporating tablet-based technologies, further expanding the number of platforms the application may need to support. Supporting multiple EFB platforms, AIDs, avionics datasets, and user interfaces presents a challenge for software developers and the management of their code baselines. Maintaining multiple baselines to support all deployment targets can be extremely cumbersome and expensive. Certification also needs to be considered when developing the application. Regardless of whether the software is itself destined to be certified, data requirements in support of the application and user interface elements may introduce certification requirements for EFB manufacturers and the airlines. The example of TAP, the challenges faced, solutions implemented, and lessons learned will give EFB application and hardware developers insight into future potential requirements in deploying TAP or similar flight-deck EFB applications.

Roscoe, David A.↗
NASA NTRS2020

PACE Technical Report Series, Volume 9: PACE Applications Plan

This volume presents PACE mission’s plan for development and execution of a PACE Applications Program. NASA maintains an Applied Sciences Program (https://appliedsciences.nasa.gov) to help institutions and individuals make better decisions about our environment, food, water, health and safety through the use of NASA data. In 2016, NASA Headquarters began requiring all flight projects to implement a Project Applications Program with the purpose of: (a) scoping and developing applied research and applications as part of the overall mission concept; (b) demonstrating the project’s benefit to society and contributions to the achievement of societal outcomes; (c) identifying specific product applications and Communities of Potential to better understand the impacts and benefit from using project products and models; (d) increasing the utility of data products; and (e) fostering a Community of Practice who can work with the project throughout the emission life cycle. In response to and in support of this NASA Headquarters directive, the PACE mission developed this PACE Applications Program Plan. While consideration of applications and applied sciences has always been embedded into PACE, the Applications Program truly kicked into high gear in December 2019 (see https://pace.gsfc.nasa.gov). At the time of this writing, the number of PACE Early Adopters has already reached 20. And, the first PACE Applications Workshop will be held (virtually) in late September 2020, with 500 attendees registered. My congratulations and thanks to the PACE Applications Program team for a tremendous first year.

Maria Tzortziou↗
NASA NTRSDate not supplied

From NASA's EOS to ESO: Advancing Applications of the Future Atmosphere Observing (AOS) Mission

The NASA Earth System Observatory (ESO) Atmosphere Observing System (AOS) is being designed to explore the fundamental questions of how interconnections between aerosols, clouds and precipitation impact our weather and climate, addressing real-world challenges to benefit society. A fundamental component of the AOS mission is ensuring that applications for economic and societal benefit are considered to the greatest extent possible in mission design. As a result, the AOS Applications Impact Team (AIT) was formed to address this objective. The overarching goal of the AIT is to help improve capacity for transitioning science to applications to make it possible to more quickly and effectively inform decisions that will directly benefit society. We seek to maximize AOS benefit to impact decisions through early engagement in the mission development phase in order to prepare stakeholders to apply observations as soon as AOS mission data become available. A critical component of preparing future users of AOS mission data is building on the successes of applications of NASA’s existing Earth Observing System (EOS), A-Train, and sub-orbital campaigns with the goal of advancing current mission applications activities and preparing for innovative AOS mission observations. NASA’s GPM mission forms a framework to enhance AOS precipitation applications while AOS health and air quality applications benefit from the heritage of CALIPSO and MODIS. Additionally, AOS will likely benefit from current and future missions such as TROPICS, MAIA, TEMPO, and PACE which launch before AOS. Additionally, current sub-orbital field campaigns, such as NASA IMPACTS and ACTIVATE, provide rich data sources to highlight future AOS capabilities. Engaging with existing missions and sub-orbital field campaigns helps to identify and understand data needs, gaps, and opportunities for current and future stakeholders, determine what data products are of highest value and use, and connect stakeholders with current mission data that can serve as AOS proxy data, among others. In this presentation, we provide an overview of AOS AIT activities, initiatives, and the AOS Applications Seminar Series to highlight how existing EOS, A-Train, and sub-orbital missions can play a critical role in advancing AOS applications prior to launch.

Emily B. Berndt↗
DOE OSTI2020

Tracking Radioactive Isotopes in HVAC and Application for Hot Cell Analyses - 20155

In recent years, the surge in the number of isotope production facilities under design has increased the need to analyze isotope migration in facility Heating, Ventilation, and Air Conditioning (HVAC) during normal operations and accident scenarios. These facilities are used to produce isotopes for medical, security, and industrial applications and as such are subject to license and regulatory requirements 10CFR20, 10CFR30, 10CFR50, and 10CFR70. GOTHIC, a general-purpose thermal-hydraulics software package, includes the ability to model isotopic tracers, radioactive decay and isotope migration as well as HEPA and charcoal filters for isotope retention. A GOTHIC model was developed by Zachry Nuclear Engineering (ZNE) to examine the effect of negative room pressure, HEPA filtration, and HVAC fluctuations on radiation areas, hot cells and gloveboxes. Radioactive tracers were used to simulate the concentration of spills within contaminated areas, track the migration of isotopes of interest, and determine the isotopic retention and buildup on facility HEPA filters. A variety of isotopes with concern to dose (e.g., Kr-85, Sr-90, I-131, etc.), including their decay and progeny, are included in the analysis. Negative pressures are maintained in the regions of interest by a representative central HVAC system equipped with a volumetric fan that exhausts to the environment after a series of isolation valves and HEPA filters. GOTHIC is an industry trusted tool for providing engineering solutions for a variety of applications, including fission product tracking, aerosol and particulate transport and ventilation assessments. The software provides an integrated analysis environment that includes a graphical user interface (GUI) for constructing analysis models, a numerical solver that includes parallel processing capabilities and a post-processor for evaluating simulation results. It solves the conservation equations for mass, momentum and energy for multicomponent, multi-phase flow in lumped parameter and multi-dimensional geometries (1, 2, or full 3D), including the effects of turbulence, diffusion and buoyancy. It has been developed and maintained under a Quality Assurance program in compliance with the requirements of 10CFR50 Appendix B and applicable portions of ASME NQA-1 since 1995. GOTHIC has been used for assessing both forced and natural convection conditions for a wide range of applications, including: - Tracking concentration of hazardous gases and chemicals for habitability and safety assessments - Determining ventilation and filtration requirements and optimizing location and arrangement of these systems - Room heat-up, including diverse and Flexible coping strategies for Extended Loss of AC Power (FLEX/ELAP) - Equipment Qualification (EQ) A distinctive feature of GOTHIC is the ability to track many different fields/substances in a simulation, including user defined tracer elements, in the liquid, vapor and droplet fields as well as surfaces and filters. This capability allows GOTHIC to model fission product transport and release or the removal of particulates or harmful toxins from exhaust gases using a spray scrubber or other types of filtration systems. GOTHIC also includes models for engineered equipment, such as fans, filters, charcoal filters, dryers/demisters, dampers, etc. The aerosols and other filtered material are removed or accumulated in these components. The range of aerosol and radiological applications that GOTHIC has been used for includes: - Source Term: Primary Coolant (Equilibrium) Activity; Non-Water Coolant Source/Leakage. - Conditions for Iodine Re-evolution: Sump/Suppression Pool Conditions and pH; - RWST Conditions and pH. - Isotope Removal Mechanisms: Containment Sprayed and Unsprayed Region Mixing; Charcoal Filter Heating due to Iodine decay. - Radionuclide Transport and Decay: Post-LOCA Release in containment; Transport between connected Compartments and vent systems; Groundwater transport of radionuclides. - Non-Newtonian Fluid modeling for sludge, waste tanks, etc. ADAMS ML071581053 (titled 'Best Practice Guidelines for the use of CFD in Nuclear Reactor Safety Applications') poses guidelines for applying single phase CFD codes in nuclear reactor safety problems and GOTHIC is listed as a 'tool for 3D flows' and 'dispersal and deposition of radionuclides.' The Nuclear Quality Assurance (NQA) pedigree of GOTHIC is an important aspect for applications in the nuclear industry. The fundamental tracer models (convective transport, molecular and turbulent diffusion, removal mechanisms, etc.) have been verified using analytical solutions and validated against applicable separate effects tests. Also, GOTHIC has been benchmarked to many integrated effects tests, including Phebus FP (Fission Product). GOTHIC gives good agreement for the buildup and decay of fission products in Phebus Test 3. The model developed by ZNE demonstrates GOTHIC's applicability and acceptability for use in analyzing the migration and retention of radioactive isotopes and their progeny in normal operation and accident scenario analyses for isotope production facilities, hot cells, and gloveboxes. The tracer activities calculated by GOTHIC can then be used in downstream radiation transport and shielding codes like RADTRAD-NAI{sup C}, MCNP{sup R}, and MicroShield{sup R} to determine on-site and of-site doses. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2016

Recent Progress on the Stochastic Objective Decision Aide (SODA) Application

Idaho State University, in collaboration with Idaho National Laboratory, is engaged in development of a simple to use software application that utilizes stochastic techniques for the calculation of radiation doses associated with hypothetical radioactive material releases. This work is being performed through a grant from the U.S. Department of Energy (DOE) Nuclear Safety Research and Development (NSR and D) Program. Initial progress on the application was reported previously. Recent additions to the application are reported here. The Stochastic Objective Decision Aide (SODA) provides an easy to use software application to help decision makers support their judgment about the need or lack of need for safety structures, systems, and components. SODA is not intended to replace traditional design basis accident dose calculation methodology, nor is it intended to replace existing software used to perform formal dose consequence calculations. Rather, SODA is intended to supplement information obtained from existing codes to give a decision maker more information about an accident scenario. SODA also provides a simple method to perform parametric or sensitivity studies on individual input parameters. Non-reactor nuclear facilities operated under the approval authority of the US DOE use unmitigated hazard evaluations to determine if potential radiological doses associated with design basis events challenge dose evaluation guidelines. Unmitigated events that sufficiently challenge dose evaluation guidelines merit the selection of safety structures, systems, or components (SSCs) to prevent or mitigate the hazard. Dose consequence calculations traditionally involve use of the 'five-factor' formula: ST = MAR.DR.ARF.RF.LPF where ST is the source term (Bq), MAR is the total available material-at-risk (Bq), DR is the damage ratio (no units), ARF is the airborne release fraction (no units), RF is the respirable fraction (no units), and LPF is the leak path factor (no units). Potential radiation doses are then calculated using: CED = χ/Q.BR.ST.DCF (2) where CED is the committed effective dose (Sv), χ/Q is the plume dispersion (s/m{sup 3}), BR is the breathing rate (m{sup 3}/s), ST is the source term (Bq), and DCF is the dose conversion factor (Sv/Bq). Conservative single value input parameters are typically used to represent ARF, RF, LPF and BR. The traditional methodology, while conservative, can lead to skewed conclusions in the balance between cost and risk reduction resulting in over engineered systems with greater design, construction and operating costs. Rather than using a bounding single point value for each parameter in the dose consequence calculation, SODA uses distributions for some or all of the parameters. Each input parameter distribution is stochastically sampled and the resulting dose consequence calculation is repeated many times to develop a dose consequence distribution. The resulting distribution provides more information for the decision maker to rely upon when determining the need for safety SSCs. The SODA application was developed using MATLAB and it incorporates the use of Monte Carlo techniques as well as a graphical user interface (GUI). The application includes user selection of the governing distribution for parameters such as the MAR, DR, ARF, RF, LPF,χ/Q, BR, and DCF. While MATLAB was used for the development work, the application is distributed as a self-contained executable program. Features of the application include pull down menus with available distributions for the various parameters. The user has the option to plot the input parameter distribution that results from the random sampling process. The resulting dose consequence distribution is automatically analyzed to determine its similarity to well know distributions. This was done using the Bayesian Information Criterion method. If the resulting distribution is sufficiently similar to a well-known distribution, the application provides information about the distributions such as the mean value and other parameters. (authors)

22 GENERAL STUDIES OF NUCLEAR REACTORS↗