Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Generation 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 469 records · Page 26

Collaborative Arrival Planning: Data Sharing and User Preference Tools

Air traffic growth and air carrier economic pressures have motivated efforts to increase the flexibility of the air traffic management process and change the relationship between the air traffic control service provider and the system user. One of the most visible of these efforts is the U.S. government/industry "free flight" initiative, in which the service provider concentrates on safety and cross-airline fairness, and the user on their business objectives and operating preferences, including selecting their own path and speed in real-time. In the terminal arrival phase of flight, severe restrictions and rigid control are currently placed on system users, typically without regard for individual user operational preferences. Airborne delays applied to arriving aircraft into capacity constrained airports are imposed on a first-come, first-serve basis, and thus do not allow the system user to plan for or prioritize late arrivals, or to economically optimize their arrival sequence. A central tenant of the free-flight operating paradigm is collaboration between service providers and users in reaching air traffic management decisions. Such collaboration would be particularly beneficial to an airline's "hub" operation, where off-schedule arrival aircraft are a consistent problem, as they cause serious air-port ramp difficulties, rippling airline scheduling effects, and result in large economic inefficiencies. Greater collaboration can also lead to increased airport capacity and decrease the severity of over-capacity rush periods. In the NASA Collaborative Arrival Planning (CAP) project, both independent exchange of real-time data between the service provider and system user and collaborative decision support tools are addressed. Data exchange of real-time arrival scheduling, airspace management, and air carrier fleet data between the FAA service provider and an air carrier is being conducted and evaluated. Collaborative arrival decision support tools to allow intra-airline arrival preferences are being developed and simulated. The CAP project is part of and leveraged from the NASA/FAA Center TRACON Automation System (CTAS), a fielded set of decision support tools that provide computer generated advisories for both enroute and terminal area controllers to manage and control arrival traffic more efficiently. In this paper, the NASA Collaborative Arrival Planning project is outlined and recent results detailed, including the real-time use of CTAS arrival scheduling data by a major air carrier and simulations of tactical and strategic user preference decision support tools.

Zelenka, Richard E.↗

Run-time parallelization and scheduling of loops

The class of problems that can be effectively compiled by parallelizing compilers is discussed. This is accomplished with the doconsider construct which would allow these compilers to parallelize many problems in which substantial loop-level parallelism is available but cannot be detected by standard compile-time analysis. We describe and experimentally analyze mechanisms used to parallelize the work required for these types of loops. In each of these methods, a new loop structure is produced by modifying the loop to be parallelized. We also present the rules by which these loop transformations may be automated in order that they be included in language compilers. The main application area of the research involves problems in scientific computations and engineering. The workload used in our experiment includes a mixture of real problems as well as synthetically generated inputs. From our extensive tests on the Encore Multimax/320, we have reached the conclusion that for the types of workloads we have investigated, self-execution almost always performs better than pre-scheduling. Further, the improvement in performance that accrues as a result of global topological sorting of indices as opposed to the less expensive local sorting, is not very significant in the case of self-execution.

Saltz, Joel H.↗

Demonstration of a Spoken Dialogue Interface for Planning Activities of a Semi-autonomous Robot

Planning and scheduling in the face of uncertainty and change pushes the capabilities of both planning and dialogue technologies by requiring complex negotiation to arrive at a workable plan. Planning for use of semi-autonomous robots involves negotiation among multiple participants with competing scientific and engineering goals to co-construct a complex plan. In NASA applications this plan construction is done under severe time pressure so having a dialogue interface to the plan construction tools can aid rapid completion of the process. But, this will put significant demands on spoken dialogue technology, particularly in the areas of dialogue management and generation. The dialogue interface will need to be able to handle the complex dialogue strategies that occur in negotiation dialogues, including hypotheticals and revisions, and the generation component will require an ability to summarize complex plans. This demonstration will describe a work in progress towards building a spoken dialogue interface to the EUROPA planner for the purposes of planning and scheduling the activities of a semi-autonomous robot. A prototype interface has been built for planning the schedule of the Personal Satellite Assistant (PSA), a mobile robot designed for micro-gravity environments that is intended for use on the Space Shuttle and International Space Station. The spoken dialogue interface gives the user the capability to ask for a description of the plan, ask specific questions about the plan, and update or modify the plan. We anticipate that a spoken dialogue interface to the planner will provide a natural augmentation or alternative to the visualization interface, in situations in which the user needs very targeted information about the plan, in situations where natural language can express complex ideas more concisely than GUI actions, or in situations in which a graphical user interface is not appropriate.

