Search NASA⌕ Search

SEARCH · Search NASA

Results for “user research”

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 19 records

Marine decision aids from space

The article discusses satellite observation of marine environments via microwave sensors and visible/infrared measurements. Specific applications include the monitoring of physical oceanography, weather and climate, coastal processes, ice processes, and resource use management. Four types of information delivery systems are identified: direct-to-user, regional/local user, global modeling user, and research user modes. Current developments in the marine information system include onboard correlation of synthetic aperture radar images at 10 to 100 m resolutions, and the extraction of wave, ship, iceberg or areal feature information from the image or signal before correlation.

Nagler, R. G.↗

Zero Gravity Research Facility User's Guide

The Zero Gravity Research Facility (ZGF) is operated by the Space Experiments Division of the NASA John H. Glenn Research Center (GRC) for investigators sponsored by the Microgravity Science and Applications Division of NASA Headquarters. This unique facility has been utilized by scientists and engineers for reduced gravity experimentation since 1966. The ZGF has provided fundamental scientific information, has been used as an important test facility in the space flight hardware design, development, and test process, and has also been a valuable source of data in the flight experiment definition process. The purpose of this document is to provide information and guidance to prospective researchers regarding the design, buildup, and testing of microgravity experiments.

Thompson, Dennis M.↗

Top-down methodology for human factors research

User computer interaction as a conversation is discussed. The design of user interfaces which depends on viewing communications between a user and the computer as a conversion is presented. This conversation includes inputs to the computer (outputs from the user), outputs from the computer (inputs to the user), and the sequencing in both time and space of those outputs and inputs. The conversation is viewed from the user's side of the conversation. Two languages are modeled: the one with which the user communicates with the computer and the language where communication flows from the computer to the user. Both languages exist on three levels; the semantic, syntactic and lexical. It is suggested that natural languages can also be considered in these terms.

Sibert, J.↗

Evolution of International Space Station Program Safety Review Processes and Tools

The International Space Station Program at NASA is constantly seeking to improve the processes and systems that support safe space operations. To that end, the ISS Program decided to upgrade their Safety and Hazard data systems with 3 goals: make safety and hazard data more accessible; better support the interconnection of different types of safety data; and increase the efficiency (and compliance) of safety-related processes. These goals are accomplished by moving data into a web-based structured data system that includes strong process support and supports integration with other information systems. Along with the data systems, ISS is evolving its submission requirements and safety process requirements to support the improved model. In contrast to existing operations (where paper processes and electronic file repositories are used for safety data management) the web-based solution provides the program with dramatically faster access to records, the ability to search for and reference specific data within records, reduced workload for hazard updates and approval, and process support including digital signatures and controlled record workflow. In addition, integration with other key data systems provides assistance with assessments of flight readiness, more efficient review and approval of operational controls and better tracking of international safety certifications. This approach will also provide new opportunities to streamline the sharing of data with ISS international partners while maintaining compliance with applicable laws and respecting restrictions on proprietary data. One goal of this paper is to outline the approach taken by the ISS Progrm to determine requirements for the new system and to devise a practical and efficient implementation strategy. From conception through implementation, ISS and NASA partners utilized a user-centered software development approach focused on user research and iterative design methods. The user-centered approach used on the new ISS hazard system utilized focused user research and iterative design methods employed by the Human Computer Interaction Group at NASA Ames Research Center. Particularly, the approach emphasized the reduction of workload associated with document and data management activities so more resources can be allocated to the operational use of data in problem solving, safety analysis, and recurrence control. The methods and techniques used to understand existing processes and systems, to recognize opportunities for improvement, and to design and review improvements are described with the intent that similar techniques can be employed elsewhere in safety operations. A second goal of this paper is to provide and overview of the web-based data system implemented by ISS. The software selected for the ISS hazard systemMission Assurance System (MAS)is a NASA-customized vairant of the open source software project Bugzilla. The origin and history of MAS as a NASA software project and the rationale for (and advantages of) using open-source software are documented elsewhere (Green, et al., 2009).

Ratterman, Christian D.↗

Practicing UX at NASA

My experiences practicing UX at NASA in an engineering driven organization and thoughts on how to communicate the value of user research, usability, and design to skeptics. In this environment hard numbers, requirements, and acronyms rule the conversation. How do you communicate the value of softer concepts such as user research, usability, and design?

UX designer user experience↗

Lightning research: A user's lament

As a user of devices and procedures for lightning protection, the author is asking the lightning research community for cookbook recipes to help him solve his problems. He is lamenting that realistic devices are scarce and that his mission does not allow him the time nor the wherewithal to bridge the gap between research and applications. A few case histories are presented. In return for their help he is offering researchers a key to lightning technology--the use of the Eastern Test Range and its extensive resources as a proving ground for their experiment in the lightning capital of the United States. A current example is given--a joint lightning characterization project to take place there. Typical resources are listed.

Golub, C. N.↗

