Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Task scheduling”

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 631 records · Page 35

STS-109 Crew Interview: Grunsfeld

STS-109 Payload Commander John Grunsfeld is seen during a prelaunch interview answering questions about his inspiration to become an astronaut and his career path. He gives details on the mission's goal (which is to service the Hubble Space Telescope (HST)), his role during the mission, the five scheduled spacewalks, the Columbia Orbiter's recent upgrades, and what he sees as the challenges of the mission. Grunsfeld describes how his experience on the STS-103 mission, a previous HST servicing mission, has helped prepare him for the STS-109 mission. The interview ends with Grunsfeld explaining why the servicing of the Reaction Wheel Assembly, a task added late in his training, is so important.

Source record↗

Habitable Mars Ascent Vehicle (MAV) Concept

NASA's ultimate goal is the human exploration of Mars. Among the many difficult aspects of a trip to Mars is the return mission that would transport the astronauts from the Martian surface back into Mars orbit. One possible conceptual design to accomplish this task is a two-stage Mars Ascent Vehicle (MAV). In order to assess this design, a general layout and configuration for the spacecraft must be developed. The objective of my internship was to model a conceptual MAV design to support NASA's latest human Mars mission architecture trade studies, technology prioritization decisions, and mass, cost, and schedule estimates.

Dang, Victor↗

Wind Information Uplink to Aircraft Performing Interval Management Operations

Interval Management (IM) is an ADS-B-enabled suite of applications that use ground and flight deck capabilities and procedures designed to support the relative spacing of aircraft (Barmore et al., 2004, Murdoch et al. 2009, Barmore 2009, Swieringa et al. 2011; Weitz et al. 2012). Relative spacing refers to managing the position of one aircraft to a time or distance relative to another aircraft, as opposed to a static reference point such as a point over the ground or clock time. This results in improved inter-aircraft spacing precision and is expected to allow aircraft to be spaced closer to the applicable separation standard than current operations. Consequently, if the reduced spacing is used in scheduling, IM can reduce the time interval between the first and last aircraft in an overall arrival flow, resulting in increased throughput. Because IM relies on speed changes to achieve precise spacing, it can reduce costly, low-altitude, vectoring, which increases both efficiency and throughput in capacity-constrained airspace without negatively impacting controller workload and task complexity. This is expected to increase overall system efficiency. The Flight Deck Interval Management (FIM) equipment provides speeds to the flight crew that will deliver them to the achieve-by point at the controller-specified time, i.e., assigned spacing goal, after the target aircraft crosses the achieve-by point (Figure 1.1). Since the IM and target aircraft may not be on the same arrival procedure, the FIM equipment predicts the estimated times of arrival (ETA) for both the IM and target aircraft to the achieve-by point. This involves generating an approximate four-dimensional trajectory for each aircraft. The accuracy of the wind data used to generate those trajectories is critical to the success of the IM operation. There are two main forms of uncertainty in the wind information used by the FIM equipment. The first is the accuracy of the forecast modeling done by the weather provider. This is generally a global environmental prediction obtained from a weather model such as the Rapid Refresh (RAP) from the National Centers for Environmental Prediction (NCEP). The weather forecast data will have errors relative to the actual, or truth, winds that the aircraft will encounter. The second source of uncertainty is that only a small subset of the forecast data can be uplinked to the aircraft for use by the FIM equipment. This results in loss of additional information. The Federal Aviation Administration (FAA) and RTCA are currently developing standards for the communication of wind and atmospheric data to the aircraft for use in NextGen operations. This study examines the impact of various wind forecast sampling methods on IM performance metrics to inform the standards development.

Ahmad, Nashat N.↗

Rise and Shine: Using Light as a Countermeasure to Sleep Inertia