Dowding, John↗

Improving the Operations of the Earth Observing One Mission via Automated Mission Planning

We describe the modeling and reasoning about operations constraints in an automated mission planning system for an earth observing satellite - EO-1. We first discuss the large number of elements that can be naturally represented in an expressive planning and scheduling framework. We then describe a number of constraints that challenge the current state of the art in automated planning systems and discuss how we modeled these constraints as well as discuss tradeoffs in representation versus efficiency. Finally we describe the challenges in efficiently generating operations plans for this mission. These discussions involve lessons learned from an operations model that has been in use since Fall 2004 (called R4) as well as a newer more accurate operations model operational since June 2009 (called R5). We present analysis of the R5 software documenting a significant (greater than 50%) increase in the number of weekly observations scheduled by the EO-1 mission. We also show that the R5 mission planning system produces schedules within 15% of an upper bound on optimal schedules. This operational enhancement has created value of millions of dollars US over the projected remaining lifetime of the EO-1 mission.

Chien, Steve A.↗

Testing to Transition the J-2X from Paper to Hardware

The J-2X Upper Stage Engine (USE) will be the first new human-rated upper stage engine since the Apollo program of the 1960s. It is designed to carry the Ares I and Ares V into orbit and send the Ares V to the Moon as part of NASA's Constellation Program. This paper will provide an overview of progress on the design, testing, and manufacturing of this new engine in 2009 and 2010. The J-2X embodies the program goals of basing the design on proven technology and experience and seeking commonality between the Ares vehicles as a way to minimize risk, shorten development times, and live within current budget constraints. It is based on the proven J-2 engine used on the Saturn IB and Saturn V launch vehicles. The prime contractor for the J-2X is Pratt & Whitney Rocketdyne (PWR), which is under a design, development, test, and engineering (DDT&E) contract covering the period from June 2006 through September 2014. For Ares I, the J-2X will provide engine start at approximately 190,000 feet, operate roughly 500 seconds, and shut down. For Ares V, the J-2X will start at roughly 190,000 feet to place the Earth departure stage (EDS) in orbit, shut down and loiter for up to five days, re-start on command and operate for roughly 300 seconds at its secondary power level to perform trans lunar injection (TLI), followed by final engine shutdown. The J-2X development effort focuses on four key areas: early risk mitigation, design risk mitigation, component and subassembly testing, and engine system testing. Following that plan, the J-2X successfully completed its critical design review (CDR) in 2008, and it has made significant progress in 2009 and 2010 in moving from the drawing board to the machine shop and test stand. Post-CDR manufacturing is well under way, including PWR in-house and vendor hardware. In addition, a wide range of component and sub-component tests have been completed, and more component tests are planned. Testing includes heritage powerpack, turbopump inducer water flow, turbine air flow, turbopump seal testing, main injector and gas generator, injector testing, augmented spark igniter testing, nozzle side loads cold flow testing, nozzle extension film cooling flow testing, control system testing with hardware in the loop, and nozzle extension emissivity coating tests. In parallel with hardware manufacturing, work is progressing on the new A-3 test stand to support full duration altitude testing. The Stennis A-2 test stand is scheduled to be turned over to the Constellation Program in September 2010 to be modified for J-2X testing also. As the structural steel was rising on the A-3 stand, work was under way in the nearby E complex on the chemical steam generator and subscale diffuser concepts to be used to evacuate the A-3 test cell and simulate altitude conditions.

Byrd, Tom↗

Garrett solar Brayton engine/generator status

