Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “executive”

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 199 records · Page 11

Symbolic Execution Enhanced System Testing

We describe a testing technique that uses information computed by symbolic execution of a program unit to guide the generation of inputs to the system containing the unit, in such a way that the unit's, and hence the system's, coverage is increased. The symbolic execution computes unit constraints at run-time, along program paths obtained by system simulations. We use machine learning techniques treatment learning and function fitting to approximate the system input constraints that will lead to the satisfaction of the unit constraints. Execution of system input predictions either uncovers new code regions in the unit under analysis or provides information that can be used to improve the approximation. We have implemented the technique and we have demonstrated its effectiveness on several examples, including one from the aerospace domain.

Davies, Misty D.↗

Predicting Operator Execution Times Using CogTool

Researchers and developers of NextGen systems can use predictive human performance modeling tools as an initial approach to obtain skilled user performance times analytically, before system testing with users. This paper describes the CogTool models for a two pilot crew executing two different types of a datalink clearance acceptance tasks, and on two different simulation platforms. The CogTool time estimates for accepting and executing Required Time of Arrival and Interval Management clearances were compared to empirical data observed in video tapes and registered in simulation files. Results indicate no statistically significant difference between empirical data and the CogTool predictions. A population comparison test found no significant differences between the CogTool estimates and the empirical execution times for any of the four test conditions. We discuss modeling caveats and considerations for applying CogTool to crew performance modeling in advanced cockpit environments.

Santiago-Espada, Yamira↗

Method and System for Controlling a Dexterous Robot Execution Sequence Using State Classification

A robotic system includes a dexterous robot and a controller. The robot includes a plurality of robotic joints, actuators for moving the joints, and sensors for measuring a characteristic of the joints, and for transmitting the characteristics as sensor signals. The controller receives the sensor signals, and is configured for executing instructions from memory, classifying the sensor signals into distinct classes via the state classification module, monitoring a system state of the robot using the classes, and controlling the robot in the execution of alternative work tasks based on the system state. A method for controlling the robot in the above system includes receiving the signals via the controller, classifying the signals using the state classification module, monitoring the present system state of the robot using the classes, and controlling the robot in the execution of alternative work tasks based on the present system state.

Sanders, Adam M.↗

Testing Flight Systems with Machine Executable Scripts

The MSAP project at JPL has been testing spacecraft avionics and flight software since 2005, in part using computer executable scripts. The scripts are document files of a common word processor and comply with the format of a traditional, formal test procedure common at JPL. These procedures use keywords to issue commands and evaluate responses, mimicking a human test operator. In effect, script lines are inserted into a normal procedure. Even though the executable structure of the procedures is limited to linear sequences of fairly simple operations, we have found significant value in certain test regimes given the repeatability, ease of execution, and readily understandable intent of these procedures.

Gibbs, Don↗

Evaluation of Crew-Centric Onboard Mission Operations Planning and Execution Tool: Year 2

Currently, mission planning for the International Space Station (ISS) is largely affected by ground operators in mission control. The task of creating a week-long mission plan for ISS crew takes dozens of people multiple days to complete, and is often created far in advance of its execution. As such, re-planning or adapting to changing real-time constraints or emergent issues is similarly taxing. As we design for future mission operations concepts to other planets or areas with limited connectivity to Earth, more of these ground-based tasks will need to be handled autonomously by the crew onboard.There is a need for a highly usable (including low training time) tool that enables efficient self-scheduling and execution within a single package. The ISS Program has identified Playbook as a potential option. It already has high crew acceptance as a plan viewer from previous analogs and can now support a crew self-scheduling assessment on ISS or on another mission. The goals of this work, a collaboration between the Human Research Program and the ISS Program, are to inform the design of systems for more autonomous crew operations and provide a platform for research on crew autonomy for future deep space missions. Our second year of the research effort have included new insights on the crew self-scheduling sessions performed by the crew through use on the HERA (Human Exploration Research Analog) and NEEMO (NASA Extreme Environment Mission Operations) analogs. Use on the NEEMO analog involved two self-scheduling strategies where the crew planned and executed two days of EVAs (Extra-Vehicular Activities). On HERA year two represented the first HERA campaign where we were able to perform research tasks. This involved selected flexible activities that the crew could schedule, mock timelines where the crew completed more complex planning exercises, usability evaluation of the crew self-scheduling features, and more insights into the limit of plan complexity that the crew could effectively self-schedule. In parallel we have added in new features and functionality in the Playbook tool based off of our insights from crew self-scheduling in the NASA analogs. In particular this year we have added in the ability for the crew to add, edit, and remove their own activities in the Playbook tool, expanding the type of planning and re-planning possible in the tool and opening up the ability for more free form plan creation. The ability to group and manipulate groups of activities from the plan task list was also added, allowing crew members to add predefined sets of activities onto their mission timeline. In addition we also added a way for crew members to roll back changes in their plan, in order to allow an undo like capability. These features expand and complement the initial self-scheduling features added in year one with the goal of making crew autonomous planning more efficient. As part of this work we have also finished developing the first version of our Playbook Data Analysis Tool, a research tool built to interpret and analyze the unobtrusively collected data obtained during the NASA analog missions through Playbook. This data which includes user click interaction as well as plan change information, through the Playbook Data Analysis Tool, allows us to playback this information as if a video camera was mounted over the crewmember's tablet. While the primary purpose of this tool is to allow usability analysis of crew self-scheduling sessions used on the NASA analog, since the data collected is structured, the tool can automatically derive metrics that would be traditionally tedious to achieve without manual analysis of video playback. We will demonstrate and discuss the ability for future derived metrics to be added to the tool. In addition to the current data and results gathered in year two we will also discuss the preparation and goals of our International Space Station (ISS) onboard technology demonstration with Playbook. This technology demonstration will be preformed as part of the CAST payload starting in late 2016.