INTRODUCTION: Sleep inertia describes the phenomenon of sleepiness and poor performance experienced after waking from sleep. This period of impaired alertness and performance is of significant concern to workers who nap on shift, or work on-call and are required to perform safety-critical tasks soon after waking (e.g., emergency services, healthcare, military). Light has been shown to acutely improve alertness during sleep deprivation and circadian misalignment. In this study, we assessed the efficacy of blue-enriched light to improve alertness and mood immediately after waking from SWS, i.e., during the sleep inertia period. METHODS: Twelve participants kept a sleep schedule of 8.5 h for 5 nights and 5 h for one night prior to the overnight laboratory visit (confirmed by actigraphy). Participants went to bed at their scheduled habitual bedtime in the laboratory and were monitored by standard polysomnography. After at least 5 min of SWS, participants were awoken and exposed to either red ambient light (control) or blue-enriched light (light) for 1 h. During this time, participants completed a subjective scale of alertness (Karolinska Sleepiness Scale, KSS) and visual analogue scales (VAS) of mood at 2 min, 17 min, 32 min, and 47 min after waking. Following this sleep inertia measurement period, all lights were turned off and participants were allowed to return to sleep. They were then awoken again from their subsequent SWS period and exposed to the opposite condition (control or light). A linear mixed-effects model with fixed effects of condition, time, and condition*time and a random effect of participant was used to determine the impact of light across the testing period. An average of baseline responses (pre-sleep) was included as a covariate. RESULTS: Compared to the control condition, participants exposed to blue-enriched light reported feeling more alert (KSS: F1,77=4.955, p=.029; VASalert: F1,77=8.226, p=.005), more cheerful (VAScheerful: F1,77=8.615, p=.004), less depressed (VASdepressed: F1,77=4.649, p=.034), and less lethargic (VASlethargic: F1,77=5.652, p=.020). DISCUSSION: Exposure to blue-enriched light immediately after waking from SWS may help to improve subjective alertness and mood. Future analyses will explore whether these findings extend to effects on cognitive performance. This countermeasure to sleep inertia may be suitable for implementation to alert crew members during mid-sleep emergencies but requires further testing in field settings.

alertness↗

Is "Sleepy Supervision" the New "Drowsy Driving"?

Human error has been implicated as a causal factor in a large proportion of road accidents. Automated driving systems purport to mitigate this risk, but self-driving systems that allow a driver to entirely disengage from the driving task also require the driver to monitor the environment and take control when necessary. Given that sleep loss impairs monitoring performance and there is a high prevalence of sleep deficiency in modern society, we hypothesized that supervising a self-driving vehicle would unmask latent sleepiness compared to manually controlled driving among individuals following their typical sleep schedules. We found that participants felt sleepier, had more involuntary transitions to sleep, had slower reaction times and more attentional failures, and showed substantial modifications in brain synchronization during and following an autonomous drive compared to a manually controlled drive. Our findings suggest that the introduction of partial self-driving capabilities in vehicles has the potential to paradoxically increase accident risk.

sleepiness↗

Report of the Defense Science Board Task Force on National Aero-Space Plane (NASP) Program

Six years ago, the Defense Science Board (DSB) initiated a review of the concept, technical basis, program content, and missions of the National Aerospace Plane (NASP) program. The report was completed in Sep. 1988, and the recommendations contributed to strengthening the technical efforts in the NASP program. Since then, substantial technological progress has been made in the technology development phase (Phase 2) of the program. Phase 2 of the program is currently scheduled to end in late Fiscal Year 1993, with a decision whether to proceed to the experimental flight vehicle phase (Phase 3) to be made at that time. This decision will be a very significant one for the Department of Defense (DoD) and the National Aeronautics and Space Administration (NASA). In February of this year, the DSB was chartered to revisit the NASP program to assess the degree to which the many technical challenges of the program have been resolved, or are likely to be resolved by the end of Phase 2.

Source record↗

Behavioral technology and its application to fire toxicology research

The application of behavioral technology to the toxicity testing of pyrolysis/combustion (P/C) products is discussed and two categories of behavioral tests commonly employed in fire toxicology programs are reviewed. Data are presented from a comparison of carbon monoxide (CO) induced incapacitation in rats performing in a rotating wheel or under a Sidmon free-operant schedule of shock avoidance. Rats performing in the rotating wheel were behaviorally incapacitated at CO concentrations and carboxyhemoglobin levels significantly lower than those which incapacitated operant avoidance animals. It is concluded that different measures of behavioral incapacitation may vary since incapacitation is a function of the particular toxic mechanism at work and the behavioral requirements of the specific task employed in the test procedure.

Russo, D. M.↗

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗

Impact of Data Exchange Provided by ATD2 Tools at Charlotte-Douglas International Airport

