Search NASA⌕ Search

SEARCH · Search NASA

Results for “Users”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2004

Graphical User Interface Development for Representing Air Flow Patterns

In the Turbine Branch, scientists carry out experimental and computational work to advance the efficiency and diminish the noise production of jet engine turbines. One way to do this is by decreasing the heat that the turbine blades receive. Most of the experimental work is carried out by taking a single turbine blade and analyzing the air flow patterns around it, because this data indicates the sections of the turbine blade that are getting too hot. Since the cost of doing turbine blade air flow experiments is very high, researchers try to do computational work that fits the experimental data. The goal of computational fluid dynamics is for scientists to find a numerical way to predict the complex flow patterns around different turbine blades without physically having to perform tests or costly experiments. When visualizing flow patterns, scientists need a way to represent the flow conditions around a turbine blade. A researcher will assign specific zones that surround the turbine blade. In a two-dimensional view, the zones are usually quadrilaterals. The next step is to assign boundary conditions which define how the flow enters or exits one side of a zone. way of setting up computational zones and grids, visualizing flow patterns, and storing all the flow conditions in a file on the computer for future computation. Such a program is necessary because the only method for creating flow pattern graphs is by hand, which is tedious and time-consuming. By using a computer program to create the zones and grids, the graph would be faster to make and easier to edit. Basically, the user would run a program that is an editable graph. The user could click and drag with the mouse to form various zones and grids, then edit the locations of these grids, add flow and boundary conditions, and finally save the graph for future use and analysis. My goal this summer is to create a graphical user interface (GUI) that incorporates all of these elements. I am writing the program in Java, a language that is portable among platforms, because it can run on different operating systems such as Windows and Unix without having to be rewritten. I had no prior experience of programming in Java at the start of my internship; I am continuously learning as I create the program. I have written the part of the program that enables a user to draw several zones, edit them, and store their locations. The next phase of my project is to allow the user to click on the side of a zone and create a boundary condition for it. A previous intern wrote a program that allows the user to input boundary conditions. I can integrate the two programs to create a larger, more usable program. After that, I will develop a way for the user to save the graph for future reference. Another eventual goal is to make the GUI capable of creating three-dimensional zones as well. Researchers such as my mentor, Dr. David Ashpis, need a quick, user-friendly

Chaudhary, Nilika↗
NASA NTRS2016

Anthropomorphic Robot Design and User Interaction Associated with Motion

Though in its original concept a robot was conceived to have some human-like shape, most robots now in use have specific industrial purposes and do not closely resemble humans. Nevertheless, robots that resemble human form in some way have continued to be introduced. They are called anthropomorphic robots. The fact that the user interface to all robots is now highly mediated means that the form of the user interface is not necessarily connected to the robots form, human or otherwise. Consequently, the unique way the design of anthropomorphic robots affects their user interaction is through their general appearance and the way they move. These robots human-like appearance acts as a kind of generalized predictor that gives its operators, and those with whom they may directly work, the expectation that they will behave to some extent like a human. This expectation is especially prominent for interactions with social robots, which are built to enhance it. Often interaction with them may be mainly cognitive because they are not necessarily kinematically intricate enough for complex physical interaction. Their body movement, for example, may be limited to simple wheeled locomotion. An anthropomorphic robot with human form, however, can be kinematically complex and designed, for example, to reproduce the details of human limb, torso, and head movement. Because of the mediated nature of robot control, there remains in general no necessary connection between the specific form of user interface and the anthropomorphic form of the robot. But their anthropomorphic kinematics and dynamics imply that the impact of their design shows up in the way the robot moves. The central finding of this report is that the control of this motion is a basic design element through which the anthropomorphic form can affect user interaction. In particular, designers of anthropomorphic robots can take advantage of the inherent human-like movement to 1) improve the users direct manual control over robot limbs and body positions, 2) improve users ability to detect anomalous robot behavior which could signal malfunction, and 3) enable users to be better able to infer the intent of robot movement. These three benefits of anthropomorphic design are inherent implications of the anthropomorphic form but they need to be recognized by designers as part of anthropomorphic design and explicitly enhanced to maximize their beneficial impact. Examples of such enhancements are provided in this report. If implemented, these benefits of anthropomorphic design can help reduce the risk of Inadequate Design of Human and Automation Robotic Integration (HARI) associated with the HARI-01 gap by providing efficient and dexterous operator control over robots and by improving operator ability to detect malfunctions and understand the intention of robot movement.