Research report: User's manual for computer program AT81y003 SHABERTH. Steady state and transient thermal analysis of a shaft bearing system including ball, cylindrical and tapered roller bearings

The SHABERTH program is capable of simulating the thermomechanical performance of a load support system consisting of a flexible shaft supported by up to five rolling element bearings. Any combination of ball, cylindrical, and tapered roller bearings can be used to support the shaft. The user can select models in calculating lubricant film thickness and traction forces. The formulation of the cage pocket/rolling element interaction model was revised to improve solution numerical convergence characteristics.

Hadden, G. B.↗

The Multi-Attribute Task Battery II (MATB-II) Software for Human Performance and Workload Research: A User's Guide

The Multi-Attribute Task Battery (MAT Battery). is a computer-based task designed to evaluate operator performance and workload, has been redeveloped to operate in Windows XP Service Pack 3, Windows Vista and Windows 7 operating systems.MATB-II includes essentially the same tasks as the original MAT Battery, plus new configuration options including a graphical user interface for controlling modes of operation. MATB-II can be executed either in training or testing mode, as defined by the MATB-II configuration file. The configuration file also allows set up of the default timeouts for the tasks, the flow rates of the pumps and tank levels of the Resource Management (RESMAN) task. MATB-II comes with a default event file that an experimenter can modify and adapt

Santiago-Espada, Yamira↗

Preliminary Design of an 'Autonomous Medical Response Agent' Interface Prototype for Long Duration Spaceflight

Major challenges for astronauts in future long-duration exploration missions (LDEMs) will be that crewmembers are not expected to be medical professionals, may be under high workload and stress, are facing physiological challenges caused by spaceflight, and will have limited, delayed voice communications with medical support from Earth. An autonomous medical response agent (AMRA) is envisioned to help astronauts address medical complaints, develop a differential diagnosis, and guide self-treatment until a healthy state is restored. AMRA develops a process of personalized diagnosis and treatment through a Bayesian predictive control system that recommends therapeutic control actions including diagnostic tests and treatments to crewmembers (Menon, 2020). The Human Computer Interaction (HCI) lab from NASA Ames Research Center’s Human Systems Integration Division (Code TH) has collaborated with Nahlia Inc in human-centered design augmentation research for AMRA. The project, titled Design of ‘Autonomous Medical Response Agent Interface Prototype for Long Duration Spaceflight, has been funded by the Translational Research Institute for Space Health (TRISH) and introduces an interactive user-interface prototype that guides astronauts through self-diagnosis, treatment, and rehabilitation while communicating with remote specialists in ground support (most notably a patient’s flight surgeon). Our project develops the interaction design for the crewmember using AMRA through user research, iterative design, and usability testing to evaluate the user interface and workflow designed. The interface design deliverable for this project, titled AMRA Aggregate Information Display (AMRA AID) is an integrated information display system for comprehensive autonomous medical guidance, diagnosis, and treatment of in-flight medical conditions experienced by crewmembers. AMRA AID demonstrates how we might ensure crew autonomy, increase the crew’s medical capabilities, and decrease cognitive burden within a front-end user interface. AMRA AID refrains from relying on input from ground or mission control for self-treatment of medical issues—though ground awareness and communication with ground is maintained as a means of ensuring trust between mission control and crew. AMRA AID demonstrates how the crew’s on-board medical system might integrate with information from vehicle monitoring and crew schedule, without assuming causal relationships. AMRA AID’s comprehensive view enables efficient information access for both crew and ground support, reducing cognitive burden in the event of an unplanned or emergency medical incident and enabling informed analytical decisions to be made based on both crew and vehicle health. Human-centered design augmentation advanced within the prototype included: enhanced workflow and treatment guidance for two medical scenarios for a non-specialist user base with various levels of medical training, interaction design which considered speech (conversational user interface) elements and on-screen interactions to be developed in future iterations of the project, communication design and functional requirements relevant to self-care versus caring for another astronaut, as well as user testing of the prototype with an international space medical community. This project arrives at critical findings regarding usability needs, communication requirements, and integrated information requirements for a future technology interface functioning to increase confidence between ground support and LDEM crewmembers.

TRISH↗

Investigating Access Performance of Long Time Series with Restructured Big Model Data

Data sets generated by models are substantially increasing in volume, due to increases in spatial and temporal resolution, and the number of output variables. Many users wish to download subsetted data in preferred data formats and structures, as it is getting increasingly difficult to handle the original full-size data files. For example, application research users such as those involved with wind or solar energy, or extreme weather events are likely only interested in daily or hourly model data at a single point (or for a small area) for a long time period, and prefer to have the data downloaded in a single file. With native model file structures, such as hourly data from NASA Modern-Era Retrospective analysis for Research and Applications Version-2 (MERRA-2), it may take over 10 hours for the extraction of parameters-of-interest at a single point for 30 years. The NASA Goddard Earth Sciences Data and Information Services Center (GES DISC) is exploring methods to address this particular user need. One approach is to create value-added data by reconstructing the data files. Taking MERRA-2 data as an example, we have tested converting hourly data from one-day-per-file into different data cubes, such as one-month, or one-year. Performance is compared for reading local data files and accessing data through interoperable services, such as OPeNDAP. Results show that, compared to the original file structure, the new data cubes offer much better performance for accessing long time series. We have noticed that performance is associated with the cube size and structure, the compression method, and how the data are accessed. An optimized data cube structure will not only improve data access, but also may enable better online analysis services

