Computational Modeling Repository (CMR): User Experience-Designed Web App for HRP Computational Models
Explore the source record for details and available documents.
R D Atkins↗
SEARCH · Search NASA
Results for “User experience”
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.
Computational Model Repository (CMR): User Experience-Designed Web Application for HRP Computational Models
Explore the source record for details and available documents.
Robyn D Atkins↗
Human factors aspects of control room design
A plan for the design and analysis of a multistation control room is reviewed. It is found that acceptance of the computer based information system by the uses in the control room is mandatory for mission and system success. Criteria to improve computer/user interface include: match of system input/output with user; reliability, compatibility and maintainability; easy to learn and little training needed; self descriptive system; system under user control; transparent language, format and organization; corresponds to user expectations; adaptable to user experience level; fault tolerant; dialog capability user communications needs reflected in flexibility, complexity, power and information load; integrated system; and documentation.
Jenkins, J. P.↗
Evolving UMM-S to Better Accommodate NASA EOSDIS Web User Interfaces and Downloadable Tools for Data Use
EOSDIS has a services metadata model that is growing too complex and trying to serve multiple use cases. A potential solution being explored is to break out the model for front-end and back-end use cases. This talk will discuss how best to accommodate web user interfaces and downloadable tools in NASA's Common Metadata Repository (CMR) and how to model this information for improved discovery centered around the user experience (UI/UX) approach. The challenges and strategy for addressing the evolution of the model will be discussed along with a proposed path forward for implementation.
User Experience↗
Next Gen One Portal Usability Evaluation
Each exercise device on the International Space Station (ISS) has a unique, customized software system interface with unique layouts / hierarchy, and operational principles that require significant crew training. Furthermore, the software programs are not adaptable and provide no real-time feedback or motivation to enhance the exercise experience and/or prevent injuries. Additionally, the graphical user interfaces (GUI) of these systems present information through multiple layers resulting in difficulty navigating to the desired screens and functions. These limitations of current exercise device GUI's lead to increased crew time spent on initiating, loading, performing exercises, logging data and exiting the system. To address these limitations a Next Generation One Portal (NextGen One Portal) Crew Countermeasure System (CMS) was developed, which utilizes the latest industry guidelines in GUI designs to provide an intuitive ease of use approach (i.e., 80% of the functionality gained within 5-10 minutes of initial use without/limited formal training required). This is accomplished by providing a consistent interface using common software to reduce crew training, increase efficiency & user satisfaction while also reducing development & maintenance costs. Results from the usability evaluations showed the NextGen One Portal UI having greater efficiency, learnability, memorability, usability and overall user experience than the current Advanced Resistive Exercise Device (ARED) UI used by astronauts on ISS. Specifically, the design of the One-Portal UI as an app interface similar to those found on the Apple and Google's App Store, assisted many of the participants in grasping the concepts of the interface with minimum training. Although the NextGen One-Portal UI was shown to be an overall better interface, observations by the test facilitators noted specific exercise tasks appeared to have a significant impact on the NextGen One-Portal UI efficiency. Future updates to the NextGen One Portal UI will address these inefficiencies.
Cross, E. V., III↗
Earthdata Search Usability Study Process
User experience (UX) design is the process of enhancing user satisfaction by improving various aspects of the user's interaction with an application or website. One aspect of UX design is usability, or the extent to which an application can be used to to accomplish tasks efficiently, effectively, and with satisfaction. NASA's Earthdata Search Client recently underwent a focused usability testing project to measure usability and gain valuable user feedback and insights to increase usability for its end-users. This presentation focuses on the process by which the usability tests were administered and the lessons learned throughout the process.
UI↗
Experience in highly parallel processing using DAP
Distributed Array Processors (DAP) have been in day to day use for ten years and a large amount of user experience has been gained. The profile of user applications is similar to that of the Massively Parallel Processor (MPP) working group. Experience has shown that contrary to expectations, highly parallel systems provide excellent performance on so-called dirty problems such as the physics part of meteorological codes. The reasons for this observation are discussed. The arguments against replacing bit processors with floating point processors are also discussed.
Parkinson, D.↗
Transportable Applications Environment (TAE) Tenth Users' Conference
Conference proceedings are represented in graphic visual-aid form. Presentation and panel discussion topics include user experiences with C++ and Ada; the design and interaction of the user interface; the history and goals of TAE; commercialization and testing of TAE Plus; Computer-Human Interaction Models (CHIMES); data driven objects; item-to-item connections and object dependencies; and integration with other software. There follows a list of conference attendees.
Rouff, Chris↗
Vertiport Automation Software Architecture and Requirements
The purpose of Vertiport Automation Software Architecture and Requirements was developed to mature the Vertiport Automation System (VAS) described in the High-Density Automated Vertiport ConOps, into a set of artifacts that enable the development of a VAS prototype. The scope of document was to develop: (1) A VAS Software Architecture diagram that logically organizes VAS functionality into specific software components; (2) VAS Software Trade Study identifying existing commercial products and NASA research that can be used in part or with modifications to fulfill VAS functionality. (3) A set of VAS Functional Requirements which decompose the VAS concept into software functionality, including any interfaces and data flows needed; (4) A set of VAS Test Approaches describing a methodology for verification of the VAS Functional Requirements; and (5) An application user experience (UX) design study describing the general features needed in a VAS user interface.
Advanced Air Mobility↗
User definition and mission requirements for unmanned airborne platforms, revised
The airborne measurement requirements of the scientific and applications experiment user community were assessed with respect to the suitability of proposed strawman airborne platforms. These platforms provide a spectrum of measurement capabilities supporting associated mission tradeoffs such as payload weight, operating altitude, range, duration, flight profile control, deployment flexibility, quick response, and recoverability. The results of the survey are used to examine whether the development of platforms is warranted and to determine platform system requirements as well as research and technology needs.
Kuhner, M. B.↗
What's It like to See Earth from Space? Viewing Your World with NASA's Worldview!
When you first see Earth from space, you'll realize it's largely covered in white - our world is quite cloudy! Look closer and you'll discern landmasses, oceans, and regions covered in snow. Look closer still and you'll notice that our world is in constant motion - storms brewing and tracing paths over the oceans, plumes of smoke from wildfires and plumes of ash from volcanic eruptions billowing with the wind, dust storms blowing across the deserts, phytoplankton swirling in the oceans, icebergs floating in the oceans, and you'll see the human footprint on the earth's surface: cities connected by roads and vast swaths of agriculture. NASA's Worldview (https://worldview.earthdata.nasa.gov) interactive web map application provides a platform to view the world as it has been every day for the past 18 years, using data from NASA's fleet of Earth Observing System (EOS) satellites.This presentation will cover the history and development of the Worldview web map application; the 700+ imagery layers that are provided by the Global Imagery Browse Services (GIBS) (https://earthdata.nasa.gov/gibs); current and new features that are in Worldview to constantly improve the user experience; the interdisciplinary nature of the app and how it helps a broad range of user communities discover and interact with NASA satellite imagery; and ongoing efforts to improve Worldview and serve user communities.
Earth Science↗
SIG: Multiple Views on Safety-Critical Automation: Aircraft, Autonomous Vehicles, Air Traffic Management and Satellite Ground Segments Perspectives
This SIG focuses on the engineering of automation in interactive critical systems. Automation has already been studied in a number of (sub-) disciplines and application fields: design, human factors, psychology, (software) engineering, aviation, health care, games. One distinguishing feature of the area we are focusing on is that in the field of interactive critical systems properties such as reliability, dependability, fault tolerance are as important as usability, user experience or overall acceptance issues. The SIG targets at two problem areas: first the engineering of the user interaction with (partly-) autonomous systems: how to design, build and assess autonomous behavior, especially in cases where there is a need to represent on the user interface both autonomous and interactive objects. An example of such integration is the representation of an unmanned aerial vehicle (UAV) (where no direct interaction is possible), together with aircrafts (that have to be instructed by an air traffic controller to avoid the UAV). Second the design and engineering of user interaction in general for autonomous objects/systems (for example a cruise control in a car or an autopilot in an aircraft). The goal of the SIG is to raise interest in the CHI community on the general aspects of automation and to identify a community of researchers and practitioners interested in those increasingly prominent issues of interfaces towards (semi)-autonomous systems. The expected audience should be interested in addressing the issues of integration of mainly unconnected research domains to formulate a new joint research agenda.
human-automation interaction↗
Multiple Views on Safety-Critical Automation: Aircraft, Autonomous Vehicles, Air Traffic Management and Satellite Ground Segments Perspectives
This SIG focuses on the engineering of automation in interactive critical systems. Automation has already been studied in a number of (sub-) disciplines and application fields: design, human factors, psychology, (software) engineering, aviation, health care, games. One distinguishing feature of the area we are focusing on is that in the field of interactive critical systems properties such as reliability, dependability, fault-tolerance are as important as usability, user experience or overall acceptance issues. The SIG targets at two problem areas: first the engineering of the user interaction with (partly-) autonomous systems: how to design, build and assess autonomous behavior, especially in cases where there is a need to represent on the user interface both autonomous and interactive objects. An example of such integration is the representation of an unmanned aerial vehicle (UAV) (where no direct interaction is possible), together with aircrafts (that have to be instructed by an air traffic controller to avoid the UAV). Second the design and engineering of user interaction in general for autonomous objects systems (for example a cruise control in a car or an autopilot in an aircraft). The goal of the SIG is to raise interest in the CHI community on the general aspects of automation and to identify a community of researchers and practitioners interested in those increasingly prominent issues of interfaces towards (semi)-autonomous systems. The expected audience should be interested in addressing the issues of integration of mainly unconnected research domains to formulate a new joint research agenda.
safety-critical automation↗
Planning for Space Station Freedom laboratory payload integration
Space Station Freedom is being developed to support extensive missions involving microgravity research and applications. Requirements for on-orbit payload integration and the simultaneous payload integration of multiple mission increments will provide the stimulus to develop new streamlined integration procedures in order to take advantage of the increased capabilities offered by Freedom. The United States Laboratory and its user accommodations are described. The process of integrating users' experiments and equipment into the United States Laboratory and the Pressurized Logistics Modules is described. This process includes the strategic and tactical phases of Space Station utilization planning. The support that the Work Package 01 Utilization office will provide to the users and hardware developers, in the form of Experiment Integration Engineers, early accommodation assessments, and physical integration of experiment equipment, is described. Plans for integrated payload analytical integration are also described.
Willenberg, Harvey J.↗
Progress Report on the Airborne Composition Standard Variable Name and Time Series Working Groups of the 2017 ESDSWG
The role of NASA's Earth Science Data Systems Working Groups (ESDSWG) is to make recommendations relevant to NASA's Earth science data systems from users' experiences and community insight. Each group works independently, focusing on a unique topic. Progress of two of the 2017 Working Groups will be presented. In a single airborne field campaign, there can be several different instruments and techniques that measure the same parameter on one or more aircraft platforms. Many of these same parameters are measured during different airborne campaigns using similar or different instruments and techniques. The Airborne Composition Standard Variable Name Working Group is working to create a list of variable standard names that can be used across all airborne field campaigns in order to assist in the transition to the ICARTT Version 2.0 file format. The overall goal is to enhance the usability of ICARTT files and the search ability of airborne field campaign data. The Time Series Working Group (TSWG) is a continuation of the 2015 and 2016 Time Series Working Groups. In 2015, we started TSWG with the intention of exploring the new OGC (Open Geospatial Consortium) WaterML 2 standards as a means for encoding point-based time series data from NASA satellites. In this working group, we realized that WaterML 2 might not be the best solution for this type of data, for a number of reasons. Our discussion with experts from other agencies, who have worked on similar issues, identified several challenges that we would need to address. As a result, we made the recommendation to study the new TimeseriesML 1.0 standard of OGC as a potential NASA time series standard. The 2016 TSWG examined closely the TimeseriesML 1.0 and, in coordination with the OGC TimeseriesML Standards Working Group, identified certain gaps in TimeseriesML 1.0 that would need to be addressed for the standard to be applicable to NASA time series data. An engineering report was drafted based on the OGC Engineering Report template, describing recommended changes to TimeseriesML 1.0, in the form of use cases. In 2017, we are conducting interoperability experiments to implement the use cases and demonstrate the feasibility and suitability of these modifications for NASA and related user communities. The results will be incorporated into the existing draft engineering report.
OGC (Open Geospatial Consortium) WaterML 2 standar↗
DMFS: A Data Migration File System for NetBSD
I have recently developed dmfs, a Data Migration File System, for NetBSD. This file system is based on the overlay file system, which is discussed in a separate paper, and provides kernel support for the data migration system being developed by my research group here at NASA/Ames. The file system utilizes an underlying file store to provide the file backing, and coordinates user and system access to the files. It stores its internal meta data in a flat file, which resides on a separate file system. Our data migration system provides archiving and file migration services. System utilities scan the dmfs file system for recently modified files, and archive them to two separate tape stores. Once a file has been doubly archived, files larger than a specified size will be truncated to that size, potentially freeing up large amounts of the underlying file store. Some sites will choose to retain none of the file (deleting its contents entirely from the file system) while others may choose to retain a portion, for instance a preamble describing the remainder of the file. The dmfs layer coordinates access to the file, retaining user-perceived access and modification times, file size, and restricting access to partially migrated files to the portion actually resident. When a user process attempts to read from the non-resident portion of a file, it is blocked and the dmfs layer sends a request to a system daemon to restore the file. As more of the file becomes resident, the user process is permitted to begin accessing the now-resident portions of the file. For simplicity, our data migration system divides a file into two portions, a resident portion followed by an optional non-resident portion. Also, a file is in one of three states: fully resident, fully resident and archived, and (partially) non-resident and archived. For a file which is only partially resident, any attempt to write or truncate the file, or to read a non-resident portion, will trigger a file restoration. Truncations and writes are blocked until the file is fully restored so that a restoration which only partially succeed does not leave the file in an indeterminate state with portions existing only on tape and other portions only in the disk file system. We chose layered file system technology as it permits us to focus on the data migration functionality, and permits end system administrators to choose the underlying file store technology. We chose the overlay layered file system instead of the null layer for two reasons: first to permit our layer to better preserve meta data integrity and second to prevent even root processes from accessing migrated files. This is achieved as the underlying file store becomes inaccessible once the dmfs layer is mounted. We are quite pleased with how the layered file system has turned out. Of the 45 vnode operations in NetBSD, 20 (forty-four percent) required no intervention by our file layer - they are passed directly to the underlying file store. Of the twenty five we do intercept, nine (such as vop_create()) are intercepted only to ensure meta data integrity. Most of the functionality was concentrated in five operations: vop_read, vop_write, vop_getattr, vop_setattr, and vop_fcntl. The first four are the core operations for controlling access to migrated files and preserving the user experience. vop_fcntl, a call generated for a certain class of fcntl codes, provides the command channel used by privileged user programs to communicate with the dmfs layer.
Studenmund, William↗
ERTS-1 data collection system: Status and performance
The Data Collection System flown on the first Earth Resources Technology Satellite (ERTS-1) relays earth resources data from remotely located in-situ sensors to Goddard Space Flight Center. Data is received at Goddard at least twice each day from every sensor installation and is distributed to users (who operate the sensors and transmitters) by mail and teletype. The system consists of a data formatting and transmitting unit, called the Data Collection Platform (DCP), a receiver and a retransmitter aboard ERTS-1; and receiving, demodulating and decoding equipment located at the Goldstone, California and Goddard data acquisition stations. Data is transmitted from the data acquisition stations to the ERTS Control Center at Goddard, then to the NASA (ERTS) Data Processing Facility (NDPF) where it is processed and distributed to users. Experience to date indicates that the design of the ERTS-1 Data Collection System is adequate for operational use for 50% of the users and, with minor modifications, could meet the requirements of 75%. Some users will have to augment the system by other data collection techniques to meet their operational requirements.
Painter, J. E.↗
Earthdata Search Client: Usability Review Process, Results, and Implemented Changes, Using Earthdata Search Client as a Case Study
User experience and visual design are greatly improved when usability testing is performed on a periodic basis. Design decisions should be tested by real users so that application owners can understand the effectiveness of each decision and identify areas for improvement. It is important that applications be tested not just once, but as a part of a continuing process that looks to build upon previous tests. NASA's Earthdata Search Client has undergone a usability study to ensure its users' needs are being met and that users understand how to use the tool efficiently and effectively. This poster will highlight the process followed for usability study, the results of the study, and what has been implemented in light of the results to improve the application's interface.
design↗