onboard planning↗

The Role of Individual Differences in Executive Attentional Networks and Switching Choices in Multi-Task Management

Individual differences in cognitive processing relate to critical performance differences in real-world environments. Task switching is required for many of them and especially for task management during overload. Research exploring individual differences related to switching behavior (both frequency, and adherence to optimal switch times) is, however, sparse. We examined these relationships here, using the attentional network task to index executive control, and an ongoing tracking task (within a larger suite of concurrent task demands) to examine switching behavior. The results failed to support a general relationship between executive control and frequency in a complex, heterogeneous multi-task environment. However, higher executive control participants more successfully exploited optimal switching times, highlighting the varying role of individual differences in task management, when choice is unconstrained.

Gutzwiller, Robert S.↗

Cassini Maneuver Performance Assessment and Execution-Error Modeling Through 2015

In its twelfth year touring Saturn, the Cassini spacecraft continues to gather valuable scientific data about the planet and its moons. Cassini has executed a total of 331 propulsive maneuvers through January 23, 2016. With more than 30 maneuvers planned through July 2017 before the mission ends in September 2017, a dwindling propellant supply has become a chief concern. This manuscript will report on the analysis of Cassini maneuvers performed through December 30, 2015 and recommend execution-error models for the remainder of the mission. Maneuver performance assessment techniques and execution-error model development methods will also be outlined.

Wagner, Sean V.↗

Creating Systems Engineering Products with Executable Models in a Model-Based Engineering Environment

Applying systems engineering across the life-cycle results in a number of products built from interdependent sources of information using different kinds of system level analysis. This paper focuses on leveraging the Executable System Engineering Method (ESEM) which automates requirements verification (e.g. power and mass budget margins and duration analysis of operational modes) using executable SysML models. The particular value proposition is to integrate requirements, and executable behavior and performance models for certain types of system level analysis. The models are created with modeling patterns that involve structural, behavioral and parametric diagrams, and are managed by an open source Model Based Engineering Environment (named OpenMBEE). This paper demonstrates how the ESEM is applied in conjunction with OpenMBEE to create key engineering products (e.g. operational concept document) for the Alignment and Phasing System (APS) within the Thirty Meter Telescope (TMT) project, which is under development by the TMT International Observatory (TIO).

MBSE↗

Cassini Maneuver Performance Assessment and Execution-Error Modeling Through 2015

In its twelfth year touring Saturn, the Cassini spacecraft continues to gather valuable scientific data about the planet and its moons. Cassini has executed a total of 331 propulsive maneuvers through January 23, 2016. With more than 30 maneuvers planned through July 2017 before the mission ends in September 2017, a dwindling propellant supply has become a chief concern. This manuscript will report on the analysis of Cassini maneuvers performed through December 30, 2015 and recommend execution-error models for the remainder of the mission. Maneuver performance assessment techniques and execution-error model development methods will also be outlined.

Wagner, Sean V.↗

MEXEC: An Onboard Integrated Planning and Execution Approach for Spacecraft Commanding

The traditional form of spacecraft commanding is with sequences that specify when commands should execute based on a schedule generated on the ground. Some sequences have control logic and event driven responses to increase flexibility, but it is limited. An approach to increase autonomy is to use goal-based planning and commanding. Using this paradigm, intention and behavior is modeled on board the spacecraft. In this paper we describe MEXEC (Multi-mission EXECutive), a multi-mission, task-based, onboard planning and execution software designed specifically to be used as flight software. As a path to infusion for future flight projects, we describe two experiments performed on the ASTERIA CubeSat and testbed that demonstrate that MEXEC can be integrated and used for spacecraft operations and increase robustness and science return compared to the standard sequences that were being used.