automation/robotic integration↗
NASA NTRS2018

Importance and Incorporation of User Feedback in Data Stewardship

Since August 1994, The National Aeronautics and Space Administration's (NASA's) Earth Observation System Data and Information System (EOSDIS) has been serving a global community of over 3 million users with Earth science data in a variety of disciplines. During the entire life of EOSDIS, various mechanisms for user feedback have been extremely important and valuable to its evolution and proven performance. Some inputs from user groups have resulted in fundamental changes in the architecture, design and operations of EOSDIS, while others have provided ideas for incremental changes. The purpose of this paper is to share this experience and the benefits that have resulted from the user feedback.In early to mid-1990s, the EOSDIS Advisory Panel (a.k.a. Data Panel) provided significant inputs for the architecture and design of EOSDIS resulting in NASA's establishment of a set of Distributed Active Archive Centers (DAACs) and development of a "working prototype with operating elements" called Version 0 EOSDIS, which went into operation in August 1994. The Data Panel also participated in many of the requirement and design reviews and influenced the design of EOSDIS through their comments.In 1995, the U.S. National Research Council's Committee on Global Change Research conducted a review of the U.S. Global Change Research Program and NASA's Mission to Planet Earth/EOS, including the plans for EOSDIS. One of this committee's recommendations was that the "Responsibility for product generation and publication and for user services should be transferred to a federation of partners selected through a competitive process open to all". In response, NASA initiated an experiment with a "self-governing" federation called the Working Prototype ESIP (WP-ESIP) Federation. This federation, with support from NASA, NOAA and USGS, has now grown into the Earth Science Information Partners (ESIP) with over 140 member organizations.The EOSDIS DAACs' User Working Groups (UWGs) represent broad user communities served by the respective DAACs. As regular users of the DAACs and experts in their scientific disciplines, the UWG members provide valuable inputs for planning and prioritizing the services as well as addition of new datasets for the benefit of the community.

Research Integrity↗
NASA NTRSDate not supplied

NASA EOSDIS 20 Years of Data Usage and User Assessment in Support of Open Science Initiative

NASA EOS Data and Information System (EOSDIS) has been distributing data to world-wide users free with open access. Since the launch of NASA’s Terra satellite in 1999, more than 10,000 distinct EOS data products have been archived and distributed by NASA-funded Earth Science data centers encompassed by the EOSDIS. As of September 30, 2022, more than 90 PB of data archived by EOSDIS have been made available to public users and during FY 2023 over 60 PB have been distributed to public users worldwide. Over these twenty and more years, it has shown significant increase in the distribution of various data products. This has been possible due to free and open access of the data thereby a step towards open science initiative. The purposes of this study are 1) to perform a comprehensive investigation of the archive and distribution patterns of EOSDIS data products for last 20 years, 2) to identify and characterize the global user community for those data, 3) analyze the increased demand for data products, 4) evaluate distribution of higher level products because those are the ones most frequently used in the studies of natural disasters by public users (those data requestors not involved directly in the production or validation of the data products.) and contribute globally to the advance scientific understanding of the Earth-Atmosphere Systems. Funded by the Earth Science Data and Information System (ESDIS) Project, the ESDIS Metrics System (EMS) collects archive, distribution, and user information from EOSDIS data centers. The information (comprising all data products including heritage datasets going back to the 1990s) is stored in a relational database from which it can be analyzed in many ways. We present several metrics analyses that include data distribution patterns for all, as well as the most frequently requested data products; and user characterizations by country, domain, and Earth Science discipline (e.g., Land, Ocean, Cryosphere) of the requested products. Due to the enormous quantity of data handled by EOSDIS data centers and requirements of future data systems to archive increasing amounts of Earth Science data from future and current Earth Science missions effectively, the results of this study can provide insight on how the user communities have accessed the data and provide guidance for open science initiative.

Lalit Wanchoo↗
NASA NTRS1977

STS pilot user development program

