SEARCH · Search NASA

Results for “user”

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 73 records · Page 4

All sources NASA NTRS DOE OSTI

DOE OSTI2024

FECM/NETL Natural Gas with Hydrogen Pipeline Cost Model (2024): Description and User’s Manual

This is the user’s manual for The FECM/NETL Natural Gas with Hydrogen Pipeline Cost Model (NG-H2_P_COM) that estimates costs for transporting gaseous hydrogen with natural gas in a pipeline from a source, such as a hydrogen production facility, to a final destination which may be a user of the hydrogen and natural gas or a distribution center where hydrogen in the pipeline with natural gas is diverted to multiple end users. This user’s manual provides two main functions. First, the detailed statement describes the equations and algorithms that are used by the model to calculate technical quantities (such as blend hydrogen percentage, reuse percentage of the pipeline and stations, the pipe diameter size and length needed to transport a user-specified hydrogen with natural gas rate in a specified distance) and engineering-economic quantities (such as capital costs, operating costs, and cash flows). Second, the document is a user’s manual for the model that describes the procedures the user must follow to configure and setup the model, run the model, analyze the results, and visualize the outcomes. Such details offer user a quick and handy way to utilize the model for their application and decision making. The model can be accessed at this URL: https://www.netl.doe.gov/energy-analysis/details?id=cf3f6564-3c55-4aa5-b712-7160e558d9f6. The Model Results and Comparative Analysis can be accessed here: https://www.netl.doe.gov/energy-analysis/details?id=83862799-a28c-4944-a809-90b7e23d4af6.

03 NATURAL GAS↗

NASA NTRS1973

Study of data collection platform concepts: Data collection system user requirements

The overall purpose of the survey was to provide real world data on user requirements. The intent was to assess data collection system user requirements by questioning actual potential users rather than speculating on requirements. The end results of the survey are baseline requirements models for both a data collection platform and a data collection system. These models were derived from the survey results. The real value of these models lies in the fact that they are based on actual user requirements as delineated in the survey questionnaires. Some users desire data collection platforms of small size and light weight. These sizes and weights are beyond the present state of the art. Also, the survey provided a wealth of information on the nature and constituency of the data collection user community as well as information on user applications for data collection systems. Finally, the data sheds light on the generalized platform concept. That is, the diversity of user requirements shown in the data indicates the difficulty that can be anticipated in attempting to implement such a concept.

Source record↗

NASA NTRS1976

Phase 2 STS new user development program. Volume 1: Executive summary

A methodology for developing new users for STS other than NASA and DoD, thereby maximizing the use of the STS system was developed. The approach to user development, reflected in the implementation plan, and attendant informational material to be used were evaluated by conducting a series of test cases with selected user organizations. These test case organizations were, in effect, used as consultants to evaluate the effectiveness, the needs, the completeness, and the adequacy of the user development approach and informational material. The selection of the test cases provided a variety of potential STS users covering industry, other government agencies, and the educational sector. The test cases covered various use areas and provided a mix of user organization types. A summary of the actual test cases conducted is given. The conduct of the test cases verified the general approach of the implementation plan, the validity of the user development strategy prepared for each test case organization and the effectiveness of the STS basic and user customized informational material.

Mcdowell, J. R.↗

NASA NTRS1976

Phase 2 STS new user development program. Volume 4: Guidance/instructions for representatives

The overall STS New User Development (NUD) Function is shown. The user development function is directly responsible for implementing the strategy derived to develop a specific, prospective new user. The burden of actually developing the user falls on the NUD representative, and the success of his user contacts will depend upon how well he is prepared to interface with the user. The guidance/instructions as to what a NUD representative needs to know about the prospective user, and the type of data he should provide when calling on a potential user, are presented.

Mcdowell, J. R.↗

NASA NTRS1980

Seasat data applications by commercial users

The Seasat Program was initiated as a proof-of-concept mission to evaluate the effectiveness of a study of remotely sensed oceanographic phenomena from a satellite platform. From its inception the Seasat Program has been user-oriented. The user comprised three major segments of the ocean community, including academic users, users within various government agencies, and commercial users. Commercial users represent a broad spectrum of commercial marine industries. The commercial users proposed to NASA to carry out a pilot demonstration to assess the utility of Seasat data in the private sector. The commercial users' program is considered along with case studies that utilize Seasat data, and aspects of real-time system operation. Attention is given to the potential value of an employment of synthetic aperture radar, the altimeter, the scatterometer, and the scanning multichannel microwave radiometer.

Montgomery, D. R.↗

NASA NTRS1990

Compensating user position for GPS ephemeris error

A method for canceling the effect of GPS ephemeris error on user position is proposed. In this method, the baseline vectors from the reference stations to the user are estimated without adjusting the GPS ephemeris. The user position is computed by adjustment using differenced data from the user and each station separately and averaging the results with weights inversely proportional to the lengths of the baselines. Alternatively, the differenced data can be averaged in a similar manner before the user position is estimated. The averaging procedure cancels most of the ephemeris error because the error is proportional to the length of the baseline. A numerical simulation is performed to demonstrate and evaluate the method. Two reference stations with perfectly known locations are assumed to be placed several hundred kilometers apart. A user receiver with a poorly known location is located between the stations. The user positions are first estimated separately using data from the user and each station and then averaged. The averaging reduces the error by about one order of magnitude.

