SEARCH · Engineering Papers

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 379 records · Page 21

All sources NASA NTRS DOE OSTI

NASA NTRS2001

Mississippi Company Using NASA Software Program to Provide Unique Imaging Service: DATASTAR Success Story

DATASTAR, Inc., of Picayune, Miss., has taken NASA's award-winning Earth Resources Laboratory Applications (ELAS) software program and evolved it to the point that the company is now providing a unique, spatial imagery service over the Internet. ELAS was developed in the early 80's to process satellite and airborne sensor imagery data of the Earth's surface into readable and useable information. While there are several software packages on the market that allow the manipulation of spatial data into useable products, this is usually a laborious task. The new program, called the DATASTAR Image Processing Exploitation, or DIPX, Delivery Service, is a subscription service available over the Internet that takes the work out of the equation and provides normalized geo-spatial data in the form of decision products.

Source record↗

NASA NTRS1972

Development of flight experiment task requirements. Volume 2: Technical Report. Part 1: Program report and Appendices A-G

Activities are documented of the study to determine skills required of on-orbit crew personnel of the space shuttle. The material is presented in four sections that include: (1) methodology for identifying flight experiment task-skill requirements, (2) task-skill analysis of selected flight experiments, (3) study results and conclusions, and (4) new technology.

Hatterick, G. R.↗

NASA NTRS1990

Performance-based workload assessment: Allocation strategy and added task sensitivity

The preliminary results of a research program investigating the use of added tasks to evaluate mental workload are reviewed. The focus of the first studies was a reappraisal of the traditional secondary task logic that encouraged the use of low-priority instructions for the added task. It was believed that such low-priority tasks would encourage subjects to split their available resources among the two tasks. The primary task would be assigned all the resources it needed, and any remaining reserve capacity would be assigned to the secondary task. If the model were correct, this approach was expected to combine sensitivity to primary task difficulty with unintrusiveness to primary task performance. The first studies of the current project demonstrated that a high-priority added task, although intrusive, could be more sensitive than the traditional low-priority secondary task. These results suggested that a more appropriate model of the attentional effects associated with added task performance might be based on capacity switching, rather than the traditional optimal allocation model.

Vidulich, Michael A.↗

NASA NTRS1992

AXAF user interfaces for heterogeneous analysis environments

The AXAF Science Center (ASC) will develop software to support all facets of data center activities and user research for the AXAF X-ray Observatory, scheduled for launch in 1999. The goal is to provide astronomers with the ability to utilize heterogeneous data analysis packages, that is, to allow astronomers to pick the best packages for doing their scientific analysis. For example, ASC software will be based on IRAF, but non-IRAF programs will be incorporated into the data system where appropriate. Additionally, it is desired to allow AXAF users to mix ASC software with their own local software. The need to support heterogeneous analysis environments is not special to the AXAF project, and therefore finding mechanisms for coordinating heterogeneous programs is an important problem for astronomical software today. The approach to solving this problem has been to develop two interfaces that allow the scientific user to run heterogeneous programs together. The first is an IRAF-compatible parameter interface that provides non-IRAF programs with IRAF's parameter handling capabilities. Included in the interface is an application programming interface to manipulate parameters from within programs, and also a set of host programs to manipulate parameters at the command line or from within scripts. The parameter interface has been implemented to support parameter storage formats other than IRAF parameter files, allowing one, for example, to access parameters that are stored in data bases. An X Windows graphical user interface called 'agcl' has been developed, layered on top of the IRAF-compatible parameter interface, that provides a standard graphical mechanism for interacting with IRAF and non-IRAF programs. Users can edit parameters and run programs for both non-IRAF programs and IRAF tasks. The agcl interface allows one to communicate with any command line environment in a transparent manner and without any changes to the original environment. For example, the authors routinely layer the GUI on top of IRAF, ksh, SMongo, and IDL. The agcl, based on the facilities of a system called Answer Garden, also has sophisticated support for examining documentation and help files, asking questions of experts, and developing a knowledge base of frequently required information. Thus, the GUI becomes a total environment for running programs, accessing information, examining documents, and finding human assistance. Because the agcl can communicate with any command-line environment, most projects can make use of it easily. New applications are continually being found for these interfaces. It is the authors' intention to evolve the GUI and its underlying parameter interface in response to these needs - from users as well as developers - throughout the astronomy community. This presentation describes the capabilities and technology of the above user interface mechanisms and tools. It also discusses the design philosophies guiding the work, as well as hopes for the future.