Data Exchange and Integration is necessary for progress towards an Integrated Arrival, Departure, and Surface (IADS) traffic management capability. In collaboration with the FAA, NASA has introduced new data exchange elements to Charlotte-Douglas International Airport air traffic facilities, including the American Airlines ramp, as part of the Airspace Technology Demonstration 2 (ATD2). This paper describes the new tools that deliver these elements, and the human factors impact of the tools as measured by post-bank surveys. Workload was unaffected by ATD2 tool use, and situational awareness was improved in the Tower and with Ramp controllers in the second round of surveys. Respondents described their tools as more helpful if they included ATD2 tools 1) in the Tower for insuring compliance for aircraft under a Traffic Management Initiative, 2) in the TRACON when actively used for many TRACON tasks, and 3) in the Ramp in the second round of surveys.

and surface traffic management; human factors asse↗

Space-based multifunctional end effector systems functional requirements and proposed designs

The end effector is an essential element of teleoperator and telerobot systems to be employed in space in the next decade. The report defines functional requirements for end effector systems to perform operations that are currently only feasible through Extra-Vehicular Activity (EVA). Specific tasks and functions that the end effectors must be capable of performing are delineated. Required capabilities for forces and torques, clearances, compliance, and sensing are described, using current EVA requirements as guidelines where feasible. The implications of these functional requirements on the elements of potential end effector systems are discussed. The systems issues that must be considered in the design of space-based manipulator systems are identified; including impacts on subsystems tightly coupled to the end effector, i.e., control station, information processing, manipulator arm, tool and equipment stowage. Possible end effector designs are divided into three categories: single degree-of-freedom end effectors, multiple degree of freedom end effectors, and anthropomorphic hands. Specific design alternatives are suggested and analyzed within the individual categories. Two evaluations are performed: the first considers how well the individual end effectors could substitute for EVA; the second compares how manipulator systems composed of the top performers from the first evaluation would improve the space shuttle Remote Manipulator System (RMS) capabilities. The analysis concludes that the anthropomorphic hand is best-suited for EVA tasks. A left- and right-handed anthropomorphic manipulator arm configuration is suggested as appropriate to be affixed to the RMS, but could also be used as part of the Smart Front End for the Orbital Maneuvering Vehicle (OMV). The technical feasibility of the anthropomorphic hand and its control are demonstrated. An evolutionary development approach is proposed and approximate scheduling provided for implementing the suggested manipulator systems in time for space stations operations in the early 1990s.

Mishkin, A. H.↗

A software tool for dataflow graph scheduling

A graph-theoretic design process and software tool is presented for selecting a multiprocessing scheduling solution for a class of computational problems. The problems of interest are those that can be described using a dataflow graph and are intended to be executed repetitively on multiple processors. The dataflow paradigm is very useful in exposing the parallelism inherent in algorithms. It provides a graphical and mathematical model which describes a partial ordering of algorithm tasks based on data precedence.

Jones, Robert L., III↗

Affordable Development and Demonstration of a Small Nuclear Thermal Rocket (NTR) Engine and Stage: How Small Is Big Enough?

The Nuclear Thermal Rocket (NTR) derives its energy from fission of uranium-235 atoms contained within fuel elements that comprise the engine's reactor core. It generates high thrust and has a specific impulse potential of approximately 900 specific impulse - a 100 percent increase over today's best chemical rockets. The Nuclear Thermal Propulsion (NTP) project, funded by NASA's Advanced Exploration Systems (AES) program, includes five key task activities: (1) Recapture, demonstration, and validation of heritage graphite composite (GC) fuel (selected as the Lead Fuel option); (2) Engine Conceptual Design; (3) Operating Requirements Definition; (4) Identification of Affordable Options for Ground Testing; and (5) Formulation of an Affordable Development Strategy. During fiscal year (FY) 2014, a preliminary Design Development Test and Evaluation (DDT&E) plan and schedule for NTP development was outlined by the NASA Glenn Research Center (GRC), Department of Energy (DOE) and industry that involved significant system-level demonstration projects that included Ground Technology Demonstration (GTD) tests at the Nevada National Security Site (NNSS), followed by a Flight Technology Demonstration (FTD) mission. To reduce cost for the GTD tests and FTD mission, small NTR engines, in either the 7.5 or 16.5 kilopound-force thrust class, were considered. Both engine options used GC fuel and a common fuel element (FE) design. The small approximately 7.5 kilopound-force criticality-limited engine produces approximately157 thermal megawatts and its core is configured with parallel rows of hexagonal-shaped FEs and tie tubes (TTs) with a FE to TT ratio of approximately 1:1. The larger approximately 16.5 kilopound-force Small Nuclear Rocket Engine (SNRE), developed by Los Alamos National Laboratory (LANL) at the end of the Rover program, produces approximately 367 thermal megawatts and has a FE to TT ratio of approximately 2:1. Although both engines use a common 35-inch (approximately 89-centimeters) -long FE, the SNRE's larger diameter core contains approximately 300 more FEs needed to produce an additional 210 thermal megawatts of power. To reduce the cost of the FTD mission, a simple one-burn lunar flyby mission was considered to reduce the liquid hydrogen (LH2) propellant loading, the stage size and complexity. Use of existing and flight proven liquid rocket and stage hardware (e.g., from the RL10B-2 engine and Delta Cryogenic Second Stage) was also maximized to further aid affordability. This paper examines the pros and cons of using these two small engine options, including their potential to support future human exploration missions to the Moon, near Earth asteroids (NEA), and Mars, and recommends a preferred size. It also provides a preliminary assessment of the key activities, development options, and schedule required to affordably build, ground test and fly a small NTR engine and stage within a 10-year timeframe.