The solar advanced gas turbine (SAGT-1) is being developed by the Garrett Turbine Engine Company, for use in a Brayton cycle power conversion module. The engine is derived from the advanced gas turbine (AGT101) now being developd by Garrett and Ford Motor Company for automotive use. The SAGT Program is presently funded for the design, fabrication and test of one engine at Garrett's Phoenix facility. The engine when mated with a solar receiver is called a power conversion module (PCU). The PCU is scheduled to be tested on JPL's test bed concentrator under a follow on phase of the program. Approximately 20 kw of electrical power will be generated.

Anson, B.↗

Lessons learned from the CSIS

A discussion is presented of the Centralized Storm Information System (CSIS), a joint effort by several organizations including NASA and the National Weather Service, which has been developed to aid the forecaster in evaluating weather data. The CSIS was developed to provide a handling, analyzing, intercomparison, and display system for real-time data from all available sources. The CSIS hardware and software, the impact of the CSIS, and the initial experience gained following the implementation of the CSIS are examined. Several general insights learned from this interactive processing system are examined in detail, including the benefits of an evolutionary bottom up rather than top down design approach, the crucial nature of scheduler function to any real time system, the recognition that meteorological interactive terminals requirements are different from image processing terminals requirements, and the knowledge that forecasters generate a large peak load on computer resources.

Mosher, F. R.↗

Generating Test Templates via Automated Theorem Proving

Testing can be used during the software development process to maintain fidelity between evolving specifications, program designs, and code implementations. We use a form of specification-based testing that employs the use of an automated theorem prover to generate test templates. A similar approach was developed using a model checker on state-intensive systems. This method applies to systems with functional rather than state-based behaviors. This approach allows for the use of incomplete specifications to aid in generation of tests for potential failure cases. We illustrate the technique on the cannonical triangle testing problem and discuss its use on analysis of a spacecraft scheduling system.

Kancherla, Mani Prasad↗

ACTS: Technology Description and Results

The ACTS Project was originated at NASA Glenn Research Center in the early 1980's to sponsor the development and application of technology that was intended to be used by the private sector. The program was formulated with the underlying philosophy of maintaining US leadership in satellite communications while focusing technology development for efficient use of the frequency spectrum. This report chronicles the execution and results of the program from the perspective of its technology managers, from inception through hardware and system development to on-orbit experiments and demonstrations of the technology. The first eight sections of the report discuss programmatic background, the specific satellite and ground terminal technology and the results generated by the program including industry relevance. A federally funded program of this type attracted strong advocates and adversaries and the resulting impact on the project schedule is also discussed. The last two sections are a list of useful acronyms and extensive references.

Gedney, Richard T.↗

Coded Modulation in C and MATLAB

This software, written separately in C and MATLAB as stand-alone packages with equivalent functionality, implements encoders and decoders for a set of nine error-correcting codes and modulators and demodulators for five modulation types. The software can be used as a single program to simulate the performance of such coded modulation. The error-correcting codes implemented are the nine accumulate repeat-4 jagged accumulate (AR4JA) low-density parity-check (LDPC) codes, which have been approved for international standardization by the Consultative Committee for Space Data Systems, and which are scheduled to fly on a series of NASA missions in the Constellation Program. The software implements the encoder and decoder functions, and contains compressed versions of generator and parity-check matrices used in these operations.

Hamkins, Jon↗

First Assessments of ICESat-2 Performance Using Aircraft Data

The Ice, Cloud, and land Elevation Satellite-2 (ICESat-2) Is a next-generation laser altimeter designed to continue key observations of ice sheet elevation change, sea ice freeboard, vegetation canopy height, earth surface elevation, and sea surface height. Scheduled for launch in early 2016, ICESat-2 will use a high repetition rate (approximately 10 kHz), small footprint (10m diameter) laser, and a single-photon-sensitive detection strategy (photon counting) to measure precise ranges to the earth's surface. Operating in the green (approximately 532nm), the six beams of ICESat-2 will provide improved spatial coverage compared with ICESat while the differences in transmit energy among the beams provide a large dynamic range. In order to evaluate models of predicted ICESat-2 performance, and provide ICESat-2-like data for algorithm development an airborne ICESat-2 simulator was developed and first flown in 2010, this simulator, the Multiple Altimeter Beam Experimental Lidar (MABEL) has now had three deployments in the western US, and will be deployed to the polar regions in spring of 2012. MABEL uses a similar measurement strategy to what will be used on ICESat-2. MABEL collects more spatially-dense data than ICESat-2 (approximately 2-cm along track) with a smaller 2m diameter footprint in 16 green channels and an additional 8 channels in the infrared. The comparison between frequencies allows for analysis of possible penetration of green energy into water or snow. We present MABEL data collected over deserts, forests, ocean water, lakes. snow covered mountains, and saft flats, provide examples of how these data are being used to develop algorithms that derive geophysical products from ICESat 2 and assess expected performances.