Mandel, Eric↗

NASA NTRS1994

Technical assessment of Mir-1 life support hardware for the international space station

NASA has been progressively learning the design and performance of the Russian life support systems utilized in their Mir space station. In 1992, a plan was implemented to assess the benefits of the Mir-1 life support systems to the Freedom program. Three primary tasks focused on: evaluating the operational Mir-1 support technologies and understanding if specific Russian systems could be directly utilized on the American space station and if Russian technology design information could prove useful in improving the current design of the planned American life support equipment; evaluating the ongoing Russian life support technology development activities to determine areas of potential long-term application to the U.S. space station; and utilizing the expertise of their space station life support systems to evaluate the benefits to the current U.S. space station program which included the integration of the Russian Mir-1 designs with the U.S. designs to support a crew of six.

Mitchell, K. L.↗

NASA NTRS1989

A situated reasoning architecture for space-based repair and replace tasks

Space-based robots need low level control for collision detection and avoidance, short-term load management, fine-grained motion, and other physical tasks. In addition, higher level control is required to focus strategic decision making as missions are assigned and carried out. Reasoning and control must be responsive to ongoing changes in the environment. Research aimed at bridging the gap between high level artificial intelligence (AI) planning techniques and task-level robot programming for telerobotic systems is described. Situated reasoning is incorporated into AI and Robotics systems in order to coordinate a robot's activity within its environment. An integrated system under development in a component maintenance domain is described. It is geared towards replacing worn and/or failed Orbital Replacement Units (ORUs) designed for use aboard NASA's Space Station Freedom based on the collection of components available at a given time. High level control reasons in component space in order to maximize the number operational component-cells over time, while the task-level controls sensors and effectors, detects collisions, and carries out pick and place tasks in physical space. Situated reasoning is used throughout the system to cope with component failures, imperfect information, and unexpected events.

Bloom, Ben↗

NASA NTRSDate not supplied

Onboard Autonomous Trajectory Planning for Mars Power Descent

In recent years, there has been an increasing interest in space-qualified processors such as multi-core central processing units and graphics processing units that can withstand the adverse effects of space radiation. These processors can allow parallel programming to perform tasks that typically demand high computational power. One can study guidance schemes that can take advantage of these currently developing processors and provide more robust guidance. Software for Multi-model Autonomous Real-time Trajectories (SMART) guidance can identify robust trajectories by running an onboard Monte Carlo analysis. SMART guidance can take advantage of knowledge updates obtained from the onboard sensors, allowing it to consider the off-nominal cases that it would not typically encounter during the offline trajectory analysis. This work uses the SMART guidance for the powered divert at Mars simulation in Program to Optimize and Simulated Trajectories- II.

Pardha Sai Chadalavada↗

NASA NTRSDate not supplied

Onboard Autonomous Trajectory Planning for Mars Power Descent

Autonomous Planning↗

DOE OSTI2023

Analytical Radiochemical Method Development for Mark 18A Program

The Savannah River National Laboratory Nuclear Measurements Group was tasked by the Mark 18A Program team with developing three analytical characterization methods. These methods will support process and waste characterization of the Mark 18A program material. While methods already existed for most analytes of interest to the Mark 18A program team, the Nuclear Measurements Group developed and refined methods to quantify the Cf isotopes, 107 Pd, and 121m Sn. The results of that effort are presented in this work. Methods were successfully developed to characterize the Mark 18A samples for the needed isotopes and the NMG is ready to receive Mark 18A program samples.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

NASA NTRS2007

Program Management Tool