reanalysis↗

Designing Interfaces for Astronaut Autonomy in Space

As we move towards human deep space missions, astronauts will no longer be able to say, Houston, we have a problem. The restricted contact with mission control because of the incredible distance from Earth will require astronauts to make autonomous decisions. How will astronauts take on the roles of mission control? This is an area of active research that has far reaching implications for the future of distant spaceflight. Come to this talk to hear how we are using design and user research to come up with innovative solutions for astronauts to effectively explore the Moon, Mars, and beyond.

design↗

Terrestrial Hydrological Data from NASA's Hydrology Data and Information Services Center (HDISC): Products, Services, and Applications

Terrestrial hydrological variables are important in global hydrology, climate, and carbon cycle studies. The North American and Global Land Data Assimilation Systems (NLDAS and GLDAS, respectively) have been generating a series of land surface states (soil moisture, snow, and temperature) and fluxes (evapotranspiration, radiation, and heat flux) variables. These data, hosted at and available from NASA s Hydrology Data and Information Services Center (HDISC), include the NLDAS hourly 1/8 degree products and the GLDAS 3-hourly 0.25 and 1.0 degree products. HDISC provides easy access and visualization and analysis capabilities for these products, thus reducing the time and resources spent by scientists on data management and facilitating hydrological research. Users can perform spatial and parameter subsetting, data format transformation, and data analysis operations without needing to first download the data. HDISC is continually being developed as a data and services portal that supports weather and climate forecasts, and water and energy cycle research.

Fang, Hongliang↗

Essential Water Variables (EWVs) for Water Cycle Research & Water Sustainability Applications

The Group on Earth Observations System of Systems (GEOSS) Water Strategy Report (WSR), From Observations to Decisions (2014), identifies several key water variables as Essential Water Variables (EWVs). This was based on an earlier (2010) meta-survey of water-related observational needs for GEO Societal Benefit Areas (SBAs). EWVs have also been surveyed by GEO Global Water Sustainability (GEOGloWS) for operational relevance. This paper summarizes EWVs required by key end-user research and applications sectors. As a follow up to the WSR, we highlight the relevance of EWVs to the indicator-monitoring objectives of the UN Sustainable Development Goals (SDGs). We also identify those that are supported by Remote Sensing and/or In situ observing platforms. The GEO Virtual Symposium is invited to comment on, endorse, and/or recommend additional EWVs that should be considered for adoption by GEOGloWS and GEO.

water variables↗

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↗

Aeronautics Autonomy Testbed Capability (AATC) Team Developed Concepts

In 2015, the National Aeronautics and Space Administration (NASA) formed a multi-center, interdisciplinary team of engineers from three different aeronautics research centers who were tasked with improving NASA autonomy research capabilities. This group was subsequently named the Aeronautics Autonomy Testbed Capability (AATC) team. To aid in confronting the autonomy research directive, NASA contracted IDEO, a design firm, to provide consultants and guides to educate NASA engineers through the practice of design thinking, which is an unconventional method for aerospace design processes. The team then began learning about autonomy research challenges by conducting interviews with a diverse group of researchers and pilots, military personnel and civilians, experts and amateurs. Part of this design thinking process involved developing ideas for products or programs known as concepts that could enable real world fulfillment of the most important latent needs identified through analysis of the interviews. The concepts are intended to be sacrificial, intermediate steps in the design thinking process and are presented in this report to record the efforts of the AATC group. Descriptions are provided in present tense to allow for further ideation and imagining the concept as reality as was attempted during the teams discussions and interviews. This does not indicate that the concepts are actually in practice within NASA though there may be similar existing programs independent of AATC. These concepts were primarily created at two distinct stages during the design thinking process. After the initial interviews, there was a workshop for concept development and the resulting ideas are shown in this work as from the First Round. As part of succeeding interviews, the team members presented the First Round concepts to refine the understanding of existing research needs. This knowledge was then used to generate an additional set of concepts denoted as the Second Round. Some concepts were created by a single person in a few minutes while others were refined by the entire team over several weeks. Thus, certain ideas are more detailed than others but those from the second round are not necessarily more comprehensive than the first round concepts. Primarily, as reported here in the Second Round section, the designs serve to encompass more of the high level end user research needs which were not necessarily known to the team during the prior workshop. In the figures provided throughout this report, illustrations are often provided to represent a concept. Nearly all of the images are informal sketches or renderings and this casualness should, hopefully, not be held to negate the potential insights available within the concepts.

Smith, Phillip J.↗