Search NASA⌕ Search

SEARCH · Search NASA

Results for “task programming”

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 955 records · Page 53
All sourcesNASA NTRSDOE OSTI
NASA NTRS1981

Process development for automated solar cell and module production. Task 4: Automated array assembly

The Unimate robot was programmed for the final 35 cell pattern to be used in the fabrication of the deliverable modules. Mechanical construction of the Automated Lamination Station and Final Assembly Station were completed on schedule. All final wiring and interconnect cables were also completed and the first operational testing began. The final controlling program was written. A local fabricator was contracted to produce the glass reinforced concrete panels to be used for testing and deliverables. A video tape showing all three stations in operation was produced.

Hagerty, J. J.↗
NASA NTRS1992

Design for a complete SOHO mission under the ISTP

The Solar and Heliospheric Observatory (SOHO) occupies a crucial slot in the International Solar Terrestrial Physics (ISTP) program, which investigates the energy and material flows in key regions of the geospace. Prior space missions which have brought understanding of the corona to what it is today are reviewed. Similarly, space science programs on the horizon will build on SOHO discoveries and insights. SOHO program structure and cost control methods are sketched; tasks have been transferred off the spacecraft where possible, and capabilities will be delivered just before needed. The team analyses of data will be augmented by a SOHO guest investigator program after launch. Theorists on teams would similarly be joined by participants in a proposed SOHO theory program. The ISTP program is built on a foundation of collaborative science, implying the need for observational campaigns directed from a user friendly operations center.

Wagner, W. J.↗
NASA NTRS1988

KALI - An environment for the programming and control of cooperative manipulators

A design description is given of a controller for cooperative robots. The background and motivation for multiple arm control are discussed. A set of programming primitives which permit a programmer to specify cooperative tasks are described. Motion primitives specify asynchronous motions, master/slave motions, and cooperative motions. In the context of cooperative robots, trajectory generation issues are discussed and the authors' implementation briefly described. The relations between programming and control in the case of multiple robots are examined. The allocation of various tasks among a multiprocessor computer is described.

Hayward, Vincent↗
NASA NTRS1985

Analysis of Spiral Bevel Gearing

Program generalized for automated finite-element-method model generation. Tedious task of finite-element-method (FEM) model preparation greatly reduced by development of preprocessing program for automated model generation. Utility of program, including ability to rapidly evaluate parametric changes, demonstrated for spiral, helical, and spiral bevel gearing. Postprocessing program also developed, aids in review and interpretation of calculated FEM stresses.

Drago, R. J.↗
NASA NTRS1995

Using an architectural approach to integrate heterogeneous, distributed software components

Many computer programs cannot be easily integrated because their components are distributed and heterogeneous, i.e., they are implemented in diverse programming languages, use different data representation formats, or their runtime environments are incompatible. In many cases, programs are integrated by modifying their components or interposing mechanisms that handle communication and conversion tasks. For example, remote procedure call (RPC) helps integrate heterogeneous, distributed programs. When configuring such programs, however, mechanisms like RPC must be used explicitly by software developers in order to integrate collections of diverse components. Each collection may require a unique integration solution. This paper describes improvements to the concepts of software packaging and some of our experiences in constructing complex software systems from a wide variety of components in different execution environments. Software packaging is a process that automatically determines how to integrate a diverse collection of computer programs based on the types of components involved and the capabilities of available translators and adapters in an environment. Software packaging provides a context that relates such mechanisms to software integration processes and reduces the cost of configuring applications whose components are distributed or implemented in different programming languages. Our software packaging tool subsumes traditional integration tools like UNIX make by providing a rule-based approach to software integration that is independent of execution environments.

Callahan, John R.↗
NASA NTRS1995

Urine Pretreat Injection System