Full exploitation of the STS capabilities will be not only dependent on the extensive use of the STS for known space applications and research, but also on new, innovative ideas of use originating with both current and new users. In recognition of this, NASA has been engaged in a User Development Program for the STS. The program began with four small studies. Each study addressed a separate sector of potential new users to identify techniques and methodologies for user development. The collective results established that a user development function was not only feasible, but necessary for NASA to realize the full potential of the STS. This final report begins with a description of the overall pilot program plan, which involved five specific tasks defined in the contract Statement of Work. Each task is then discussed separately; but two subjects, the development of principal investigators and space processing users, are discussed separately for improved continuity of thought. These discussions are followed by a summary of the primary results and conclusions of the Pilot User Development Program. Specific recommendations of the study are given.

Mcdowell, J. R.↗
NASA NTRS1987

Usage analysis of user files in UNIX

Presented is a user-oriented analysis of short term file usage in a 4.2 BSD UNIX environment. The key aspect of this analysis is a characterization of users and files, which is a departure from the traditional approach of analyzing file references. Two characterization measures are employed: accesses-per-byte (combining fraction of a file referenced and number of references) and file size. This new approach is shown to distinguish differences in files as well as users, which cam be used in efficient file system design, and in creating realistic test workloads for simulations. A multi-stage gamma distribution is shown to closely model the file usage measures. Even though overall file sharing is small, some files belonging to a bulletin board system are accessed by many users, simultaneously and otherwise. Over 50% of users referenced files owned by other users, and over 80% of all files were involved in such references. Based on the differences in files and users, suggestions to improve the system performance were also made.

Devarakonda, Murthy V.↗
NASA NTRS1986

A methodology for the design and evaluation of user interfaces for interactive information systems

The definition of proposed research addressing the development and validation of a methodology for the design and evaluation of user interfaces for interactive information systems is given. The major objectives of this research are: the development of a comprehensive, objective, and generalizable methodology for the design and evaluation of user interfaces for information systems; the development of equations and/or analytical models to characterize user behavior and the performance of a designed interface; the design of a prototype system for the development and administration of user interfaces; and the design and use of controlled experiments to support the research and test/validate the proposed methodology. The proposed design methodology views the user interface as a virtual machine composed of three layers: an interactive layer, a dialogue manager layer, and an application interface layer. A command language model of user system interactions is presented because of its inherent simplicity and structured approach based on interaction events. All interaction events have a common structure based on common generic elements necessary for a successful dialogue. It is shown that, using this model, various types of interfaces could be designed and implemented to accommodate various categories of users. The implementation methodology is discussed in terms of how to store and organize the information.

Dominick, Wayne D.↗
NASA NTRS1988

A representational framework and user-interface for an image understanding workstation

Problems in image understanding involve a wide variety of data (e.g., image arrays, edge maps, 3-D shape models) and processes or algorithms (e.g., convolution, feature extraction, rendering). The underlying structure of an Image Understanding Workstation designed to support mulitple levels and types of representations for both data and processes is described, also the user-interface. The Image Understanding Workstation consists of two parts: the Image Understanding (IU) Framework, and the user-interface. The IU Framework is the set of data and process representations. It includes multiple levels of representation for data such as images (2-D), sketches (2-D), surfaces (2 1/2 D), and models (3-D). The representation scheme for processes characterizes their inputs, outputs, and parameters. Data and processes may reside on different classes of machines. The user-interface to the IU Workstation gives the user convenient access for creating, manipulating, transforming, and displaying image data. The user-interface follows the structure of the IU Framework and gives the user control over multiple types of data and processes. Both the IU Framework and user-interface are implemented on a LISP machine.

Schroeder, Joyce D.↗
NASA NTRS1989

Spatial issues in user interface design from a graphic design perspective

The user interface of a computer system is a visual display that provides information about the status of operations on data within the computer and control options to the user that enable adjustments to these operations. From the very beginning of computer technology the user interface was a spatial display, although its spatial features were not necessarily complex or explicitly recognized by the users. All text and nonverbal signs appeared in a virtual space generally thought of as a single flat plane of symbols. Current technology of high performance workstations permits any element of the display to appear as dynamic, multicolor, 3-D signs in a virtual 3-D space. The complexity of appearance and the user's interaction with the display provide significant challenges to the graphic designer of current and future user interfaces. In particular, spatial depiction provides many opportunities for effective communication of objects, structures, processes, navigation, selection, and manipulation. Issues are presented that are relevant to the graphic designer seeking to optimize the user interface's spatial attributes for effective visual communication.