Spacecraft design↗

Assessment of Scheduling and Plan Execution of Apollo 14 Lunar Surface Operations

Although over forty years have passed since first landing on the Moon, there is not yet a comprehensive, quantitative assessment of Apollo extravehicular activities (EVAs). Quantitatively evaluating lunar EVAs will provide a better understanding of the challenges involved with surface operations. This first evaluation of a surface EVA centers on comparing the planned and the as-ran timeline, specifically collecting data on discrepancies between durations that were estimated versus executed. Differences were summarized by task categories in order to gain insight as to the type of surface operation activities that were most challenging. One Apollo 14 EVA was assessed utilizing the described methodology. Selected metrics and task categorizations were effective, and limitations to this process were identified.

Marquez, Jessica J.↗

Real-Time MENTAT programming language and architecture

Real-time MENTAT, a programming environment designed to simplify the task of programming real-time applications in distributed and parallel environments, is described. It is based on the same data-driven computation model and object-oriented programming paradigm as MENTAT. It provides an easy-to-use mechanism to exploit parallelism, language constructs for the expression and enforcement of timing constraints, and run-time support for scheduling and exciting real-time programs. The real-time MENTAT programming language is an extended C++. The extensions are added to facilitate automatic detection of data flow and generation of data flow graphs, to express the timing constraints of individual granules of computation, and to provide scheduling directives for the runtime system. A high-level view of the real-time MENTAT system architecture and programming language constructs is provided.

Grimshaw, Andrew S.↗

A rule-based shell to hierarchically organize HST observations

An observing program on the Hubble Space Telescope (HST) is described in terms of exposures that are obtained by one or more of the instruments onboard the HST. These exposures are organized into a hierarchy of structures for purposes of efficient scheduling of observations. The process by which exposures get organized into the higher-level structures is called merging. This process relies on rules to determine which observations can be 'merged' into the same higher level structure, and which cannot. The TRANSformation expert system converts proposals for astronomical observations with HST into detailed observing plans. The conversion process includes the task of merging. Within TRANS, we have implemented a declarative shell to facilitate merging. This shell offers the following features: (1) an easy way of specifying rules on when to merge and when not to merge, (2) a straightforward priority mechanism for resolving conflicts among rules, (3) an explanation facility for recording the merging history, (4) a report generating mechanism to help users understand the reasons for merging, and (5) a self-documenting mechanism that documents all the merging rules that have been defined in the shell, ordered by priority. The merging shell is implemented using an object-oriented paradigm in CLOS. It has been a part of operational TRANS (after extensive testing) since July 1993. It has fulfilled all performance expectations, and has considerably simplified the process of implementing new or changed requirements for merging. The users are pleased with its report-generating and self-documenting features.

Bose, Ashim↗

The Joint Confidence Level Paradox: A History of Denial