The Program Management Tool (PMT) is a comprehensive, Web-enabled business intelligence software tool for assisting program and project managers within NASA enterprises in gathering, comprehending, and disseminating information on the progress of their programs and projects. The PMT provides planning and management support for implementing NASA programmatic and project management processes and requirements. It provides an online environment for program and line management to develop, communicate, and manage their programs, projects, and tasks in a comprehensive tool suite. The information managed by use of the PMT can include monthly reports as well as data on goals, deliverables, milestones, business processes, personnel, task plans, monthly reports, and budgetary allocations. The PMT provides an intuitive and enhanced Web interface to automate the tedious process of gathering and sharing monthly progress reports, task plans, financial data, and other information on project resources based on technical, schedule, budget, and management criteria and merits. The PMT is consistent with the latest Web standards and software practices, including the use of Extensible Markup Language (XML) for exchanging data and the WebDAV (Web Distributed Authoring and Versioning) protocol for collaborative management of documents. The PMT provides graphical displays of resource allocations in the form of bar and pie charts using Microsoft Excel Visual Basic for Application (VBA) libraries. The PMT has an extensible architecture that enables integration of PMT with other strategic-information software systems, including, for example, the Erasmus reporting system, now part of the NASA Integrated Enterprise Management Program (IEMP) tool suite, at NASA Marshall Space Flight Center (MSFC). The PMT data architecture provides automated and extensive software interfaces and reports to various strategic information systems to eliminate duplicative human entries and minimize data integrity issues among various NASA systems that impact schedules and planning.

Gawadiak, Yuri↗

NASA NTRS1995

NASA-UVa light aerospace alloy and structures technology program supplement: Aluminum-based materials for high speed aircraft

This report on the NASA-UVa light aerospace alloy and structure technology program supplement: Aluminum-Based Materials for High Speed Aircraft covers the period from July 1, 1992. The objective of the research is to develop aluminum alloys and aluminum matrix composites for the airframe which can efficiently perform in the HSCT environment for periods as long as 60,000 hours (certification for 120,000 hours) and, at the same time, meet the cost and weight requirements for an economically viable aircraft. Current industry baselines focus on flight at Mach 2.4. The research covers four major materials systems: (1) Ingot metallurgy 2XXX, 6XXX, and 8XXX alloys, (2) Powder metallurgy 2XXX alloys, (3) Rapidly solidified, dispersion strengthened Al-Fe-X alloys, and (4) Discontinuously reinforced metal matrix composites. There are ten major tasks in the program which also include evaluation and trade-off studies by Boeing and Douglas aircraft companies.

Starke, E. A., Jr.↗

NASA NTRS1993

NASA-UVa light aerospace alloy and structure technology program supplement: Aluminum-based materials for high speed aircraft

This report on the NASA-UVa Light Aerospace Alloy and Structure Technology Program Supplement: Aluminum-Based Materials for High Speed Aircraft covers the period from January 1, 1992 to June 30, 1992. The objective of the research is to develop aluminum alloys and aluminum matrix composites for the airframe which can efficiently perform in the HSCT environment for periods as long as 60,000 hours (certification for 120,000 hours) and, at the same time, meet the cost and weight requirements for an economically viable aircraft. Current industry baselines focus on flight at Mach 2.4. The research covers four major materials systems: (1) ingot metallurgy 2XXX, 6XXX, and 8XXX alloys, (2) powder metallurgy 2XXX alloys, (3) rapidly solidified, dispersion strengthened Al-Fe-X alloys, and (4) discontinuously reinforced metal matrix composites. There are ten major tasks in the program which also include evaluation and trade-off studies by Boeing and Douglas aircraft companies.

Starke, E. A., Jr.↗

NASA NTRS1996

An interactive parallel programming environment applied in atmospheric science

This article introduces an interactive parallel programming environment (IPPE) that simplifies the generation and execution of parallel programs. One of the tasks of the environment is to generate message-passing parallel programs for homogeneous and heterogeneous computing platforms. The parallel programs are represented by using visual objects. This is accomplished with the help of a graphical programming editor that is implemented in Java and enables portability to a wide variety of computer platforms. In contrast to other graphical programming systems, reusable parts of the programs can be stored in a program library to support rapid prototyping. In addition, runtime performance data on different computing platforms is collected in a database. A selection process determines dynamically the software and the hardware platform to be used to solve the problem in minimal wall-clock time. The environment is currently being tested on a Grand Challenge problem, the NASA four-dimensional data assimilation system.