A new method of introducing the OXONE (Registered Trademark) Monopersulfate Compound for urine pretreat into a two-phase urine/air flow stream has been successfully tested and evaluated. The feasibility of this innovative method has been established for purposes of providing a simple, convenient, and safe method of handling a chemical pretreat required for urine processing in a microgravity space environment. Also, the Oxone portion of the urine pretreat has demonstrated the following advantages during real time collection of 750 pounds of urine in a Space Station design two-phase urine Fan/Separator: Eliminated urine precipitate buildup on internal hardware and plumbing; Minimized odor from collected urine; and Virtually eliminated airborne bacteria. The urine pretreat, as presently defined for the Space Station program for proper downstream processing of urine, is a two-part chemical treatment of 5.0 grams of Oxone and 2.3 ml of H2SO4 per liter of urine. This study program and test demonstrated only the addition of the proper ratio of Oxone into the urine collection system upstream of the Fan/Separator. This program was divided into the following three major tasks: (1) A trade study, to define and recommend the type of Oxone injection method to pursue further; (2) The design and fabrication of the selected method; and (3) A test program using high fidelity hardware and fresh urine to demonstrate the method feasibility. The trade study was conducted which included defining several methods for injecting Oxone in different forms into a urine system. Oxone was considered in a liquid, solid, paste and powered form. The trade study and the resulting recommendation were presented at a trade study review held at Hamilton Standard on 24-25 October 94. An agreement was reached at the meeting to continue the solid tablet in a bag concept which included a series of tablets suspended in the urine/air flow stream. These Oxone tablets would slowly dissolve at a controlled rate providing the proper concentration in the collected urine. To implement the solid tablet in a bag approach, a design concept was completed with prototype drawings of the complete urine pretreat prefilter assembly. A successful fabrication technique was developed for retaining the Oxone tablets in a fabric casing attached to the end of the existing Space Station Waste Collection System urine prefilter assembly. The final pretreat prefilter configuration held sufficient Oxone in a tablet form to allow normal scheduled daily (or twice daily) change out of the urine filter depending on the use rate of the Space Station urine collection system. The actual tests to prove the concept were conducted using the Urine Fan/Separator assembly that was originally used in the STS-52 Design Test Objective (DTO) urinal assembly. Other related tests were conducted to demonstrate the actual minimum ratio of Oxone to urine that will control microbial growth.

Source record↗
NASA NTRS2010

Ares I-X Flight Evaluation Tasks in Support of Ares I Development

NASA s Constellation Program successfully launched the Ares I-X Flight Test Vehicle on October 28, 2009. The Ares I-X flight was a development flight test that offered a unique opportunity for early engineering data to impact the design and development of the Ares I crew launch vehicle. As the primary customer for flight data from the Ares I-X mission, the Ares Projects Office established a set of 33 flight evaluation tasks to correlate fight results with prospective design assumptions and models. Included within these tasks were direct comparisons of flight data with pre-flight predictions and post-flight assessments utilizing models and modeling techniques being applied to design and develop Ares I. A discussion of the similarities and differences in those comparisons and the need for discipline-level model updates based upon those comparisons form the substance of this paper. The benefits of development flight testing were made evident by implementing these tasks that used Ares I-X data to partially validate tools and methodologies in technical disciplines that will ultimately influence the design and development of Ares I and future launch vehicles. The areas in which partial validation from the flight test was most significant included flight control system algorithms to predict liftoff clearance, ascent, and stage separation; structural models from rollout to separation; thermal models that have been updated based on these data; pyroshock attenuation; and the ability to predict complex flow fields during time-varying conditions including plume interactions.

Huebner, Lawrence D.↗
NASA NTRS2003

Research priorities and plans for the International Space Station-results of the 'REMAP' Task Force

