SEARCH · Search NASA
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.
Pre-flight scheduling and pre-flight requirements of the space transportation system are discussed. Payload safety requirements, shuttle flight manifests, and interface specifications are studied in detail.
The trade-offs between different desirable plan properties –e. g. PDDL temporal plan preferences – are often difficult to understand. Recent work proposes to address this by iterative planning with explanations elucidating the dependencies between such plan properties. Users can ask questions of the form “Why does the plan you suggest not satisfy property p?”, which are answered by “Because then we would have to forego q” where ¬q is entailed by p in plan space. It has been shown that such plan-property dependencies can be computed reasonably efficiently. But is this form of explanation actually useful for users? We contribute a user study evaluating that question. We design use cases from three domains and run a large user study (N= 40 for each domain, ca. 40 minutes work time per user and domain) on the internet platform Prolific. Comparing users with vs. without access to the explanations, we find that the explanations tend to enable users to identify better trade-offs between the plan properties, indicating an improved understanding of the task.
The space transportation system (STS) and ancillary equipment user studies are presented. Space shuttle data and planning requirements needed by the STS user are discussed along with the potential for common usage of multi-mission support equipment by the military and other aerospace personnel.
Data formats and functional flow charts for interplanetary trajectory computation program
The multi-mission support equipment (MMSE) applicable to six payloads is studied. Tables indicate individual satellite projects to which each MMSE is applicable, and which equipments are applicable to multiple payload configurations when more than one project's payload would be flown on the STS. An estimate of the first date on which interface definition information needed by a payload project are also shown.
A record of what is currently known about STS ancillary equipment is presented in this user-oriented design so that a potential user may evaluate whether he could use the described ancillary equipment or if he would need to design and fabricate a payload-unique item. References that the user can use to obtain additional details and requirements to aid in his evaluation and decision are included.
Alternative candidate STS flight charge approaches which will provide a basis for NASA's determination of an STS flight charge policy were analyzed. The analysis used STS transportation costs furnished by NASA. The STS User Charge Analysis was accomplished by (1) generating criteria for evaluation of alternative flight charge approaches, (2) defining alternative flight charge approaches, (3) computing flight charges for selected missions, (4) evaluating results using the criteria generated under (1), and (5) recommending flight charge approaches to be used as a basis for the formulation of a STS user flight charge policy.
With the increasing presence of unmanned aerial vehicles (UAVs) in everyday environments, the user base of these powerful and potentially intelligent machines is expanding beyond exclusively highly trained vehicle operators to include non-expert system users. Scientists seeking to augment costly and often inflexible methods of data collection historically used are turning towards lower cost and reconfigurable UAVs. These new users require more intuitive and natural methods for UAV mission planning. This paper explores two natural language interfaces - gesture and speech - for UAV flight path generation through individual user studies. Subjects who participated in the user studies also used a mouse-based interface for a baseline comparison. Each interface allowed the user to build flight paths from a library of twelve individual trajectory segments. Individual user studies evaluated performance, efficacy, and ease-of-use of each interface using background surveys, subjective questionnaires, and observations on time and correctness. Analysis indicates that natural language interfaces are promising alternatives to traditional interfaces. The user study data collected on the efficacy and potential of each interface will be used to inform future intuitive UAV interface design for non-expert users.
User experience and visual design are greatly improved when usability testing is performed on a periodic basis. Design decisions should be tested by real users so that application owners can understand the effectiveness of each decision and identify areas for improvement. It is important that applications be tested not just once, but as a part of a continuing process that looks to build upon previous tests. NASA's Earthdata Search Client has undergone a usability study to ensure its users' needs are being met and that users understand how to use the tool efficiently and effectively. This poster will highlight the process followed for usability study, the results of the study, and what has been implemented in light of the results to improve the application's interface.
Users of the Orbiter/Spacelab combination will require both higher electrical power and longer duration than is available with the current baseline system. Present Orbiter/Spacelab mission capability is primarily constrained by the hydrogen and oxygen available to generate power in the Orbiter fuel cells. It is also necessary to assure that considerable attitude or point flexibility is retained to assure efficient operation of the Orbiter radiator cooling system. Beyond these early limitations, it is foreseen that orbital operations will eventually need even greater quantities of the basic space utilities: electrical power; heat rejection; and attitude control. Such operations, forecasted for the mid to late 1980's, will be best accommodated by a module stored in orbit that can furnish these to a docked Orbiter/Spacelab or other vehicles. The Orbital Service Module concept to provide for these services is presented.
The purpose of the BRAVO User's Manual is to describe the BRAVO methodology in terms of step-by-step procedures. The BRAVO methodology then becomes a tool which a team of analysts can utilize to perform cost effectiveness analyses on potential future space applications with a relatively general set of input information and a relatively small expenditure of resources. An overview of the BRAVO procedure is given by describing the complete procedure in a general form.
The effect of the changes incorporated in the LANDSAT D system on the ability of a local user terminal to receive, record and process data in real time was studied. Alternate solutions to the problems raised by these changes were evaluated. A loading analysis was performed in order to determine the quantities of data that a local user terminal (LUT) would be interested in receiving and processing. The number of bits in an MSS and a TM scene were calculated along with the number of scenes per day that an LUT might require for processing. These then combined to a total number of processed bits/day for an LUT as a function of sensor and coverage circle radius.
A users's manual for the computer programs involved in a study of the space tug docking simulation is presented. The following subjects are considered: (1) subroutine narratives, (2) program elements, (3) system subroutines, and (4) Univac 1108 cross reference listing. The functional and operational requirements for the computer programming are explained.
The following tasks related to the FY 74 Shuttle Users Analysis were completed: (1) STS user charge analysis, (2) business risk and value of operations in space (BRAVO) analysis, and (3) standardized subsystem module analysis. The first task was required to initiate the process of furnishing transportation charge estimates for STS payloads to STS users.
This half-day tutorial will provide an overview of basic perceptual functioning as it relates to the design of virtual environment systems. The tutorial consists of three parts. First, basic issues in visual perception will be presented, including discussions of the visual sensations of brightness and color, and the visual perception of depth relationships in three-dimensional space (with a special emphasis on motion -specified depth). The second section will discuss the importance of conducting human-factors user studies and evaluations. Examples and suggestions on how best to get help with user studies will be provided. Finally, we will discuss how, by drawing on their complementary competencies, perceptual psychologists and computer engineers can work as a team to develop optimal VR systems, technologies, and techniques.
A six-month systems study of earth resource surveys from satellites was conducted and is reported. SKYLAB S-192 multispectral scanner (MSS) data were used as a baseline to aid in evaluating the characteristics of future systems using satellite MSS sensors. The study took the viewpoint that overall system (sensor and processing) characteristics and parameter values should be determined largely by user requirements for automatic information extraction performance in quasi-operational earth resources surveys, the other major factor being hardware limitations imposed by state-of-the-art technology and cost. The objective was to use actual aircraft and spacecraft MSS data to outline parametrically the trade-offs between user performance requirements and hardware performance and limitations so as to allow subsequent evaluation of compromises which must be made in deciding what system(s) to build.
Data management for the Spacelab Program is considered with particular attention to the human role in the process.
Cost comparisons were made between three modes of operation (expend, ground refurbish, and space resupply) for the Earth Observation System (EOS-B) to furnish data to NASA on alternative ways to use the shuttle/EOS. Results of the analysis are presented in tabular form.