Marcus, Aaron↗
NASA NTRS1990

Results of the users' requirements survey

The objectives of the High Resolution, High Frame Rate Video Technology (HHVT) Users' Requirements Survey were the following: (1) Document the requirements of potential users of the HHVT system; (2) Establish a data base relating key video parameters to HHVT users; (3) Guide the development of a high resolution, high frame rate video system offering high data storage capacity and high data transmission rates; (4) Allow users to compare their requirements to those of other users and to the state-of-the-art technology; and (5) Allow users to reassess, if necessary, their requirements in the light of existing and near-term technology. The results of the Users' Requirements Survey are presented. The diversity of these requirements indicates a need for developing a video system with great flexibility.

Butcher, Robert L.↗
NASA NTRS1990

Canadian MSAT field trial program user requirements

A wide range of mobile satellite service offerings will be available in late 1993 with the launch of Canada's first satellite devoted almost exclusively to mobile and transportable services. During the last seven years, the Dept. of Communications has been meeting with potential MSAT users in government and the private sector as part of a $20M Communications Trials Program. User trials will be conducted using leased capacity as well as capacity on Canada's MSAT satellite. User requirements are discussed which were identified under the Communications Trials Program. Land, marine, aeronautical, and fixed applications are described from the perspective of the end users. Emphasis is placed on field trials being accomplished using leased capacity such as the marine data trial being implemented by Ultimateast Data Communications, trials using transportable briefcase terminals and additional field trials being considered for implementation with the TMI Mobile Data Service. The pre-MSAT trials that will be conducted using leased capacity are only a limited sample of the overall end user requirements that have been identified to date. Additional end user applications are discussed, along with a summary of user benefits.

Pedersen, Allister↗
NASA NTRS1993

Advanced display object selection methods for enhancing user-computer productivity

The User-Interface Technology Branch at NCCOSC RDT&E Division has been conducting a series of studies to address the suitability of commercial off-the-shelf (COTS) graphic user-interface (GUI) methods for efficiency and performance in critical naval combat systems. This paper presents an advanced selection algorithm and method developed to increase user performance when making selections on tactical displays. The method has also been applied with considerable success to a variety of cursor and pointing tasks. Typical GUI's allow user selection by: (1) moving a cursor with a pointing device such as a mouse, trackball, joystick, touchscreen; and (2) placing the cursor on the object. Examples of GUI objects are the buttons, icons, folders, scroll bars, etc. used in many personal computer and workstation applications. This paper presents an improved method of selection and the theoretical basis for the significant performance gains achieved with various input devices tested. The method is applicable to all GUI styles and display sizes, and is particularly useful for selections on small screens such as notebook computers. Considering the amount of work-hours spent pointing and clicking across all styles of available graphic user-interfaces, the cost/benefit in applying this method to graphic user-interfaces is substantial, with the potential for increasing productivity across thousands of users and applications.

Osga, Glenn A.↗
NASA NTRS1993

Minimum Hamiltonian ascent trajectory evaluation (MASTRE) program (update to automatic flight trajectory design, performance prediction, and vehicle sizing for support of shuttle and shuttle derived vehicles) users manual

Documentation for the User Interface Program for the Minimum Hamiltonian Ascent Trajectory Evaluation (MASTRE) is provided. The User Interface Program is a separate software package designed to ease the user input requirements when using the MASTRE Trajectory Program. This document supplements documentation on the MASTRE Program that consists of the MASTRE Engineering Manual and the MASTRE Programmers Guide. The User Interface Program provides a series of menus and tables using the VAX Screen Management Guideline (SMG) software. These menus and tables allow the user to modify the MASTRE Program input without the need for learning the various program dependent mnemonics. In addition, the User Interface Program allows the user to modify and/or review additional input Namelist and data files, to build and review command files, to formulate and calculate mass properties related data, and to have a plotting capability.

Lyons, J. T.↗
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

International Space Station Alpha user payload operations concept