Recent events in the International Space Station (ISS) Program have resulted in the necessity to re-examine the research priorities and research plans for future years. Due to both technical and fiscal resource constraints expected on the International Space Station, it is imperative that research priorities be carefully reviewed and clearly articulated. In consultation with OSTP and the Office of Management and budget (OMB), NASA's Office of Biological and Physical Research (OBPR) assembled an ad-hoc external advisory committee, the Biological and Physical Research Maximization and Prioritization (REMAP) Task Force. This paper describes the outcome of the Task Force and how it is being used to define a roadmap for near and long-term Biological and Physical Research objectives that supports NASA's Vision and Mission. Additionally, the paper discusses further prioritizations that were necessitated by budget and ISS resource constraints in order to maximize utilization of the International Space Station. Finally, a process has been developed to integrate the requirements for this prioritized research with other agency requirements to develop an integrated ISS assembly and utilization plan that maximizes scientific output. c2003 American Institute of Aeronautics and Astronautics. Published by Elsevier Science Ltd. All rights reserved.

NASA Center HQS↗
NASA NTRS2015

Affordable Development and Demonstration of a Small NTR Engine and Stage: How Small is Big Enough?

In FY11, NASA formulated a plan for Nuclear Thermal Propulsion (NTP) development that included Foundational Technology Development followed by system-level Technology Demonstrations The ongoing NTP project, funded by NASAs Advanced Exploration Systems (AES) program, is focused on Foundational Technology Development and includes 5 key task activities:(1) Fuel element fabrication and non-nuclear validation testing of heritage fuel options;(2) Engine conceptual design;(3) Mission analysis and engine requirements definition;(4) Identification of affordable options for ground testing; and(5) Formulation of an affordable and sustainable NTP development program Performance parameters for Point of Departure designs for a small criticality-limited and full size 25 klbf-class engine were developed during FYs 13-14 using heritage fuel element designs for both RoverNERVA Graphite Composite (GC) and Ceramic Metal (Cermet) fuel forms To focus the fuel development effort and maximize use of its resources, the AES program decided, in FY14, that a leader-follower down selection between GC and cermet fuel was required An Independent Review Panel (IRP) was convened by NASA and tasked with reviewing the available fuel data and making a recommendation to NASA. In February 2015, the IRP recommended and the AES program endorsed GC as the leader fuel In FY14, a preliminary development schedule DDTE plan was produced by GRC, DOE industry for the AES program. Assumptions, considerations and key task activities are presented here Two small (7.5 and 16.5 klbf) engine sizes were considered for ground and flight technology demonstration within a 10-year timeframe; their ability to support future human exploration missions was also examined and a recommendation on a preferred size is provided.

spacecraft design↗
NASA NTRS2015

Affordable Development and Demonstration of a Small NTR Engine and Stage: A Preliminary NASA, DOE, and Industry Assessment

In FY11, NASA formulated a plan for Nuclear Thermal Propulsion (NTP) development that included Foundational Technology Development followed by system-level Technology Demonstrations. The ongoing NTP project, funded by NASA's Advanced Exploration Systems (AES) program, is focused on Foundational Technology Development and includes 5 key task activities: (1) Fuel element fabrication and non-nuclear validation testing of heritage fuel options; (2) Engine conceptual design; (3) Mission analysis and engine requirements definition; (4) Identification of affordable options for ground testing; and (5) Formulation of an affordable and sustainable NTP development program. Performance parameters for Point of Departure designs for a small criticality-limited and full size 25 klb (sub f) (kip, or 1000 pound-force)-class engine were developed during FYs 13-14 using heritage fuel element designs for both Rover NERVA (Nuclear Engine for Rocket Vehicle Applications) Graphite Composite (GC) and Ceramic Metal (Cermet) fuel forms. To focus the fuel development effort and maximize use of its resources, the AES program decided, in FY14, that a leader-follower down-selection between GC and cermet fuel was required. An Independent Review Panel (IRP) was convened by NASA and tasked with reviewing the available fuel data and making a recommendation to NASA. In February 2015, the IRP recommended and the AES program endorsed GC as the leader fuel In FY14, a preliminary development schedule DDTE (Design Development Test and Evaluation) plan was produced by GRC (Glenn Research Center), DOE (Department of Energy) and industry for the AES program. Assumptions, considerations and key task activities are presented here. At the direction of NASA HQ (32515), NASA and DOE are to work together to formulate a detailed development plan and schedule allowing the affordable development of a small (7.5-16.5 klbf) GC engine for possible flight technology demonstration (FTD) mission within a 10-year timeframe.

