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 109 records · Page 6

All sources NASA NTRS DOE OSTI

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 OSTI2015

Controlling user access to electronic resources without password

Described herein are devices and techniques for remotely controlling user access to a restricted computer resource. The process includes pre-determining an association of the restricted computer resource and computer-resource-proximal environmental information. Indicia of user-proximal environmental information are received from a user requesting access to the restricted computer resource. Received indicia of user-proximal environmental information are compared to associated computer-resource-proximal environmental information. User access to the restricted computer resource is selectively granted responsive to a favorable comparison in which the user-proximal environmental information is sufficiently similar to the computer-resource proximal environmental information. In at least some embodiments, the process further includes comparing user-supplied biometric measure and comparing it with a predetermined association of at least one biometric measure of an authorized user. Access to the restricted computer resource is granted in response to a favorable comparison.

97 MATHEMATICS AND COMPUTING↗

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 OSTI2020

Experiences with a Flexible User Research Process to Build Data Change Tools

Scientific software development processes are understood to be distinct from commercial software development practices due to uncertain and evolving states of scientific knowledge. Sustaining these software products is a recognized challenge, but under-examined is the usability and usefulness of such tools to their scientific end users. User research is a well-established set of techniques (e.g., interviews, mockups, usability tests) applied in commercial software projects to develop foundational, generative, and evaluative insights about products and the people who use them. Currently these approaches are not commonly applied and discussed in scientific software development work. The use of user research techniques in scientific environments can be challenging due to the nascent, fluid problem spaces of scientific work, varying scope of projects and their user communities, and funding/economic constraints on projects.In this paper, we reflect on our experiences undertaking a multi-method user research process in the Deduce project. The Deduce project is investigating data change to develop metrics, methods, and tools that will help scientists make decisions around data change. There is a lack of common terminology since the concept of systematically measuring and managing data change is under explored in scientific environments. To bridge this gap we conducted user research that focuses on user practices, needs, and motivations to help us design and develop metrics and tools for data change. This paper contributes reflections and the lessons we have learned from our experiences. We offer key takeaways for scientific software project teams to effectively and flexibly incorporate similar processes into their projects.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2019

Analysis of transit users’ waiting tolerance in response to unplanned service disruptions

Public transit not only provides an affordable, efficient, and green service but also plays a critical role in the development of resilient transportation systems in urban areas. Transit disruption as a common incident in transit service operation can severely affect the resiliency of the transportation system as well as users’ satisfaction. While it is of great interest to transportation authorities to understand passengers’ decision behavior during unplanned transit disruptions in order to implement efficacious recovery strategies, still little is known about users’ behavior in case of such incidents. The scarcity of available data is a major underlying factor for this gap. Utilizing a recently collected data of transit users in the Chicago metropolitan area, this study investigates transit users’ waiting tolerance during unplanned service disruptions and disclose the factors that affect their behavior. A set of interval-censored accelerated failure time models using different survival distributions are developed, compared, and the factors influencing the survival functions of the waiting tolerance are identified. The results of the analysis reveal that, for instance, having experience of using ridesharing services decreases users’ waiting tolerance during a disruption. Further, built-environment attributes (such as the density of pedestrian-oriented links and transit service frequency), availability of alternative modes, transit service type, user’s attitudes, and trip characteristics turn to be significant in users’ decision behavior.

99 GENERAL AND MISCELLANEOUS↗

DOE OSTI2020

Distributing User Code with the CernVM FileSystem

The CernVM FileSystem (CVMFS) is widely used in High Throughput Computing to efficiently distributed experiment code. However, the standard CVMFS publishing tools are designed for a small group of people from each experiment to maintain common software, and the tools are not a good fit for publishing software from numerous users in each experiment. As a result, most user code, such as code to do specific physics analyses, is still sent with every job to the place the job is run. That process is relatively inefficient, especially when the user code is large. To overcome these limitations, we have built a CVMFS user code publication system. This publication system enables users to still submit their code with their jobs but the code is distributed and accessed through the standard CVMFS infrastructure. The user code is automatically deleted from CVMFS after a period of no use. Most of the software for the system is available as a single self-contained open source rpm called cvmfs-user-pub and is available for other deployments.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2020

Data Driven User Emulator

This software generates realistic network traffic to test intrusion detection systems. The most realistic traffic is generated when software is used to drive actual applications, thereby behaving like a real user. Tools that generate such realistic user behavior are called user emulators. However, no existing user emulators use models based on data science and real user data, and they suffer from a decrease in the fidelity of the generated traffic. We develop a user emulator that uses real user data and data science to generate higher fidelity emulation and increase the accuracy of our experimental results.

Oesch, TimothyS.↗

DOE OSTI2013

Disposal Systems Evaluation Framework DSEF User Manual (V.3.0)

The Disposal Systems Evaluation Framework (DSEF) has been developed at Lawrence Livermore National Laboratory (LLNL) to formalize and facilitate the development and documentation of repository conceptual design options for a range of waste forms, geologic environments, repository design concepts, and repository operating modes. DSEF is one component of the Engineered Barrier System (EBS) family of work packages at several national laboratories led by Sandia National Laboratories (SNL), in support of the DOE Office of Nuclear Energy, specifically of the Used Fuel Disposition (UFD) Campaign within the Office of Used Nuclear Fuel Disposition Research and Development (NE-53). DSEF is a knowledge management system that allows the user to intelligently access and draw data from a case library of hundreds of completed thermal analyses (currently 721 cases in the library), and draw input from databases of material properties and repository development cost data (currently the data in these databases are drawn from more than 100 references). The core functionality of DSEF is provided by a Microsoft Office Excel 2010 workbook with macros and form controls that create a structured environment and walk the user through the steps of creating the input data required to perform disposal system evaluations internally and by interfacing with external programs. The user can choose to work with built-in data from the case library of previous analysis cases, from the material property databases, or can define their own input descriptions and data. DSEF uses the Excel worksheet protection (implemented on a sheet by sheet basis) to prevent inadvertent over-writing of formulas with data. When worksheet protection is enabled, the user can see all underlying formulas, and enter data in unprotected cells (the unprotected cells generally correspond to the yellow highlighted cells). Worksheet protection also prevents restructuring the files (adding or deleting rows or columns) and changing the formatting, as well as preventing access to the Visual Basic Editor to prevent modification of the macros. If the user needs to modify the worksheet structure, formulas, or macros, they can contact LLNL to get the password to unprotect the worksheets. However, care should be taken in making any modifications, since the macros and formulas are dependent in some cases on the current structure, range names, and macro subroutines DSEF is set up to retrieve the results of external thermal analysis program runs, summarize them graphically, and provide a template for adding the new results to the Case Library. The Case Library worksheet in DSEF is set up to create a Case Library data record for each new analysis case, at the top of the list of prior cases. Therefore, a separate DSEF file (with unique name) should be saved for each run that is to be archived. Users should submit a copy of their DSEF files to LLNL so that their results can be added to the overall Case Library and made available to other laboratories and stakeholders. LLNL will maintain the DSEF Case Library and make the most current files available on the SNL SharePoint site. The Revision History sheet documents the file evolution. One of the key objectives of DSEF is to allow the user to compare the results of thermal analyses to the thermal constraints of the design components. These comparisons can then be used to consider design, layout, and operating mode modifications to find combinations that can meet the thermal constraints for a given combination of waste form, geologic medium, surface storage time, and system concept of operation.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