Search NASA⌕ Search

SEARCH · Search NASA

Results for “execution time”

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 1,495 records · Page 83

Maxine Onsite: Estimating Dose from Chronic Atmospheric Radioactive Releases

Maxine Onsite: Developed to estimate dose to individuals who are working onsite but are not site employees. Follows the methodologies discussed in US NRC Regulatory Guides 1.109 and 1.111 to determine dose from a chronic atmospheric release. Determines the dose given relative air concentrations and deposition concentrations as input. We look at four locations onsite that may be accessed by members of the public. To show compliance with the EPA and DOE public dose limit of 10 mrem/yr, determining who is a member of the public or a worker onsite is necessary. SRS has defined a member of the public for NESHAPS and DOE O 458.1. Maxine Onsite runs on Microsoft Windows Operating System through a Microsoft Excel spreadsheet. Input from the user includes parameters that are variable such as air concentrations, and fixed, such as distance to the receptor and elemental iodine fraction. Maxine Onsite was developed from Maxine which is a program meant to calculate dose to the MEI via three pathways, external, inhalation, and ingestion. Maxine Onsite is meant for looking at the exposure through the external and inhalation pathways only, no local food production onsite. The ways that Maxine Onsite is used to calculate the dose to the MEI includes the following: - Determining the respective air concentration values at each location using distances from the release stack; - Breathing rates for the MEI; - Determining the amount of time the MEI is outside; - Determining the plume travel time. The following relative air and ground deposition values for proper execution of the spreadsheet come from MAXDOSE-SR and are needed to accurately determine the dose to the MEI: relative air concentration, relative air concentration decayed by 2.26 days, relative air concentration decayed and depleted for 8 days, and relative deposition. Test cases were designed, developed, and executed to determine the accuracy of Maxine Onsite, which were verified additionally through hand calculations. Several changes were made for testing, including varying air concentrations, distances, breathing rates, and shielding factors. Each test case was then verified through hand calculations to assure the accuracy of the calculated doses. The results from the test cases, as well as the default parameters, can be used for benchmarking Maxine Onsite in the future. Maxine Onsite performs as expected and produces correct and accurate results at each of the different locations onsite (TRL, B-Area Barracks, SRELCC, and Gunsite 51) for varying test cases. The input required by the user is minimal and includes the results of the dose to the MEI on the first page for ease of access. Future plans for Maxine Onsite include adding in the ingestion pathway and adding in atmospheric dispersion estimates to the spreadsheet.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

The Exascale Framework for High Fidelity coupled Simulations (EFFIS): Enabling whole device modeling in fusion science

We present the Exascale Framework for High Fidelity coupled Simulations (EFFIS), a workflow and code coupling framework developed as part of the Whole Device Modeling Application (WDMApp) in the Exascale Computing Project. EFFIS consists of a library, command line utilities, and a collection of run-time daemons. Together, these software products enable users to easily compose and execute workflows that include: strong or weak coupling, in situ (or offline) analysis/visualization/monitoring, command-and-control actions, remote dashboard integration, and more. We describe WDMApp physics coupling cases and computer science requirements that motivate the design of the EFFIS framework. Furthermore, we explain the essential enabling technology that EFFIS leverages: ADIOS for performant data movement, PerfStubs/TAU for performance monitoring, and an advanced COUPLER for transforming coupling data from its native format to the representation needed by another application. Finally, we demonstrate EFFIS using coupled multi-simulation WDMApp workflows and exemplify how the framework supports the project’s needs. We show that EFFIS and its associated services for data movement, visualization, and performance collection does not introduce appreciable overhead to the WDMApp workflow and that the resource-dominant application’s idle time while waiting for data is minimal.

97 MATHEMATICS AND COMPUTING↗

Combining Partial Redundancy and Checkpointing for HPC