Neumann, Tom↗

First Assessments of Predicted ICESat-2 Performance Using Aircraft Data

The Ice, Cloud, and land Elevation Satellite-2 (ICESat-2) is a next-generation laser altimeter designed to continue key observations of ice sheet elevation change, sea ice freeboard, vegetation canopy height, earth surface elevation, and sea surface height. Scheduled for launch in mid-2016, ICESat-2 will use a high repetition rate (10 kHz), small footprint (10 m nominal ground diameter) laser, and a single-photon-sensitive detection strategy (photon counting) to measure precise range to the earth's surface. Using green light (532 nm), the six beams of ICESat-2 will provide improved spatial coverage compared with the single beam of ICESat, while the differences in transmit energy among the beams provide a large dynamic range. The six beams are arranged into three pairs of beams which allow slopes to measured on an orbit-by-orbit basis. In order to evaluate models of predicted ICESat-2 performance and provide ICESat-2-like data for algorithm development, an airborne ICESat-2 simulator was developed and first flown in 2010. This simulator, the Multiple Altimeter Beam Experimental Lidar (MABEL) was most recently deployed to Iceland in April 2012 and collected approx 85 hours of science data over land ice, sea ice, and calibration targets. MABEL uses a similar photon-counting measurement strategy to what will be used on ICESat-2. MABEL collects data in 16 green channels and an additional 8 channels in the infrared aligned across the direction of flight. By using NASA's ER-2 aircraft flying at 20km altitude, MABEL flies as close to space as is practical, and collects data through approx 95% of the atmosphere. We present background on the MABEL instrument, and data from the April 2012 deployment to Iceland. Among the 13 MABEL flights, we collected data over the Greenland ice sheet interior and outlet glaciers in the southwest and western Greenland, sea ice data over the Nares Strait and Greenland Sea, and a number of small glaciers and ice caps in Iceland and Svalbard. Several of the flights were coincident in time and space with NASA's Operation IceBridge, which provides an independent data set for validation. MABEL also collected data along CryoSat track 10482 in north central Greenland approximately one month after CryoSat passed overhead.

Neumann, Thomas↗

An Examination of Selected Datacom Options for the Near-Term Implementation of Trajectory Based Operations

A primary feature of the Next Generation Air Transportation System (NextGen) is trajectory based operations (TBO). Under TBO, aircraft flight plans are known to computer systems on the ground that aid in scheduling and separation. The Future Air Navigation System (FANS) was developed to support TBO, but relatively few aircraft in the US are FANSequipped. Thus, any near-term implementation must provide TBO procedures for non-FANS aircraft. Previous research has explored controller clearances, but any implementation must also provide procedures for aircraft requests. The work presented here aims to surface issues surrounding TBO communication procedures for non-FANS aircraft and for aircraft requesting deviations around weather. Three types of communication were explored: Voice, FANS, and ACARS,(Aircraft Communications Addressing and Reporting System). ACARS and FANS are datacom systems that differ in that FANS allows uplinked flight plans to be loaded into the Flight Management System (FMS), while ACARS delivers flight plans as text that must be entered manually via the Control Display Unit (CDU). Sixteen pilots (eight two-person flight decks) and four controllers participated in 32 20-minute scenarios that required the flight decks to navigate through convective weather as they approached their top of descents (TODs). Findings: The rate of non-conformance was higher than anticipated, with aircraft off path more than 20% of the time. Controllers did not differentiate between the ACARS and FANS datacom, and were mixed in their preference for Voice vs. datacom (ACARS and FANS). Pilots uniformly preferred Voice to datacom, particularly ACARS. Much of their dislike appears to result from the slow response times in the datacom conditions. As a result, participants frequently resorted to voice communication. These results imply that, before implementing TBO in environments where pilots make weather deviation requests, further research is needed to develop communication procedures that integrate voice and datacom.