Interactive Display Devices↗

NASA NTRS2014

NASA's Approach to Critical Risks for Extended Human Space Flight

Planetary Robotic and Human Spaceflight Exploration Humans are exposed to a great variety of hazards in the space environment. These include the effects of weightlessness, radiation, isolation and confinement, altered day-night cycles, and others. These inherent hazards have both physiological and behavioral consequences. The adaptive capabilities of humans in these situations is remarkable, and often exceed our expectations. However, the demanding environment and challenging operational pace can push some of these adaptive processes to their limits. The NASA Human Research Program (HRP) is tasked with mitigating the most serious of these effects on human health, safety, and performance, in long-duration space flight. This can involve the development and deployment of physiological countermeasures, better understanding of the physiological alterations and avoidance of exacerbating situations, inputs to the design of future spacecraft to minimize risks, and in some cases the awareness that some level of risk might have to be accepted based on the resulting consequences and their likelihood. HRP has identified a few areas that are of special concern due to their severity, lack of understanding of underlying causes, or potential for negative impact on health or performance. Some of these areas are visual impairment possibly due to increased intracranial pressure, behavioral and performance problems due to sleep deficits and isolation, and acute and chronic effects of radiation. These problems can, if not addressed, be expected to increase on longer and more distant missions. The evidence from spaceflight, laboratory, and analog studies that supports the selection of the most critical risks will be discussed. Current and planned research programs that address these risks, and their anticipated outcomes, will also be described.

Shelhamer, Mark↗

DOE OSTI2020

Proposed guidance for preparing and reviewing a molten salt non-power production or utilization facility application