Campuzano, Brian↗

The 7 Year Evolution of EOS CA Support for Planning & Executing Risk Mitigation Maneuvers

This presentation will discuss the evolution of Collision Avoidance (CA) support for planning and executing Risk Mitigation Maneuvers (RMMs) for the Earth Observing System (EOS) Aqua, Aura, and Terra satellites within the seven-year period of January 2015 through December 2021. Several enhancements were implemented by the EOS team to expedite and improve the RMM planning and execution process, including updates to High Interest Event (HIE) analysis, maneuver preparation, maneuver ephemeris generation, conjunction event data screening, and maneuver commanding. As of 2022, these advancements allow the EOS team to plan and execute an RMM within 5 hours of identification with an accurate and low-risk solution. This represents a vast improvement from the 30 hours required to turn around an RMM back in 2015. In addition, the current process is substantially less error prone. Details of this progression and the specific aspects of each supporting component are explicated in the content of the presentation.

Syed Hasan↗

Discrete Event Modeling and Massively Parallel Execution of Epidemic Outbreak Phenomena

In complex phenomena such as epidemiological outbreaks, the intensity of inherent feedback effects and the significant role of transients in the dynamics make simulation the only effective method for proactive, reactive or post-facto analysis. The spatial scale, runtime speed, and behavioral detail needed in detailed simulations of epidemic outbreaks make it necessary to use large-scale parallel processing. Here, an optimistic parallel execution of a new discrete event formulation of a reaction-diffusion simulation model of epidemic propagation is presented to facilitate in dramatically increasing the fidelity and speed by which epidemiological simulations can be performed. Rollback support needed during optimistic parallel execution is achieved by combining reverse computation with a small amount of incremental state saving. Parallel speedup of over 5,500 and other runtime performance metrics of the system are observed with weak-scaling execution on a small (8,192-core) Blue Gene / P system, while scalability with a weak-scaling speedup of over 10,000 is demonstrated on 65,536 cores of a large Cray XT5 system. Scenarios representing large population sizes exceeding several hundreds of millions of individuals in the largest cases are successfully exercised to verify model scalability.

99 GENERAL AND MISCELLANEOUS↗

Resilient Control System Execution Agent (ReCoSEA)

In an increasingly networked world, critical infrastructure systems suffer from two types of vulnerability. The first is the traditionally recognized problem of monitoring the systems for faults and failures, recognizing and analyzing data, and responding with real understanding to the problems of the system. Increasingly complex systems create the opportunity for single points of failure to cascade when inaccurate assessment of system health increases response time or leads to faulty analysis of the problems involved. A second problem involves vulnerability to cyber intrusion, in which bad actors can mask system deterioration or present false data about system status. A resilient system will protect stability, efficiency, and security. To ensure these three states, the system must react to changing conditions within the system with coordination: no one component of the system can be allowed to react to problems without real consideration of the effects of that action on other components within the system. Systems with multi-agent design typically have three layers of action, a management layer, a coordination layer, and an execution layer. A resilient multi-agent system will emphasize functions of the execution layer, which has the responsibility of initiating actions, monitoring, analyzing, and controlling its own processes, while feeding information back to the higher levels of management and coordination. The design concept of a resilient control system execution agent (ReCoSEA) grows out of these underpinnings, and through the use of computational intelligence techniques, this paper suggests an associated design methodology.

47 OTHER INSTRUMENTATION↗

VOLTTRON: An Agent Execution Platform for the Electric Power System

Volttron is an agent execution platform that is engineered for use in the electric power system. Volttron provides resource guarantees for agents and the platform including memory and processor utilization; authentication and authorization services; directory services for agent and resource location; and agent mobility. Unlike most other agent platforms, Volttron does not depend on a single agent authoring language. Instead, we chose to design and implement Volttron as a platform service and framework that is decoupled from the agent execution environment. A prototype implementation of Volttron has been written in Python (using Python v2.7.2) and we have executed agents written in Python and Java and as shell scripts. The intended use of Volttron is in the power distribution system for managing distributed generation, demand-response, and plug-in electric vehicles.

Multi-Agent Systems↗

Build and Execute Environment