Wu, J. T.↗

NASA NTRS1994

FAST User Guide

The Flow Analysis Software Toolkit, FAST, is a software environment for visualizing data. FAST is a collection of separate programs (modules) that run simultaneously and allow the user to examine the results of numerical and experimental simulations. The user can load data files, perform calculations on the data, visualize the results of these calculations, construct scenes of 3D graphical objects, and plot, animate and record the scenes. Computational Fluid Dynamics (CFD) visualization is the primary intended use of FAST, but FAST can also assist in the analysis of other types of data. FAST combines the capabilities of such programs as PLOT3D, RIP, SURF, and GAS into one environment with modules that share data. Sharing data between modules eliminates the drudgery of transferring data between programs. All the modules in the FAST environment have a consistent, highly interactive graphical user interface. Most commands are entered by pointing and'clicking. The modular construction of FAST makes it flexible and extensible. The environment can be custom configured and new modules can be developed and added as needed. The following modules have been developed for FAST: VIEWER, FILE IO, CALCULATOR, SURFER, TOPOLOGY, PLOTTER, TITLER, TRACER, ARCGRAPH, GQ, SURFERU, SHOTET, and ISOLEVU. A utility is also included to make the inclusion of user defined modules in the FAST environment easy. The VIEWER module is the central control for the FAST environment. From VIEWER, the user can-change object attributes, interactively position objects in three-dimensional space, define and save scenes, create animations, spawn new FAST modules, add additional view windows, and save and execute command scripts. The FAST User Guide uses text and FAST MAPS (graphical representations of the entire user interface) to guide the user through the use of FAST. Chapters include: Maps, Overview, Tips, Getting Started Tutorial, a separate chapter for each module, file formats, and system administration.

Walatka, Pamela P.↗

NASA NTRS1998

Collaborative Arrival Planning: Data Sharing and User Preference Tools

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

Zelenka, Richard E.↗

NASA NTRS2003

Discrete Abstractions of Hybrid Systems: Verification of Safety and Application to User-Interface Design

Human interaction with a complex control system involves the user, the automation’s discrete mode logic, and the underlying continuous dynamics of the physical system. The user-interface of such systems always displays a reduced set of information about the entire system. Designing interfaces such that all the pertinent information is available and assuring that this information is correct is important for any user-interface, but especially so for safety-critical systems such as automotive systems and autopilots. Here we describe a methodology for the analysis of hybrid control systems that incorporate user interaction, with the goal of assuring that the information provided to the user is correct. That is, the user-interface must contain all information necessary to safely complete a desired procedure or task. We begin with a hybrid system model which incorporates discrete mode logic as well as nonlinear continuous dynamics. Using a hybrid computational tool for reachability, we find the largest region of the state-space in which we can guarantee the state of the system can always remain – this is the safe region of operation. By implementing a controller for safety which arises from this computation, we mathematically guarantee that this safe region is invariant, meaning that the system will always remain within the safe region if the determined controller is used on the boundary of the safe region. Verification within a hybrid framework allows us to account for the continuous dynamics underlying the discrete representations displayed to the user. Using the computed invariant regions as discrete states, we can abstract a discrete event system from this hybrid system with safety restrictions. This abstraction can be used to determine what information must be provided on the display. Furthermore, in cases in which an interface already exists, the abstraction provides the necessary input into existing interface verification methods. We provide two examples: a car traveling through a yellow light at an intersection and an aircraft autopilot in an automatic landing/go-around maneuver. The examples demonstrate the applicability of this methodology to hybrid systems that have operational constraints we can pose in terms of safety. This methodology differs from existing work in hybrid system verification in that we directly account for the user’s interactions with the system.

Meeko Oishi↗

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↗

DOE OSTI2024

User-Centered Software Design in the All Hazards Analysis Application

To design good software, you must always keep the end user in mind. Some benefits of incorporating the user-centered design process include saving users time and effort and helping them to utilize all capabilites of an application. In my work on the All Hazards Analysis (AHA) application, I employed principles of user-centered design to make the application easier for new users to navigate. This poster describes user-centered software design in general and showcases some of my user-centered design work on the AHA application.

58 GEOSCIENCES↗

DOE OSTI2025

The User Guide for the ComPro Database

An extensive database of glass composition and durability data has been compiled at Savannah River National Laboratory to support the development of nuclear waste glasses. This database is referred to as the Glass Composition-Properties Database (ComPro). The ComPro Database, Revision 3, contains 14,134 total rows of data and 125 columns of composition, durability, as defined by the Product Consistency Test, and other fabrication and characterization information, if available, for each glass. Of the 14,134 total rows, 8,484 rows have been classified as “Model” data and 5,650 rows have been classified as “Non-Model” data. An integral supplement to the ComPro database is the User Guide. The User Guide was developed as a tool to aid the End User in a more effective use of the ComPro database. The User Guide provides a road-map of the specific datasets that comprise the ComPro database (both “Model” and “Non-Model” data) as well as a technical basis for the terminology and definitions the End User will encounter. In this report, a general description of the format and information contained in the User Guide is provided. In addition, specific terminology used in the User Guide is also discussed.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

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.↗