Development of non-power molten salt reactors (MSRs) are under consideration to further establish an MSR experience base, support the requirements of Title 10 of the Code of Federal Regulations (10 CFR) Section 50.43(e), and provide any additional analyses needed for development of a full-scale MSR. Guidance provided in this report is based on MSRs operating with liquid fuel (i.e., fuel dissolved within a molten salt). These reactors, unless owned by the DOE or DOD, will require licensing by the US Nuclear Regulatory Commission (NRC) staff. Standard review plan (SRP) guidance for large light water reactors (LWRs) is available in NUREG-0800, Standard Review Plan for the Review of Safety Analysis Reports for Nuclear Power Plants; Light Water Reactor (LWR) Edition. However, NRC staff observed that NUREG-0800 is very cumbersome to apply to non-power reactors “because of the great differences in complexity and hazards between non-power reactors and nuclear power plants.” Therefore, a program to develop performance-based guidance applicable to non-power reactors was initiated. In 1996, NUREG-1537, Parts 1 and 2, Guidelines for Preparing and Reviewing Applications for the Licensing of Non-Power Reactors, was published. Part 1, the format and content guide, suggests a uniform format for presenting information in non-power reactor applications that is acceptable to the NRC staff, but conformance with the format and content is not required. Part 2, the SRP, ensures the quality and uniformity of the staff review of an application. Unfortunately, the application guidelines and SRP do not provide adequate guidance for all advanced non-LWR technologies and applications. This discrepancy eventually led to the 2012 development of interim staff guidance (ISG) for NUREG-1537, which includes criteria for describing and reviewing aqueous homogeneous reactors (AHRs). Specifically, NUREG-1537 ISG, 2012 expanded the original document to address three areas: 1. updated criteria for heterogeneous non-power reactors, 2. criteria for licensing AHRs, and 3. criteria for licensing a Part 50-licensed isotope production facility. In 2015, the US Department of Energy (DOE) opted to build on the AHR NUREG-1537 ISG experience by performing a gap analysis of the guidance that would be used to license a non-power MSR. MSRs represent one of the advanced non-LWR technologies selected by DOE for development through a multiyear cost share award with Southern Company Services. Under this Advanced Reactor Concepts 2015 (DOE Advanced Reactor Concepts [ARC] 15) award program, the DOE tasked Oak Ridge National Laboratory (ORNL) to evaluate the guidance changes that the NRC may need to consider when licensing an MSR non-power reactor. ORNL staff, with support from Boston Government Services, LLC, focused on five system-related chapters in NUREG-1537 that were considered most relevant to inform the effort that would be required for a non-power MSR applicant. ORNL documented this review in a technical report, ORNL/TM-2018/834, Proposed Guidance for Preparing and Reviewing Molten Salt Non-Power Reactor License Applications (NUREG-1537). The report was subsequently shared with industry and the NRC. The 2018 review was limited in scope, focusing on key system chapters based on the expected significance of each chapter relative to expected differences in addressing advanced non-LWR technologies, specifically non-power MSRs, compared with heterogeneously fueled non-power reactors. In the ORNL report, proposed generic adaptations were suggested for the following NUREG-1537 chapters: Chapter 4, “Reactor Description”; Chapter 5, “Reactor Coolant Systems”; Chapter 6, “Engineered Safety Features”; Chapter 9, “Auxiliary Systems”; Chapter 11, “Radiation Protection Program and Waste Management” The inclusion of Chapter 11 in the previous review effort was intended to provide guidance for categorizing the waste-handling process for an MSR operating with homogenous fuel. The introductions from Parts 1 and 2 of the 2012 NUREG-1537 ISG provide guidance for the application and review of production facilities. After a period of operation, non-power MSRs with homogenous fuel will include gaseous and soluble fission products. The gaseous fission products will be collected and held for decay in an off-gas system. There might also be an initiative to polish or filter the soluble fission products in the fuel salt by some mechanical or chemical means. The treatment and handling of fission products in the non-power MSR fuel salt and the description of this process in the safety analysis report (SAR) must be very precise to avoid the waste treatment facility being construed as a co-located special nuclear material (SNM) fuel cycle facility (see Section 2.3 of this report). Subsequent to the release of ORNL/TM-2018/834, NRC staff expressed a desire to continue the regulatory gap analysis that was begun in that report. This would provide additional clarity and information addressed in certain sections of the original report, while also providing new guidance on certain topics not addressed in the original report. This revision would benefit the NRC staff reviewing applications involving non-power MSR designs and would help developers understand how the NRC staff might approach the review of such applications. The focus of this report is to provide infrastructure support to the NRC staff for the regulatory review of non-power MSRs.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

NASA NTRS2024

Lunar Terrain Vehicle (LTV) Remote Teleoperation Studies Under Four Lunar Communication Latencies