trajectory based operations↗

CoCoSim, a Code Generation Framework for Control/command Applications: An Overview of CoCoSim for Multi-Periodic Discrete Simulink Models

We present CoCoSim, a framework to support the design, code generation and analysis of discrete dataflow model expressed in Simulink. In this work, we specifically focus on the analysis and code generation of multi-periodic systems. For that CoCoSim provides two complementary approaches: the first amounts to encode the multiperiodic semantics in a pure-synchronous one – à la Lustre–, enabling the use of model checker for verifying properties. The second provides a faithful code generation into multiple communicating (mono)synchronous components – à la Prelude– that can be then simulated or embedded in the final platform with any real-time scheduler. These approaches have been experimented in various settings.

Bourbouh, Hamza↗

Assessment of Crew Time for Maintenance and Repairs Activities for Lunar Surface Missions

NASA is currently evaluating different methods to predict how much time crewmembers will spend conducting repair and maintenance activities on future space missions. As mission scope and spacecraft architectures change, it will be necessary to understand how crew repair and maintenance timelines are impacted by mission operations and technology changes. Past work has been done using historical ISS data to accurately predict crew habitation and operation timelines, resulting in the development of NASA’s Exploration Crew Time Model (ECTM). However, understanding crew maintenance and repair requirements has posed a unique challenge due to the complexity of available datasets, the probabilistic nature of sub-system failures, and the impacts of reliability growth on failure rates. This paper presents a methodology to collect and condition empirical repair and maintenance time data from available data sets, to extrapolate from that data to estimate projected maintenance and repair times for a lunar Surface Habitat, and to assess how uncertainty in repair time could impact utilization time on the lunar surface. NASA International Space Station (ISS) maintenance and crew time data are logged into two central databases, the Maintenance Data Collection (MDC) and the Operations Planning Timeline Integration System (OPTimIS) respectively. Separately, each of these two datasets capture only portions of the complete set of data required to generate an accurate assessment of crew time spent on maintenance activities at a sub-system level. MDC provides a detailed catalog of failure events and an overview of the failure’s required maintenance and OPTimIS provides a description of crew activities and crew time durations dedicated to maintenance. To create a more useful crew time estimate for maintenance timelines, the authors developed a methodology to capture relevant data from each set and combine and utilize that data by linking crew time requirements to specific components. The authors compare the failure logs in the MDC to crew activity logs pulled from OPTimIS and then process the data to estimate required repair times for each failure event. Data is also classified by the outcome of each repair event, whether the failed component was replaced or whether it was repaired in place. The entire maintenance activity dataset is then categorized based on the class of failed component to allow for a statistically significant sample size for each class and to provide accurate crew time estimates for any components lacking relevant data. This resultant component repair time data can be used in the future to generate Mean Time To Repair (MTTR) estimates and confidence intervals for each class of component based on a probabilistic distribution of documented maintenance events. These improved MTTR values can then be applied to candidate element sub-system architectures, along with component Mean Time Between Failure (MTBF) data to generate distributions for potential required system crew repair time estimates for a given mission. Repair time distributions can then be used to develop more accurate crew schedules and to assess potential available utilization time.

Crew Time↗

Space Shuttle Main Engine (SSME) Options for the Future Shuttle