At exascale, the challenge becomes to develop applications that run at scale and use exascale platforms reliably, efficiently, and flexibly. Workflows become much more complex because they must seamlessly integrate simulation and data analytics. They must include down-sampling, post-processing, feature extraction, and visualization. Power and data transfer limitations require these analysis tasks to be run in-situ or in-transit. We expect successful workflows will comprise multiple linked simulations along with tens of analysis routines. Users will have limited development time at scale and, therefore, must have rich tools to develop, debug, test, and deploy applications. At this scale, successful workflows will compose linked computations from an assortment of reliable, well-defined computation elements, ones that can come and go as required, based on the needs of the workflow over time. We propose a novel framework that utilizes both virtual machines (VMs) and software containers to create a workflow system that establishes a uniform build and execution environment (BEE) beyond the capabilities of current systems. In this environment, applications will run reliably and repeatably across heterogeneous hardware and software. Containers, both commercial (Docker and Rocket) and open-source (LXC and LXD), define a runtime that isolates all software dependencies from the machine operating system. Workflows may contain multiple containers that run different operating systems, different software, and even different versions of the same software. We will run containers in open-source virtual machines (KVM) and emulators (QEMU) so that workflows run on any machine entirely in user-space. On this platform of containers and virtual machines, we will deliver workflow software that provides services, including repeatable execution, provenance, checkpointing, and future proofing. We will capture provenance about how containers were launched and how they interact to annotate workflows for repeatable and partial re-execution. We will coordinate the physical snapshots of virtual machines with parallel programming constructs, such as barriers, to automate checkpoint and restart. We will also integrate with HPC-specific container runtimes to gain access to accelerators and other specialized hardware to preserve native performance. Containers will link development to continuous integration. When application developers check code in, it will automatically be tested on a suite of different software and hardware architectures.

Guan, Qiang↗

Using redundant transactions to verify the correctness of program code execution

In the described embodiments, a processor core (e.g., a GPU core) receives a section of program code to be executed in a transaction from another entity in a computing device. The processor core sends the section of program code to one or more compute units in the processor core to be executed in a first transaction and concurrently executed in a second transaction, thereby creating a “redundant transaction pair.” When the first transaction and the second transaction are completed, the processor core compares a read-set of the first transaction to a read-set of the second transaction and compares a write-set of the first transaction to a write-set of the second transaction. When the read-sets and the write-sets match and no transactional error condition has occurred, the processor core allows results from the first transaction to be committed to an architectural state of the computing device.

Gurumurthi, Sudhanva↗

Heterogeneous graphics processing unit for scheduling thread groups for execution on variable width SIMD units

A compute unit configured to execute multiple threads in parallel is presented. The compute unit includes one or more single instruction multiple data (SIMD) units and a fetch and decode logic. The SIMD units have differing numbers of arithmetic logic units (ALUs), such that each SIMD unit can execute a different number of threads. The fetch and decode logic is in communication with each of the SIMD units, and is configured to assign the threads to the SIMD units for execution based on such differing numbers of ALUs.

97 MATHEMATICS AND COMPUTING↗

Back from the Brink with Something for Everyone - The Final Executed Memorandum of Agreement for Interpretation of the East Tennessee Technology Park and the K-25 Building - 13370

When the Environmental Management (EM) Program at the Oak Ridge Office of the Department of Energy (DOE) began its major decontamination and decommissioning (D and D) program activities in the mid-1990's, it was understood that the work to demolish the gaseous diffusion process buildings at the K-25 Site, as it was then known, would be challenging. Nothing of that size and breadth had ever been done within the DOE complex and the job brought about a full menu of unique attributes: radiological contamination with enriched materials entrained in certain areas of the system, a facility that was never designed not to operate but had been shut down since 1964, and a loyal following of individuals and organizations who were committed to the physical preservation of at least some portion of the historic Manhattan Project property. DOE was able to solve and resolve the issues related to nuclear materials management, contamination control, and determining the best way to safely and efficiently deconstruct the massive building. However, for a variety of reasons, resolution of the historic preservation questions - what and how much to preserve, how to preserve it, where to preserve it, how to interpret it, how much to spend on preservation, and by and for whom preservation should occur - remained open to debate for over a decade. After a dozen years, countless meetings, phone calls, discussions and other exchanges, and four National Historic Preservation Act (NHPA) [1] Memoranda of Agreement (MOA), a final MOA [2] has been executed. The final executed MOA's measures are robust, creative, substantive, and will be effective. They include a multi-story replica of a portion of the K-25 Building, the dedication of the K-25 Building footprint for preservation purposes, an equipment building to house authentic Manhattan Project and Cold War equipment, a virtual museum, an on-site history center, a grant to preserve a historically-significant Manhattan Project-era hotel in Oak Ridge, and more. The MOA was designed to offer something for everyone. The MOA for the K- 25 Building and interpretation of the East Tennessee Technology Park (ETTP; formerly the K-25 Site) was executed by all of the signatory parties on August 7, 2012 - almost 67 years to-the-day after the 'product' of the K-25 process building became known to more than just a small group of scientists and engineers working on a secret project for the Army Corps of Engineers Manhattan District. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