Lunar Flyby Mission↗
NASA NTRS1983

Advanced Platform Systems Technology study. Volume 4: Technology advancement program plan

An overview study of the major technology definition tasks and subtasks along with their interfaces and interrelationships is presented. Although not specifically indicated in the diagram, iterations were required at many steps to finalize the results. The development of the integrated technology advancement plan was initiated by using the results of the previous two tasks, i.e., the trade studies and the preliminary cost and schedule estimates for the selected technologies. Descriptions for the development of each viable technology advancement was drawn from the trade studies. Additionally, a logic flow diagram depicting the steps in developing each technology element was developed along with descriptions for each of the major elements. Next, major elements of the logic flow diagrams were time phased, and that allowed the definition of a technology development schedule that was consistent with the space station program schedule when possible. Schedules show the major milestone including tests required as described in the logic flow diagrams.

Source record↗
NASA NTRS2000

Performance Characteristics of Lithium-Ion Prototype Batteries for Mars Surveyor Program 2001 Lander

A viewgraph presentation outlines the scientific payload, expected launch date and tasks, and an image of the Mars Surveyor 2001 Lander components. The Lander's battery specifications are given. The program objectives for the Li-ion cells for the Lander are listed, and results performance evaluation and cycle life performance tests are outlined for different temperatures. Cell charge characteristics are described, and test data is presented for charge capacity at varying temperatures. Capacity retention and storage characteristics tests are described and results are shown.

Smart, M. C.↗
NASA NTRS1987

System engineering techniques for establishing balanced design and performance guidelines for the advanced telerobotic testbed

Novel system engineering techniques have been developed and applied to establishing structured design and performance objectives for the Telerobotics Testbed that reduce technical risk while still allowing the testbed to demonstrate an advancement in state-of-the-art robotic technologies. To estblish the appropriate tradeoff structure and balance of technology performance against technical risk, an analytical data base was developed which drew on: (1) automation/robot-technology availability projections, (2) typical or potential application mission task sets, (3) performance simulations, (4) project schedule constraints, and (5) project funding constraints. Design tradeoffs and configuration/performance iterations were conducted by comparing feasible technology/task set configurations against schedule/budget constraints as well as original program target technology objectives. The final system configuration, task set, and technology set reflected a balanced advancement in state-of-the-art robotic technologies, while meeting programmatic objectives and schedule/cost constraints.

Zimmerman, W. F.↗
NASA NTRS1981

Modal analysis using a Fourier analyzer, curve-fitting, and modal tuning