The main engines for the Future Shuttle will focus on improved safety and operability. Performance enhancements may also be required for vehicle safety purposes to achieve more desirable abort scenarios. This paper discusses the potential improvements that will be considered for implementation into the Future Shuttle. Integrated engine and vehicle health management systems will achieve additional system-level reliability improvements over those currently in development. Advanced instrumentation for detecting leaks, analyzing component wear and degradation, and providing sophisticated operational data will be used for reliable engine control and scheduling maintenance operations. A new nozzle and main combustion chamber (MCC) will reduce failure probability by 50% and allow for higher thrust capability without requiring the entire engine to be redesigned. Turbopump improvements may range from minor component improvements to using 3rd-generation pumps built on the advanced concepts demonstrated by the Integrated Powerhead Development (IPD) program and the Space Launch Initiative (SLI) prototype engines.The main engines for the Future Shuttle will focus on improved safety and operability. Performance enhancements may also be required for vehicle safety purposes to achieve more desirable abort scenarios. This paper discusses the potential improvements that will be considered for implementation into the Future Shuttle. Integrated engine and vehicle health management systems will achieve additional system-level reliability improvements over those currently in development. Advanced instrumentation for detecting leaks, analyzing component wear and degradation, and providing sophisticated operational data will be used for reliable engine control and scheduling maintenance operations. A new nozzle and main combustion chamber (MCC) will reduce failure probability by 50% and allow for higher thrust capability without requiring the entire engine to be redesigned. Turbopump improvements may range from minor component improvements to using 3rd-generation pumps built on the advanced concepts demonstrated by the Integrated Powerhead Development (IPD) program and the Space Launch Initiative (SLI) prototype engines.

Jue, Fred↗

The TechSat 21 Autonomous Sciencecraft Experiment

Software has been developed to perform a number of functions essential to autonomous operation in the Autonomous Sciencecraft Experiment (ASE), which is scheduled to be demonstrated aboard a constellation of three spacecraft, denoted TechSat 21, to be launched by the Air Force into orbit around the Earth in January 2006. A prior version of this software was reported in Software for an Autonomous Constellation of Satellites (NPO-30355), NASA Tech Briefs, Vol. 26, No. 11 (November 2002), page 44. The software includes the following components: Algorithms to analyze image data, generate scientific data products, and detect conditions, features, and events of potential scientific interest; A program that uses component-based computational models of hardware to analyze anomalous situations and to generate novel command sequences, including (when possible) commands to repair components diagnosed as faulty; A robust-execution-management component that uses the Spacecraft Command Language (SCL) software to enable event-driven processing and low-level autonomy; and The Continuous Activity Scheduling, Planning, Execution, and Replanning (CASPER) program for replanning activities, including downlink sessions, on the basis of scientific observations performed during previous orbit cycles.

Sherwood, Robert↗

Systems Engineering Approach to Technology Integration for NASA's 2nd Generation Reusable Launch Vehicle

The overall goal of the 2nd Generation RLV Program is to substantially reduce technical and business risks associated with developing a new class of reusable launch vehicles. NASA's specific goals are to improve the safety of a 2nd generation system by 2 orders of magnitude - equivalent to a crew risk of 1-in-10,000 missions - and decrease the cost tenfold, to approximately $1,000 per pound of payload launched. Architecture definition is being conducted in parallel with the maturating of key technologies specifically identified to improve safety and reliability, while reducing operational costs. An architecture broadly includes an Earth-to-orbit reusable launch vehicle, on-orbit transfer vehicles and upper stages, mission planning, ground and flight operations, and support infrastructure, both on the ground and in orbit. The systems engineering approach ensures that the technologies developed - such as lightweight structures, long-life rocket engines, reliable crew escape, and robust thermal protection systems - will synergistically integrate into the optimum vehicle. To best direct technology development decisions, analytical models are employed to accurately predict the benefits of each technology toward potential space transportation architectures as well as the risks associated with each technology. Rigorous systems analysis provides the foundation for assessing progress toward safety and cost goals. The systems engineering review process factors in comprehensive budget estimates, detailed project schedules, and business and performance plans, against the goals of safety, reliability, and cost, in addition to overall technical feasibility. This approach forms the basis for investment decisions in the 2nd Generation RLV Program's risk-reduction activities. Through this process, NASA will continually refine its specialized needs and identify where Defense and commercial requirements overlap those of civil missions.

Thomas, Dale↗