Remotely operating a lunar rover from Earth while subject to an Earth-Moon time delay of multiple seconds could result in a dangerous state where the roving vehicle is either damaged or lost, thereby potentially compromising an entire mission or series of missions. Providing the right capabilities to the remote operator to manage inherent communication latencies will be important for remote driving to be successful. NASA conducted two studies to investigate the average speed and number of kilometers per day that an operator on Earth could teleoperate a notional Artemis unpressurized rover with minimal remote operator capabilities under 0- and 4-second communication delays (April 2023 study) and 6- and 8-second delays (August 2023 study). A primary goal of these studies was to understand if an Artemis Lunar Terrain Vehicle (LTV) could cover 6 kilometers (km) in 24 hours when operated remotely. During the April 2023 evaluation, eight test operators used an in-house simulation of the lunar surface South Pole to teleoperate a NASA government reference LTV. Each operator received approximately 30 minutes of remote driving familiarization/training prior to their test run. Operators viewed the surrounding terrain via a single, rover mast-mounted, high-resolution camera with pan/tilt/zoom capabilities; continuous communication was provided throughout all testing. In the August 2023 evaluation, remote operators received approximately 3 hours of familiarization training in each latency, and the simulation environment provided remote operators with an operator-selected rate limiter to enable finer sensitivity in the hand controller and a predictive circle function to better assist operators with predicting the path the vehicle could take. All test operators were able to successfully navigate and drive through six different types of terrain and five planned traverse scenarios using natural lighting under all communication delays. Results for average speeds for each communication delay, computed by averaging the data from all test conditions for that latency and all operators, are shown in the table below. The average speed data was then used to derive the total time needed to cover 6 km, 8 km, and 20 km (distances relevant to LTV-SYS071 and -029 requirements). Remote operators drove slower and used the brake more frequently when subject to a communication latency as opposed to no communication latency. Subjective workload assessments revealed that while operating in a latency the overall workload significantly increased when compared to a 0-s delay with mental demand, frustration, and performance being the primary contributing factors. Driving strategies in the 0-s delay did not vary significantly among subjects; however, in the 4-s delay condition, three different driving strategies were identified. In the 6-s and 8-s latency conditions the operator’s use of the cruise control to maintain speed was more apparent. Additionally, over the course of the August study, the operator took advantage of the predictive circle indicator on the navigation display and over 95% of the operator’s navigation used the mast camera 180-degree panning function for ground truthing in terms of boulders and craters. Operators started to define more specific parameters in driving strategies for general operations. This consisted of setting the vehicle into a low-speed cruise mode of approximately 11.5 kph and noticing driving performance of the vehicle seemed to be much harder at slower speeds 0.4–0.8 kph; however, the vehicle was more responsive at speeds of 2.9–3.6 kph. Regardless of communication delay, operators used both the horizontal translation rails and the vehicle fenders as guides to predict a path for the vehicle through heavily concentrated terrain features. Test operators acknowledged that the teleoperations training for this study was substantially less than what an actual LTV remote operator will ultimately receive. They estimated a minimum of 20 to 100 hours spread across multiple days and weeks (e.g., strategies included immersion training over a 3-day period, to a short 8-week starter program) would be needed to get an operator ~ 60% proficient (i.e., able to complete a subset of remote driving tasks), to a yearlong program for full proficiency in remote driving tasks under all terrain types and natural lighting conditions. Remotely operating a vehicle on another planetary body while subject to communication latency is a complex task. Speed, distance covered, time spent driving, time spent navigating, brake usage and rock contacts are all affected by operator workload, driving strategies, workstation ergonomics and training. These studies provided a “first-look” answer to a potential system requirement (namely if a remote operator could cover a given distance in a given amount of time); however, considerable general knowledge was gained to begin to understand what it will take to make a successful lunar rover teleoperator.

LTV↗

NASA NTRS2025

Lunar Terrain Vehicle (LTV) Remote Teleoperation Studies Under Four Lunar Communication Latencies