Today's largest High Performance Computing (HPC) systems exceed one Petaflops (10^15 floating point operations per second) and exascale systems are projected within seven years. But reliability is becoming one of the major challenges faced by exascale computing. With billion-core parallelism, the mean time to failure is projected to be in the range of minutes or hours instead of days. Failures are becoming the norm rather than the exception during execution of HPC applications. Current fault tolerance techniques in HPC focus on reactive ways to mitigate faults, namely via checkpoint and restart (C/R). Apart from storage overheads, C/R-based fault recovery comes at an additional cost in terms of application performance because normal execution is disrupted when checkpoints are taken. Studies have shown that applications running at a large scale spend more than 50\% of their total time saving checkpoints, restarting and redoing lost work. Redundancy is another fault tolerance technique, which employs redundant processes performing the same task. If a process fails, a replica of it can take over its execution. Thus, redundant copies can decrease the overall failure rate. The downside of redundancy is that extra resources are required and there is an additional overhead on communication and synchronization. This work contributes a model and analyzes the benefit of C/R in coordination with redundancy at different degrees to minimize the total wallclock time and resources utilization of HPC applications. We further conduct experiments with an implementation of redundancy within the MPI layer on a cluster. Our experimental results confirm the benefit of dual and triple redundancy - but not for partial redundancy - and show a close fit to the model. At 80,000 processes, dual redundancy requires twice the number of processing resources for an application but allows two jobs of 128 hours wallclock time to finish within the time of just one job without redundancy. For narrow ranges of processor counts, partial redundancy results in the lowest time. Once the count exceeds 770, 000, triple redundancy has the lowest overall cost. Thus, redundancy allows one to trade-off additional resource requirements against wallclock time, which provides a tuning knob for users to adapt to resource availabilities.

Elliott, James↗

On-the fly scheduling of execution of dynamic hardware behaviors

Methods for dynamically executing computer code across multiple disparate processing unit architectures are disclosed. During execution of a first portion of computer code on a first processing unit, it is determined that a first dynamic hardware behavior of a plurality of dynamic hardware behaviors will occur at a subsequent point in time, based on a second dynamic hardware behavior that is occurring. The methods include determining to execute code corresponding to the first dynamic hardware behavior on a second processing unit, rather than the first processing unit, and scheduling computer program code corresponding to the first dynamic hardware behavior to execute on the second processing unit rather than the first processing unit. Upon completion of execution of the computer code corresponding to the first dynamic hardware behavior, a remaining portion of the computer code is scheduled to execute on the first processing unit.

97 MATHEMATICS AND COMPUTING↗

Event-Driven Modeling and Execution of Robotic Activities and Contingencies in the Europa Lander Mission Concept Using BPMN

TRACE (Traceable Robotic Activity Composer and Executive) is a tool designed to address the model-ing, verification, and execution of planned and con-tingent activities during robotic space missions. These activities can be modeled (i.e., planned) graph-ically in TRACE using the Business Process Model and Notation (BPMN) language. This standardized language is used to model a sequence of robotic ac-tivities tied together by logical constructs, events, and time. TRACE includes verification tools to en-sure feasibility before mission models are executed by TRACE’s executive, which is integrated into the autonomy subsystem via a connector. In this paper, we describe TRACE in detail as it would apply to a conceptual Europa Lander surface mission with planned excavation and sample collection activities, as well as, contingency activities when execution is off-nominal—all highlighting our novel use of BPMN as a lingua franca for the pipeline from mis-sion planning to autonomous execution.

Lim, Grace↗

Modeling and optimum time performance for concurrent processing

The development of a new graph theoretic model for describing the relation between a decomposed algorithm and its execution in a data flow environment is presented. Called ATAMM, the model consists of a set of Petri net marked graphs useful for representing decision-free algorithms having large-grained, computationally complex primitive operations. Performance time measures which determine computing speed and throughput capacity are defined, and the ATAMM model is used to develop lower bounds for these times. A concurrent processing operating strategy for achieving optimum time performance is presented and illustrated by example.

Mielke, Roland R.↗

Simulator for heterogeneous dataflow architectures

A new simulator is developed to simulate the execution of an algorithm graph in accordance with the Algorithm to Architecture Mapping Model (ATAMM) rules. ATAMM is a Petri Net model which describes the periodic execution of large-grained, data-independent dataflow graphs and which provides predictable steady state time-optimized performance. This simulator extends the ATAMM simulation capability from a heterogenous set of resources, or functional units, to a more general heterogenous architecture. Simulation test cases show that the simulator accurately executes the ATAMM rules for both a heterogenous architecture and a homogenous architecture, which is the special case for only one processor type. The simulator forms one tool in an ATAMM Integrated Environment which contains other tools for graph entry, graph modification for performance optimization, and playback of simulations for analysis.

Malekpour, Mahyar R.↗

A Prototype Lisp-Based Soft Real-Time Object-Oriented Graphical User Interface for Control System Development