This paper is intended to provide a reliable methodology for those tasked with generating price tags on construction (C0F) and research and development (R&D) activities in the NASA performance world. This document consists of a collection of cost-related engineering detail and project fulfillment information from early agency days to the present. Accurate historical detail is the first place to start when determining improved methodologies for future cost and schedule estimating. This paper contains a beneficial proposed cost estimating method for arriving at more reliable numbers for future submits. When comparing current cost and schedule methods with earlier cost and schedule approaches, it became apparent that NASA's organizational performance paradigm has morphed. Mission fulfillment speed has slowed and cost calculating factors have increased in 21st Century space exploration.

Butts, Glenn↗

Effectiveness of Redundant Communications Systems in Maintaining Operational Control of Small Unmanned Aircraft

NASA has been researching prototype technologies for an Unmanned Aircraft System (UAS) Traffic Management (UTM) system to facilitate enabling of safe and efficient civilian low-altitude airspace and UAS operations, in a series of Technical Capability Levels (TCL) activities that are increasingly complex. In TCL1, completed in 2015, visual line-of-sight operations such as agriculture, firefighting and infrastructure monitoring were addressed with a focus on geofencing and operations scheduling. Technologies and requirements needed for beyond visual line-of-sight (BVLOS) operations in sparsely populated areas were examined in TCL2 in 2016, and those for operations over moderately populated areas in TCL3 in 2017 and 2018. TCL4 will build on the earlier TCLs and focus on technologies and requirements for operations in higher-density urban areas for tasks such as news gathering, package delivery and for managing large-scale contingencies. This paper describes a communications test conducted in TCL3 and discusses insights gained from the test. In the test, operators were directed to equip UAS with redundant Command and Control (C2) communications systems, send a maneuver command to Unmanned Aircraft (UA) via the primary system, then verify execution of the sent command. This exercise was repeated with each redundant system. The test was designed to assess effectiveness of redundant C2 systems in maintaining operational control of UA. Several UAS were configured with varying arrangements to achieve redundancy, including two identical radio modems using the same frequency band, WiFi and Long-Term Evolution (LTE) cellular modems, etc. From the test, digital data such as time maneuver command sent, time maneuver verified, etc., were collected. Descriptions of methods to detect loss of C2 communications and contingency steps for such event were collected and assessed. The final paper will include a detailed analysis of the collected data leading to the following insights. First, effectiveness of redundant C2 systems depends on several factors, such as operational environment and communications service availability. For example, use of two identical point-to-point radio to connect operator and UA on the same frequency band can be effective in mitigating radio malfunction when operating in an environment where possibility of Radio Frequency (RF) interference is low, such as over open plains. However, the same arrangement may not be effective where high level of RF transmissions in broad spectrum ranges can be expected, such as over or near urban areas. For redundant systems that consist of external communications services, such as cellular and satellite communications network, redundancy is maintained only in the areas where more than one services are available. Therefore, UAS operators should have the means to plan for and monitor the performance of external communications services they are relying on to control UA. Second, communications performance needs, such as the minimum data transfer rate and the maximum tolerable latency, should be assessed to reflect the potential hazard that can come from loss of UA control. For example, UA operations over desolate area pose less hazard to people than operations over densely populated area and performance need for the former would be less than the latter.

Jung, Jaewoo↗

Surface Systems Capability Gaps for Enabling NASA’s Sustainable Lunar Operations

This paper discusses the NASA Ground, Test, and Surface Systems Taxonomy (TX-13) related capability gaps, including details of architecture, technology, engineering, and policy gaps for enabling sustainable lunar surface operations and subsequent Mars missions. Architecture gaps include standardized architectures and interfaces, multi-element systems engineering and integration, design for supportability, and nuclear payload processing and launch approach. Technology gaps, primarily focused on uncrewed surface operations, include automated/autonomous cryogenic loading, transfer, servicing, and storage of commodities; health determination and fault management; automated/autonomous planning and scheduling; automated/autonomous inspection, maintenance and repair; logistics management and reliability; launch and landing site preparation; commodity management; and advanced umbilicals and dust tolerant interfaces. Engineering gaps include high-purity propellant production for ground and surface applications and large-scale xenon servicing capabilities. The policy gap includes nuclear propulsion acceptance testing and qualification approach. Strategically identifying human/automation roles and tasks and infusing automation and autonomy practices early in a system’s lifecycle is essential for achieving the mission objectives for a sustainable human lunar presence, improving performance and mission effectiveness, reducing operations costs and reliance on humans to perform tasks, and accommodating ground communication delays.

Surface Systems↗