Remotely operating a lunar rover from Earth while subject to an Earth-Moon time delay of multiple seconds could result in a dangerous state where the roving vehicle is either damaged or lost, thereby potentially compromising an entire mission or series of missions. Providing the right capabilities to the remote operator to manage inherent communication latencies will be important for remote driving to be successful. The National Aeronautics and Space Administration (NASA) conducted two studies to investigate the average speed and number of kilometers per day that an operator on Earth could teleoperate a notional Artemis unpressurized rover with minimal remote operator capabilities under 0- and 4-second communication delays (April 2023 study) and 6- and 8-second delays (August 2023 study). A primary goal of these studies was to understand if an Artemis Lunar Terrain Vehicle (LTV) could cover 6 kilometers (km) in 24 hours when operated remotely. During the April 2023 evaluation, eight test operators used an in-house simulation of the lunar surface South Pole to teleoperate a NASA government reference LTV. Each operator received approximately 30 minutes of remote driving familiarization/training prior to their test run. Operators viewed the surrounding terrain via a single, rover mast-mounted, high-resolution camera with pan/tilt/zoom capabilities; continuous communication was provided throughout all testing. In the August 2023 evaluation, remote operators received approximately 3 hours of familiarization training in each latency, and the simulation environment provided remote operators with an operator-selected rate limiter to enable finer sensitivity in the hand controller and a predictive circle function to better assist operators with predicting the path the vehicle could take. All test operators were able to successfully navigate and drive through six different types of terrain and five planned traverse scenarios using natural lighting under all communication delays. Results for average speeds for each communication delay, computed by averaging the data from all test conditions for that latency and all operators, are shown in the table below. The average speed data was then used to derive the total time needed to cover 6 km, 8 km, and 20 km. Remote operators drove slower and used the brake more frequently when subject to a communication latency as opposed to no communication latency. Subjective workload assessments revealed that while operating in a latency the overall workload significantly increased when compared to a 0-s delay with mental demand, frustration, and performance being the primary contributing factors. Driving strategies in the 0-s delay did not vary significantly among subjects; however, in the 4-s delay condition, three different driving strategies were identified. In the 6-s and 8-s latency conditions the operator’s use of the cruise control to maintain speed was more apparent. Additionally, over the course of the August study, the operator took advantage of the predictive circle indicator on the navigation display and over 95% of the operator’s navigation used the mast camera 180-degree panning function for ground truthing in terms of boulders and craters. Operators started to define more specific parameters in driving strategies for general operations. This consisted of setting the vehicle into a low-speed cruise mode of approximately 1–1.5 kph and noticing driving performance of the vehicle seemed to be much harder at slower speeds 0.4–0.8 kph; however, the vehicle was more responsive at speeds of 2.9–3.6 kph. Regardless of communication delay, operators used both the horizontal translation rails and the vehicle fenders as guides to predict a path for the vehicle through heavily concentrated terrain features. Test operators acknowledged that the teleoperations training for this study was substantially less than what an actual LTV remote operator will ultimately receive. They estimated a minimum of 20 to 100 hours spread across multiple days and weeks (e.g., strategies included immersion training over a 3-day period, to a short 8-week starter program) would be needed to get an operator ~ 60% proficient (i.e., able to complete a subset of remote driving tasks), to a yearlong program for full proficiency in remote driving tasks under all terrain types and natural lighting conditions. Remotely operating a vehicle on another planetary body while subject to communication latency is a complex task. Speed, distance covered, time spent driving, time spent navigating, brake usage and rock contacts are all affected by operator workload, driving strategies, workstation ergonomics and training. These studies provided a “firstlook” answer to a potential system requirement (namely if a remote operator could cover a given distance in a given amount of time); however, considerable general knowledge was gained to begin to understand what it will take to make a successful lunar rover teleoperator.

LTV↗

NASA NTRS2004

Constructing an Educational Mars Simulation

Working in the Educational Programs Office, my task this summer is to model a 3D habitat that will be part of a future Mars base. With the President's charge to further explore mars by way of robotic-led and human-led missions, there has been a surge in the activity regarding the "red planet". Since all present designs are merely conjecture, I have some creative freedom in deciding what the habitat will look like. To get ideas for what a Mars habitat might be like, I looked at several references including websites and NASA documents. One of these was a NASA Technical Memorandum about Space Transportation Systems that I looked at to get insight on spaceship design. Information about the planet's environment, such as the gravity and the weather, is useful as well when designing the structure. The main software that I am using is Lightwave 3D and Modeler 7.5 that comes along with it. Lightwave is very complex in that it lets you model, surface, and animate so there was a lot to learn. To learn the software I watched a series of instructional videos, looked at online tutorials, and referenced several books. Modeling is like shaping clay with a computer. Every item modeled is made of smaller shapes called polygons. For example, each side of a box would be a different polygon. Modelers must be careful to design with users' systems in mind. Having a model made with too many polygons can slow down a walk-through, but it usually improves the small details on a model. Getting speed and quality proved tricky. An important thing for me to remember when modeling the habitat was to save space. Also, I must consider that technology in the future will be much different than now, so I must be especially creative. My project will be used in an educational walkthough simulation in which users can interact with the environment. I worked closely with intern Stephen Henke who built a Mars Rover, terrain and programmed code for the simulation. This summer's project will help me with future aspirations in computer graphics. Modeling is a valuable skill that I appreciate having the chance to learn and practice.

Henke, Stephen A.↗