The proposed modal test program differs from single-input methods in that preliminary data may be acquired using multiple inputs, and modal tuning procedures may be employed to define closely spaced frquency modes more accurately or to make use of frequency response functions (FRF's) which are based on several input locations. In some respects the proposed modal test proram resembles earlier sine-sweep and sine-dwell testing in that broadband FRF's are acquired using several input locations, and tuning is employed to refine the modal parameter estimates. The major tasks performed in the proposed modal test program are outlined. Data acquisition and FFT processing, curve fitting, and modal tuning phases are described and examples are given to illustrate and evaluate them.

Craig, R. R., Jr.↗
DOE OSTI2019

ROBOT: A Tool for Automating Ontology Workflows

BACKGROUND:Ontologies are invaluable in the life sciences, but building and maintaining ontologies often requires a challenging number of distinct tasks such as running automated reasoners and quality control checks, extracting dependencies and application-specific subsets, generating standard reports, and generating release files in multiple formats. Similar to more general software development, automation is the key to executing and managing these tasks effectively and to releasing more robust products in standard forms. For ontologies using the Web Ontology Language (OWL), the OWL API Java library is the foundation for a range of software tools, including the Protégé ontology editor. In the Open Biological and Biomedical Ontologies (OBO) community, we recognized the need to package a wide range of low-level OWL API functionality into a library of common higher-level operations and to make those operations available as a command-line tool. RESULTS:ROBOT (a recursive acronym for "ROBOT is an OBO Tool") is an open source library and command-line tool for automating ontology development tasks. The library can be called from any programming language that runs on the Java Virtual Machine (JVM). Most usage is through the command-line tool, which runs on macOS, Linux, and Windows. ROBOT provides ontology processing commands for a variety of tasks, including commands for converting formats, running a reasoner, creating import modules, running reports, and various other tasks. These commands can be combined into larger workflows using a separate task execution system such as GNU Make, and workflows can be automatically executed within continuous integration systems. CONCLUSIONS:ROBOT supports automation of a wide range of ontology development tasks, focusing on OBO conventions. It packages common high-level ontology development functionality into a convenient library, and makes it easy to configure, combine, and execute individual tasks in comprehensive, automated workflows. This helps ontology developers to efficiently create, maintain, and release high-quality ontologies, so that they can spend more time focusing on development tasks. It also helps guarantee that released ontologies are free of certain types of logical errors and conform to standard quality control checks, increasing the overall robustness and efficiency of the ontology development lifecycle.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗
NASA NTRS1991

Database for propagation models

A propagation researcher or a systems engineer who intends to use the results of a propagation experiment is generally faced with various database tasks such as the selection of the computer software, the hardware, and the writing of the programs to pass the data through the models of interest. This task is repeated every time a new experiment is conducted or the same experiment is carried out at a different location generating different data. Thus the users of this data have to spend a considerable portion of their time learning how to implement the computer hardware and the software towards the desired end. This situation may be facilitated considerably if an easily accessible propagation database is created that has all the accepted (standardized) propagation phenomena models approved by the propagation research community. Also, the handling of data will become easier for the user. Such a database construction can only stimulate the growth of the propagation research it if is available to all the researchers, so that the results of the experiment conducted by one researcher can be examined independently by another, without different hardware and software being used. The database may be made flexible so that the researchers need not be confined only to the contents of the database. Another way in which the database may help the researchers is by the fact that they will not have to document the software and hardware tools used in their research since the propagation research community will know the database already. The following sections show a possible database construction, as well as properties of the database for the propagation research.

Kantak, Anil V.↗
NASA NTRSDate not supplied

Handling Qualities Assessment of Manual Lunar Landing with Display Augmentation

Research and development is being conducted to support data-driven design decisions for manual control and human involvement in the lunar landing task under the Human Landing System (HLS) program within the Artemis campaign. A human-in-the-loop simulator evaluation of the manual control of a lunar landing vehicle in the final approach and landing phase was conducted at NASA Langley Research Center in the Lunar Flight Deck simulator using the Altair Design and Analysis Cycle (DAC)-2 government reference vehicle. The objective was to perform a direct comparison of control law types with display aiding for various rotational control powers being considered under HLS. Ten subjects (four NASA test pilots and six current pilot astronauts) provided Cooper-Harper ratings, NASA Task Load Index workload ratings, and qualitative comments. The piloting task was to assume manual control of the vehicle (including vertical descent rate) at 150 m above the landing zone, fly to a redesignated landing target (which was up to 75 m radially from the center of the landing zone) and to touch down within a position accuracy of 5m. The data showed that the display augmentation in the form of a “hover cue” significantly improved the pilot’s ability to control translation and create satisfactory handling qualities for otherwise sluggish configurations; however, the investigation also showed that display augmentation is not a panacea. Handling qualities problems, including pilot-induced oscillations, and higher workload for the lowest control powers can still be evident.

Lynda J. Kramer↗