International Space Station Alpha (ISSA) will accommodate a variety of user payloads investigating diverse scientific and technology disciplines on behalf of five international partners: Canada, Europe, Japan, Russia, and the United States. A combination of crew, automated systems, and ground operations teams will control payload operations that require complementary on-board and ground systems. This paper presents the current planning for the ISSA U.S. user payload operations concept and the functional architecture supporting the concept. It describes various NASA payload operations facilities, their interfaces, user facility flight support, the payload planning system, the onboard and ground data management system, and payload operations crew and ground personnel training. This paper summarizes the payload operations infrastructure and architecture developed at the Marshall Space Flight Center (MSFC) to prepare and conduct ISSA on-orbit payload operations from the Payload Operations Integration Center (POIC), and from various user operations locations. The authors pay particular attention to user data management, which includes interfaces with both the onboard data management system and the ground data system. Discussion covers the functional disciplines that define and support POIC payload operations: Planning, Operations Control, Data Management, and Training. The paper describes potential interfaces between users and the POIC disciplines, from the U.S. user perspective.

Schlagheck, Ronald A.↗
NASA NTRS1995

3DGRAPE/AL User's Manual

This document is a users' manual for a new three-dimensional structured multiple-block volume g generator called 3DGRAPE/AL. It is a significantly improved version of the previously-released a widely-distributed programs 3DGRAPE and 3DMAGGS. It generates volume grids by iteratively solving the Poisson Equations in three-dimensions. The right-hand-side terms are designed so that user-specific; grid cell heights and user-specified grid cell skewness near boundary surfaces result automatically, with little user intervention. The code is written in Fortran-77, and can be installed with or without a simple graphical user interface which allows the user to watch as the grid is generated. An introduction describing the improvements over the antecedent 3DGRAPE code is presented first. Then follows a chapter on the basic grid generator program itself, and comments on installing it. The input is then described in detail. After that is a description of the Graphical User Interface. Five example cases are shown next, with plots of the results. Following that is a chapter on two input filters which allow use of input data generated elsewhere. Last is a treatment of the theory embodied in the code.

Sorenson, Reese L.↗
NASA NTRS1997

Developing a Graphical User Interface for the ALSS Crop Planning Tool

The goal of my project was to create a graphical user interface for a prototype crop scheduler. The crop scheduler was developed by Dr. Jorge Leon and Laura Whitaker for the ALSS (Advanced Life Support System) program. The addition of a system-independent graphical user interface to the crop planning tool will make the application more accessible to a wider range of users and enhance its value as an analysis, design, and planning tool. My presentation will demonstrate the form and functionality of this interface. This graphical user interface allows users to edit system parameters stored in the file system. Data on the interaction of the crew, crops, and waste processing system with the available system resources is organized and labeled. Program output, which is stored in the file system, is also presented to the user in performance-time plots and organized charts. The menu system is designed to guide the user through analysis and decision making tasks, providing some help if necessary. The Java programming language was used to develop this interface in hopes of providing portability and remote operation.

Koehlert, Erik↗
NASA NTRS2008

User Guide for the Anvil Threat Cooridor Forecast Tool V2.4 for AWIPS

The Anvil Tool GUI allows users to select a Data Type, toggle the map refresh on/off, place labels, and choose the Profiler Type (source of the KSC 50 MHz profiler data), the Date- Time of the data, the Center of Plot, and the Station (location of the RAOB or 50 MHz profiler). If the Data Type is Models, the user selects a Fcst Hour (forecast hour) instead of Station. There are menus for User Profiles, Circle Label Options, and Frame Label Options. Labels can be placed near the center circle of the plot and/or at a specified distance and direction from the center of the circle (Center of Plot). The default selection for the map refresh is "ON". When the user creates a new Anvil Tool map with Refresh Map "ON, the plot is automatically displayed in the AWIPS frame. If another Anvil Tool map is already displayed and the user does not change the existing map number shown at the bottom of the GUI, the new Anvil Tool map will overwrite the old one. If the user turns the Refresh Map "OFF", the new Anvil Tool map is created but not automatically displayed. The user can still display the Anvil Tool map through the Maps dropdown menu* as shown in Figure 4.

Barett, Joe H., III↗