A prototype Lisp-based soft real-time object-oriented Graphical User Interface for control system development is presented. The Graphical User Interface executes alongside a test system in laboratory conditions to permit observation of the closed loop operation through animation, graphics, and text. Since it must perform interactive graphics while updating the screen in real time, techniques are discussed which allow quick, efficient data processing and animation. Examples from an implementation are included to demonstrate some typical functionalities which allow the user to follow the control system's operation.

Litt, Jonathan↗

The Automated Instrumentation and Monitoring System (AIMS) reference manual

Whether a researcher is designing the 'next parallel programming paradigm,' another 'scalable multiprocessor' or investigating resource allocation algorithms for multiprocessors, a facility that enables parallel program execution to be captured and displayed is invaluable. Careful analysis of execution traces can help computer designers and software architects to uncover system behavior and to take advantage of specific application characteristics and hardware features. A software tool kit that facilitates performance evaluation of parallel applications on multiprocessors is described. The Automated Instrumentation and Monitoring System (AIMS) has four major software components: a source code instrumentor which automatically inserts active event recorders into the program's source code before compilation; a run time performance-monitoring library, which collects performance data; a trace file animation and analysis tool kit which reconstructs program execution from the trace file; and a trace post-processor which compensate for data collection overhead. Besides being used as prototype for developing new techniques for instrumenting, monitoring, and visualizing parallel program execution, AIMS is also being incorporated into the run-time environments of various hardware test beds to evaluate their impact on user productivity. Currently, AIMS instrumentors accept FORTRAN and C parallel programs written for Intel's NX operating system on the iPSC family of multi computers. A run-time performance-monitoring library for the iPSC/860 is included in this release. We plan to release monitors for other platforms (such as PVM and TMC's CM-5) in the near future. Performance data collected can be graphically displayed on workstations (e.g. Sun Sparc and SGI) supporting X-Windows (in particular, Xl IR5, Motif 1.1.3).

Yan, Jerry↗

Summary of Differences in Approach to Executing the NGNP Project

The following discuss the summary differences between the NGNP Industry Alliance’s approach to execution of the NGNP Project as described in its Project Execution Strategy, and that included in the DOE’s Report to Congress on the Next Generation Nuclear Plant dated April 2010. These summary differences are not a comprehensive description of the results of a detailed gap analysis, but rather are those differences that warrant discussion in meetings between DOE executives and the private sector represented by the Alliance. In practical fact, the full range and content of the differences will not be understood until such time as detailed discussions are engaged between the DOE and the Alliance to develop a mutually agreed-to project execution plan.

42 ENGINEERING↗

The Rocket Balloon (Rocketball): Applications to Science, Technology, and Education

Originally envisioned to study upper atmospheric phenomena, the Rocket Balloon system (or Rocketball for short) has utility in a range of applications, including sprite detection and in-situ measurements, near-space measurements and calibration correlation with orbital assets, hurricane observation and characterization, technology testing and validation, ground observation, and education. A salient feature includes the need to reach space and near-space within a critical time-frame and in adverse local meteorological conditions. It can also provide for the execution of technology validation and operational demonstrations at a fraction of the cost of a space flight. In particular, planetary entry probe proof-of-concepts can be examined. A typical Rocketball operational scenario consists of a sounding rocket launch and subsequent deployment of a balloon above a desired location. An obvious advantage of this combination is the additional mission 'hang-time' rendered by the balloon once the sounding rocket flight is completed. The system leverages current and emergent technologies at the NASA Goddard Space Flight Center and other organizations.

Esper, Jaime↗

The University of Colorado OSO-8 spectrometer experiment. IV - Mission operations

The remote operation of two high-resolution ultraviolet spectrometers on the OSO-8 satellite is discussed. Mission operations enabled scientific observers to plan observations based on current solar data, interact with the observing program using real- or near real-time data and commands, evaluate quick-look instrument data, and analyze the observations for publication. During routine operations, experiments were planned a day prior to their execution, and the data from these experiments received a day later. When a shorter turnaround was required, a real-time mode was available. Here, the real-time data and command links into the remote control center were used to evaluate experiment operation and make satellite pointing or instrument configuration changes with a 1-90 minute turnaround.

Hansen, E. R.↗

Preparing Cassini Uplink Operations for Extended Mission

The Cassini-Huygens Mission to Saturn and Titan, a joint venture between the National Aeronautics and Space Administration, the European Space Agency, and the Italian Space Agency, is conducting a four-year, prime mission exploring the Saturnian system, including its atmosphere, rings, magnetosphere, moons and icy satellites. Launched in 1997, Cassini began its prime mission in 2004. Cassini is now preparing for a new era, a two-year extended mission to revisit many of the highlights and new discoveries made during the prime mission. Because of the light time delay from Earth to Saturn, and the time needed to coordinate the complicated science and engineering activities that take place on the spacecraft, commanding on Cassini is done in approximately 40-day intervals known as sequences. The Cassini Uplink Operations team is responsible for the final development and validation of the pointing profile and instrument and spacecraft commands that are contained in a sequence. During this final analysis prior to uplink to the spacecraft, thorough and exact evaluation is necessary to ensure there are no mistakes during commanding. In order to perform this evaluation, complete and refined processes and procedures are fundamental. The Uplink Operations team is also responsible for anomaly response during sequence execution, a process in which critical decisions often are made in real-time. Recent anomalies on other spacecraft missions have highlighted two major risks in the operations process: (1) personnel turnover and the retirement of critical knowledge and (2) aging, outdated operations procedures. If other missions are a good barometer, the Cassini extended mission will be presented with a high personnel turnover of the Cassini flight team, which could lead to a loss of expertise that has been essential to the success of the prime mission. In order to prepare the Cassini Uplink Operations Team for this possibility and to continue to develop and operate safe science and engineering sequences, a review and major update of the current documentation and operations procedures was needed. This paper will address the changes made to extended mission sequence generation processes primarily due to new restrictions in spacecraft operating capability and lessons learned from prime mission. In addition, it will address the state of the prime mission operations procedures, the philosophy changes and updates that were made to those procedures in response to process improvement, and the validation of those new procedures through the training of current and new personnel. And lastly, it will address the lessons learned throughout prime mission and how the Uplink Operations team chose to incorporate those lessons into the working documentation and team knowledge. This incorporation was necessary to facilitate the success of the extended mission with potentially all new personnel at some point prior to the end of the mission.

Maxwell, Jennifer L.↗

Replacement of Melter 2 at the Defense Waste Processing Facility (DWPF) - 18608

The original DWPF melter was replaced in 2002 with an identical unit, and radioactive operation of Melter 2 commenced in 2003. After nearly 14 years of service, a lower electrode failure of Melter 2 occurred in February 2017 which required its removal and replacement with Melter 3. The scope of the replacement outage involves several significant evolutions: - Shutdown of Melter 2 and placement into a safe state; - Remote external and internal inspection of Melter 2 to chronicle its condition prior to removal; - Disassembly and removal of Melter 2 from the process cell; - Placement of Melter 2 into a storage box and transport to a storage vault; - Preparation and initial testing of Melter 3 prior to transport to the DWPF; - Transport to the DWPF and installation of Melter 3 in the process cell; - Final startup testing and initiation of radioactive operation. Upon determination that repair of Melter 2 was not feasible, DWPF created an outage team to integrate schedules and resources needed to execute melter replacement as well as including maintenance scope for facility work that can only be performed when the melter is de-energized. The execution of this scope required integration with other mission critical outage activities already in progress, and planned to start, including initial facility tie-in scope for the new Salt Waste Processing Facility (SWPF). This unplanned addition of the melter replacement scope to the existing outage scope resulted in the longest facility outage period since the initiation of radioactive operations at the DWPF in 1996. Successful completion of this scope across all Liquid Waste facilities would require balance - for schedules, resources, priority, funding, etc. To overcome the significant challenges created by this additional scope, a WAR Room was established to ensure adequate integration and coordination of critical resources, and daily progress. The execution of this scope has required the integration of nearly two dozen work groups across multiple facilities at Savannah River Site (SRS), in addition to support from nearly a dozen vendors. The melter replacement outage was executed with a high degree of disciplined operation to ensure the facility was ready to resume glass pouring operation in time to support restart of the Liquid Waste program at the Savannah River Site (SRS). This paper will provide a brief overview of Melter 2 operational history. The execution of the removal and replacement operations will be described with a specific focus on lessons learned and opportunities where the outage execution diverged from the original Melter 1 replacement outage. It is expected to be of interest to vitrification facilities, as well as facilities, which require remote maintenance and replacement of large process equipment. (author)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Space Technology Mission Directorate Small Spacecraft Technology Program

The Small Spacecraft Technology (SST) program within NASA’s Space Technology Mission Directorate, expands the ability to execute unique missions through rapid development and demonstration of capabilities for small spacecraft applicable to exploration, science and the commercial space sector. Through targeted development and frequent in space testing, the program: • Enables execution of missions at much lower cost than previously possible • Substantially reduces the time required for development of spacecraft • Enables new mission architectures through the use of small spacecraft • Expands the reach of small spacecraft to new destinations and challenging new environments • Enables the augmentation of existing assets and future missions with supporting small spacecraft. The program achieves its objectives through: • Identification and investment in the development of new subsystem technologies to enhance or expand the capabilities of small spacecraft • Sponsorship of flight demonstrations of new technologies, capabilities and applications for small spacecraft • Promotion of the use of small spacecraft as platforms for testing and demonstrating technologies and capabilities that might have more general applications in larger-scale spacecraft and systems Program-funded projects may be executed at academic institutions, in the private sector, at NASA Centers, as public-private partnerships, or cooperative agreements.

Roger Hunter↗

NASA Small Spacecraft Technology (SST) Program - Recent and Upcoming Technology Demonstrations and Development Efforts

The Small Spacecraft Technology program within NASA’s Space Technology Mission Directorate, expands the ability to execute unique missions through rapid development and demonstration of capabilities for small spacecraft applicable to exploration, science, and the commercial space sector. Through targeted development and frequent in space testing, the program: • Enables execution of missions at much lower cost than previously possible • Substantially reduces the time required for development of spacecraft • Enables new mission architectures through the use of small spacecraft • Expands the reach of small spacecraft to new destinations and challenging new environments • Enables the augmentation of existing assets and future missions with supporting small spacecraft. The program achieves its objectives through: • Identification and investment in the development of new subsystem technologies to enhance or expand the capabilities of small spacecraft • Sponsorship of flight demonstrations of new technologies, capabilities and applications for small spacecraft • Promotion of the use of small spacecraft as platforms for testing and demonstrating technologies and capabilities that might have more general applications in larger-scale spacecraft and systems Program-funded projects may be executed at academic institutions, in the private sector, at NASA Centers, as public-private partnerships, or cooperative agreements.

SST↗

Space Technology Mission Directorate Small Spacecraft Technology

The Small Spacecraft Technology (SST) program within NASA’s Space Technology Mission Directorate, expands the ability to execute unique missions through rapid development and demonstration of capabilities for small spacecraft applicable to exploration, science and the commercial space sector. Through targeted development and frequent in space testing, the program: • Enables execution of missions at much lower cost than previously possible • Substantially reduces the time required for development of spacecraft • Enables new mission architectures through the use of small spacecraft • Expands the reach of small spacecraft to new destinations and challenging new environments • Enables the augmentation of existing assets and future missions with supporting small spacecraft. The program achieves its objectives through: • Identification and investment in the development of new subsystem technologies to enhance or expand the capabilities of small spacecraft • Sponsorship of flight demonstrations of new technologies, capabilities and applications for small spacecraft • Promotion of the use of small spacecraft as platforms for testing and demonstrating technologies and capabilities that might have more general applications in larger-scale spacecraft and systems [1] Program-funded projects may be executed at academic institutions, in the private sector, at NASA Centers, as public-private partnerships, or cooperative agreements.

Roger Hunter↗

Evolving from Planning and Scheduling to Real-Time Operations Support: Design Challenges

Versions of Scheduling and Planning Interface for Exploration (SPIFe) have supported a variety of mission operations across NASA. This software tool has evolved and matured over several years, assisting planners who develop intricate schedules. While initially conceived for surface Mars missions, SPIFe has been deployed in other domains, where people rather than robotic explorers, execute plans. As a result, a diverse set of end-users has compelled growth in a new direction: supporting real-time operations. This paper describes the new needs and challenges that accompany this development. Among the key features that have been built for SPIFe are current time indicators integrated into the interface and timeline, as well as other plan attributes that enable execution of scheduled activities. Field tests include mission support for the Lunar CRater Observation and Sensing Satellite (LCROSS), NASA Extreme Environment Mission Operations (NEEMO) and Desert Research and Technology Studies (DRATS) campaigns.

Marquez, Jessica J.↗