Search NASA⌕ Search

SEARCH · Search NASA

Results for “Data usability”

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 469 records · Page 26
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

How Usability Testing Resulted in Improvements to Ground Collision Software for General Aviation: Improved Ground Collision Avoidance System (IGCAS)

The NASA improved Ground Collision Avoidance System (iGCAS) team conducted an onsite usability study at Experimental Aircraft Association (EAA) Air Venture in Oshkosh, Wisconsin from July 19 through July 26, 2015. EAA Air Venture had approximately 550,000 attendees from which the sample pool of pilots were selected. The objectives of this study were to assess the overall appropriateness and acceptability of iGCAS as a warning system for General Aviation aircraft, usability of the iGCAS displays and audio cues, test terrain avoidance characteristics, performance, functionality, pilot response time, and correlate terrain avoidance performance and pilot response time data.

collision avoidance↗
NASA NTRSDate not supplied

Evolution of the Next Exploration Toilet through Human-in-the-Loop (HITL) Testing

Human waste collection in space is a unique and necessary function that all crewmembers must perform. The variability in how each crewmember uses the toilet to urinate and defecate introduces complexities and challenges with regards to overall hardware design. Because of this variability, it is important to consider crew inputs in all aspects of a toilet design especially with regards to crew interfaces that could impact overall waste collection. Access to crew feedback is essential to the design process and should be considered early and often through the various design phases. In 2020, NASA started a project for the Human Landing System (HLS) program to develop a Government Furnished Equipment (GFE) toilet option. The project is known as the Lavatory On-Orbit (LOO). During the early development of the LOO, the project team conducted several crew evaluations to collect and summarize valuable crew feedback on system design, function, and overall usability to influence the next design iteration. Because every person could use the system differently in space, it was extremely important to collect and analyze the data in a very methodical manner to appropriately influence the design based on the evaluation results. Establishing a standard process ensures consistent data collection from one evaluation to another, helps to maintain privacy for each test subject’s inputs and removes any potential bias from test subject to test subject. To date, the team has completed four crew evaluations on prototypes for the different LOO hardware. This paper will summarize the methodology used to conduct the evaluations as well as how data was collected and analyzed. The paper will also provide details on each of the evaluations and how the design was updated based on the results.

toilet↗
NASA NTRSDate not supplied

Evolution of the Next Exploration Toilet Through Human-in-the-Loop (HITL) Testing

Human waste collection in space is a unique and necessary function that all crewmembers must perform. The variability in how each crewmember uses the toilet to urinate and defecate introduces complexities and challenges with regards to overall hardware design. Because of this variability, it is important to consider crew inputs in all aspects of a toilet design especially with regards to crew interfaces that could impact overall waste collection. Access to crew feedback is essential to the design process and should be considered early and often through the various design phases. In 2020, NASA started a project for the Human Landing System (HLS) program to develop a Government Furnished Equipment (GFE) toilet option. The project is known as the Lavatory On-Orbit (LOO). During the early development of the LOO, the project team conducted several crew evaluations to collect and summarize valuable crew feedback on system design, function, and overall usability to influence the next design iteration. Because every person could use the system differently in space, it was extremely important to collect and analyze the data in a very methodical manner to appropriately influence the design based on the evaluation results. Establishing a standard process ensures consistent data collection from one evaluation to another, helps to maintain privacy for each test subject’s inputs and removes any potential bias from test subject to test subject. To date, the team has completed four crew evaluations on prototypes for the different LOO hardware. This paper will summarize the methodology used to conduct the evaluations as well as how data was collected and analyzed. The paper will also provide details on each of the evaluations and how the design was updated based on the results.

toilet↗
NASA NTRSDate not supplied

Evolution of the Next Exploration Toilet Through Human-in-the-Loop (HITL) Testing

Human waste collection in space is a unique and necessary function that all crewmembers must perform. The variability in how each crewmember uses the toilet to urinate and defecate introduces complexities and challenges with regards to overall hardware design. Because of this variability, it is important to consider crew inputs in all aspects of a toilet design especially with regards to crew interfaces that could impact overall waste collection. Access to crew feedback is essential to the design process and should be considered early and often through the various design phases. In 2020, NASA started a project for the Human Landing System (HLS) program to develop a Government Furnished Equipment (GFE) toilet option. The project is known as the Lavatory On-Orbit (LOO). During the early development of the LOO, the project team conducted several crew evaluations to collect and summarize valuable crew feedback on system design, function, and overall usability to influence the next design iteration. Because every person could use the system differently in space, it was extremely important to collect and analyze the data in a very methodical manner to appropriately influence the design based on the evaluation results. Establishing a standard process ensures consistent data collection from one evaluation to another, helps to maintain privacy for each test subject’s inputs and removes any potential bias from test subject to test subject. To date, the team has completed four rounds of crew evaluations with multiple crewmembers on prototypes for the different LOO subsystems. This paper will summarize the methodology used to conduct the evaluations as well as how data was collected and analyzed. The paper will also provide details on each of the evaluations and how the design was updated based on the results.

toilet↗
NASA NTRSDate not supplied

Evolution of the Next Exploration Toilet Through Human-in-the-Loop (HITL) Testing

Human waste collection in space is a unique and necessary function that all crewmembers must perform. The variability in how each crewmember uses the toilet to urinate and defecate introduces complexities and challenges with regards to overall hardware design. Because of this variability, it is important to consider crew inputs in all aspects of a toilet design especially with regards to crew interfaces that could impact overall waste collection. Access to crew feedback is essential to the design process and should be considered early and often through the various design phases. In 2020, NASA started a project for the Human Landing System (HLS) program to develop a Government Furnished Equipment (GFE) toilet option. The project is known as the Lavatory On-Orbit (LOO). During the early development of the LOO, the project team conducted several crew evaluations to collect and summarize valuable crew feedback on system design, function, and overall usability to influence the next design iteration. Because every person could use the system differently in space, it was extremely important to collect and analyze the data in a very methodical manner to appropriately influence the design based on the evaluation results. Establishing a standard process ensures consistent data collection from one evaluation to another, helps to maintain privacy for each test subject’s inputs and removes any potential bias from test subject to test subject. To date, the team has completed four rounds of crew evaluations with multiple crewmembers on prototypes for the different LOO subsystems. This paper will summarize the methodology used to conduct the evaluations as well as how data was collected and analyzed. The paper will also provide details on each of the evaluations and how the design was updated based on the results.

toilet↗
NASA NTRS2023

Pypromice: A Python Package for Processing Automated Weather Station Data

The pypromice Python package is for processing and handling observation datasets from automated weather stations (AWS). It is primarily aimed at users of AWS data from the Geological Survey of Denmark and Greenland (GEUS), which collects and distributes in situ weather station observations to the cryospheric science research community. Functionality in pypromice is primarily handled using two key open-source Python packages, xarray (Hoyer & Hamman, 2017) and pandas (The pandas development team, 2020). A defined processing workflow is included in pypromice for transforming original AWS observations (Level 0, L0) to a usable, CF-convention-compliant dataset (Level 3, L3) (Figure 1). Intermediary processing levels (L1,L2) refer to key stages in the workflow, namely the conversion of variables to physical measurements and variable filtering (L1), cross-variable corrections and user-defined data flagging and fixing (L2), and derived variables (L3). Information regarding the station configuration is needed to perform the processing, such as instrument calibration coefficients and station type (one-boom tripod or two-boom mast station design, for example), which are held in a toml configuration file. Two example configuration files are provided with pypromice , which are also used in the package’s unit tests. More detailed documentation of the AWS design, instrumentation, and processing steps are described in Fausto et al. (2021).

pypromice↗
NASA NTRS2004

The Lewice Console

Lewice (LEWis ICE accretion program) is software used by literally hundreds of users in the aeronautics community for predicting ice shapes, collections efficiencies, and anti-icing heat requirements for aircraft. LEWICE performs its analysis in minutes on a desktop PC, allowing the user to run several parameter studies for design purposes. The ice shape predictions have been used to assess performance degradation both as an input to a CFD program or experimentally in flight or in a wind tunnel. This information is important to ensure an airplane s safe passage through an icing cloud. Currently, Lewice runs as a DOS program that accepts many different inputs such as cloud conditions, wing shapes, and thermal deicing inputs. Usually, such experimental data is stored in spreadsheets. However, Lewice inputs are text files; therefore, they must be generated by the user. Lewice s outputs (collection efficiency, ice shapes and thicknesses) are also text files; to plot the data, users must generate a spreadsheet with this output. Because all Lewice J/O is in the form of text files, using Lewice can be tricky and time-consuming. Our goal was to improve Lewice s usability by creating a user interface that would automatically generate Lewice input from a spreadsheet and automatically put Lewice output into spreadsheets with charts. Additionally, this user interface would automatically convert units (as Lewice only accepts input in certain units) and offer several output options. I call this program the Lewice Console. The Lewice Console is an easy to use interface for Lewice written in Visual Basic. It allows users to run Lewice given a spreadsheet listing experimental conditions. It automatically generates the input to Lewice, does necessary unit conversions, runs Lewice, and produces a spreadsheet with charts plotting the data. It allows users to import data from previously generated Lewice inputs into a spreadsheet. It also allows users to batch run Lewice on several different inputs to automatically generate multiple output spreadsheets. You can also generate plots of actual data vs. experimental data. These capabilities are just the beginning for the Lewice Console. Lewice is capable of running a full deicing experiment given a geometry and heating apparatus information. However, users find it difficult to run such experiments due to the number of inputs and the difficult input file format. The Lewice Console would simplify experiment generation by allowing the user to interactively draw a geometry, place heating apparatus, and specify information about each part. The input to Lewice would be automatically generated from the experiment the user draws on the screen. The Lewice Console would simplify the experiment building process. Currently, Lewice runs as a DOS program that accepts many different inputs such as

Armstrong, Aaron E.↗
NASA NTRS1981

Application of the NASA airborne oceanographic lidar to the mapping of chlorophyll and other organic pigments

Laser fluorosensing techniques used for the airborne measurement of chlorophyll a and other naturally occurring waterborne pigments are reviewed. Previous experiments demonstrating the utility of the airborne oceanographic lidar (AOL) for assessment of various marine parameters are briefly discussed. The configuration of the AOL during the NOAA/NASA Superflux experiments is described. The participation of the AOL in these experiments is presented and the preliminary results are discussed. The importance of multispectral receiving capability in a laser fluorosensing system for providing reproducible measurements over wide areas having spatial variations in water column transmittance properties is addressed. This capability minimizes the number of truthing points required and is usable even in shallow estuarine areas where resuspension of bottom sediment is common. Finally, problems encountered on the Superflux missions and the resulting limitations on the AOL data sets are addressed and feasible solutions to these problems are provided.

Hoge, F. E.↗
NASA NTRS2019

NASA Earthdata Knowledge Base

Prototype work for connecting together the main elements of Earth Observation knowledge and context in a way that is: machine-readable, human-usable and curatable. Using the latest in graph technologies and cloud managed services.

earth data↗
NASA NTRS1951

Systematic Two-Dimensional Cascade Tests of NACA 65-Series Compressor Blades at Low Speeds

The performance of NACA 65-series compressor blade section in cascade has been investigated systematically in a low-speed cascade tunnel. Porous test-section side walls and for high-pressure-rise conditions, porous flexible end walls were employed to establish conditions closely simulating two-dimensional flow. Blade sections of design lift coefficients from 0 to 2.7 were tested over the usable angle-of-attack range for various combinations of inlet-flow angle. A sufficient number of combinations were tested to permit interpolation and extrapolation of the data to all conditions within the usual range of application. The results of this investigation indicate a continuous variation of blade-section performance as the major cascade parameters, blade camber, inlet angle, and solidity were varied over the test range. Summary curves of the results have been prepared to enable compressor designers to select the proper blade camber and angle of attack when the compressor velocity diagram and desired solidity have been determined.

Herrig, L. Joseph↗
NASA NTRS1956

Low-speed cascade investigation of loaded leading-edge compressor blades

Six percent thick NACA 63-series compressor-blade sections having a loaded leading-edge A4K6 mean line have been investigated systematically in a two-dimensional porous-wall cascade over a range of Reynolds numbers from 160,000 to 385,000. Blades cambered to have isolated-airfoil lift coefficients of 0.6, 1.2, 1.8, and 2.4 were tested over the usable angle-of-attack range at inlet-air angles of 30 degrees, 45 degrees, and 60 degrees and solidities of 1.0 and 1.5. A comparison with data of NACA RM L51G31, shows that the angle-of-attack operating range is 2 degrees to 4 degrees less than the range for the uniformly loaded section; however, the wake losses near design angle of attack are slightly lower than those for the uniformly loaded section. Except for highly cambered blades at high inlet angles, the 63-(C s oA4K6)06 compressor-blade sections are capable of more efficient operation for moderate-speed subsonic compressors at design angle of attack than are the 65-(C s oa10)10 or the 65-(c s oA2I8b)10 compressor-blade sections. In contrast to the other sections, the loaded leading-edge sections are capable of operating efficiently at the lower Reynolds numbers.

Emery, James C↗
NASA NTRS1960

Orbital Capabilities of a Jupiter - Modified Agena "B" Space Vehicle

This presentation is directed towards providing additional information concerning the orbital capabilities for a two stage JUPITER-Agena "B" space vehicle. The data presented in this discussion is an extension of the preliminary information presented to NASA on 16 November, 1960. The pertinent features contained in this presentation are the usable payload and expected orbital accuracies associated with the vehicles under consideration when utilizing either an LEV-3 or ST-120 inertial guidance system. Missions of primary concern are 300, 400 or 500 nautical mile orbits around the earth. Preliminary budgetary and planning cost estimates related to the vehicle configurations discussed are presented under separate cover.

Chrysler Corporation↗
NASA NTRSDate not supplied

Crew Autonomy through Self-Scheduling: Guidelines for Crew Scheduling Performance Envelope and Mitigation Strategies

As NASA considers long-duration exploration missions, it is envisioned that crews will behave more autonomously as compared to low-Earth orbit missions. When considering long duration exploration missions, Flight Operations Directorate (FOD) identified the following benefits and challenges presented on this slide. As missions operate further from Earth, the communication latency between the spacecraft and Mission Control Center will increase requiring the crew to take a more active role in reacting to daily planning. However, one of the key challenges for crew self-scheduling is that we do not want to overwhelm astronauts who are not expert mission planners. This leads to our primary research objective: to first, characterize the human performance envelope for the task of planning and scheduling in the context of human spaceflight operations, then, develop countermeasure aids to mitigate adverse performance effects due to plan complexity, and finally, inform performance standards and guidelines based on research results. Our next steps are to finish summarizing our findings from the experiment in conference papers and our upcoming yearly report. In the upcoming year, we will continue to collect data in analog missions and begin summarizing our recommended standards and guidelines.

user experience↗
NASA NTRS1991

User modeling techniques for enhanced usability of OPSMODEL operations simulation software

The PC based OPSMODEL operations software for modeling and simulation of space station crew activities supports engineering and cost analyses and operations planning. Using top-down modeling, the level of detail required in the data base can be limited to being commensurate with the results required of any particular analysis. To perform a simulation, a resource environment consisting of locations, crew definition, equipment, and consumables is first defined. Activities to be simulated are then defined as operations and scheduled as desired. These operations are defined within a 1000 level priority structure. The simulation on OPSMODEL, then, consists of the following: user defined, user scheduled operations executing within an environment of user defined resource and priority constraints. Techniques for prioritizing operations to realistically model a representative daily scenario of on-orbit space station crew activities are discussed. The large number of priority levels allows priorities to be assigned commensurate with the detail necessary for a given simulation. Several techniques for realistic modeling of day-to-day work carryover are also addressed.

Davis, William T.↗
NASA NTRS2012

Software to Control and Monitor Gas Streams

This software package interfaces with various gas stream devices such as pressure transducers, flow meters, flow controllers, valves, and analyzers such as a mass spectrometer. The software provides excellent user interfacing with various windows that provide time-domain graphs, valve state buttons, priority- colored messages, and warning icons. The user can configure the software to save as much or as little data as needed to a comma-delimited file. The software also includes an intuitive scripting language for automated processing. The configuration allows for the assignment of measured values or calibration so that raw signals can be viewed as usable pressures, flows, or concentrations in real time. The software is based on those used in two safety systems for shuttle processing and one volcanic gas analysis system. Mass analyzers typically have very unique applications and vary from job to job. As such, software available on the market is usually inadequate or targeted on a specific application (such as EPA methods). The goal was to develop powerful software that could be used with prototype systems. The key problem was to generalize the software to be easily and quickly reconfigurable. At Kennedy Space Center (KSC), the prior art consists of two primary methods. The first method was to utilize Lab- VIEW and a commercial data acquisition system. This method required rewriting code for each different application and only provided raw data. To obtain data in engineering units, manual calculations were required. The second method was to utilize one of the embedded computer systems developed for another system. This second method had the benefit of providing data in engineering units, but was limited in the number of control parameters.

Arkin, C.↗
NASA NTRS1988

Status of fusion research and implications for D/He-3 systems

World wide programs in both magnetic confinement and inertial confinement fusion research have made steady progress towards the experimental demonstration of energy breakeven. However, after breakeven is achieved, considerable time and effort must still be expended to develop a usable power plant. The main program described is focused on Deuterium-Tritium devices. In magnetic confinement, three of the most promising high beta approaches with a reasonable experimental data base are the Field Reversed Configuration, the high field tokamak, and the dense Z-pinch. The situation is less clear in inertial confinement where the first step requires an experimental demonstration of D/T spark ignition. It appears that fusion research has reached a point in time where an R and D plan to develop a D/He-3 fusion reactor can be laid out with some confidence of success.

Miley, George H.↗
NASA NTRS1999

A Cutoff in the X-Ray Fluctuation Power Density Spectrum of the Seyfert 1 Galaxy NGC 3516

During 1997 March-July, RXTE observed the bright, strongly variable Seyfert 1 galaxy NGC 3516 once every approx. 12.8 hr for 4.5 months and nearly continuously (with interruptions due to SAA passage but not Earth occultation) for a 4.2 day period in the middle. These were followed by ongoing monitoring once every approx. 4.3 days. These data are used to construct the first well-determined X-ray fluctuation power density spectrum (PDS) of an active galaxy to span more than 4 decades of usable temporal frequency. The PDS shows no signs of any strict or quasi-periodicity, but does show a progressive flattening of the power-low slope from -1.74 at short time scales to -0.73 at longer time scales. This is the clearest observation to date of the long-predicted cutoff in the PDS. The characteristic variability time scale corresponding to this cutoff temporal frequency is approx. 1 month. Although it is unclear how this time scale may be interpreted in terms of a physical size or process, there are several promising candidate models. The PDS appears similar to those seen for Galactic black hole candidates such as Cyg X-1, suggesting that these two classes of objects with very different luminosities and putative black hole masses (differing by more than a factor of 10(exp 5)) may have similar X-ray generation processes and structures.

Edelson, Rick↗
NASA NTRS1997

Increased User Satisfaction Through an Improved Message System

With all of the enhancements in software methodology and testing, there is no guarantee that software can be delivered such that no user errors occur, How to handle these errors when they occur has become a major research topic within human-computer interaction (HCI). Users of the Multimission Spacecraft Analysis Subsystem(MSAS) at the Jet Propulsion Laboratory (JPL), a system of X and motif graphical user interfaces for analyzing spacecraft data, complained about the lack of information about the error cause and have suggested that recovery actions be included in the system error messages...The system was evaluated through usability surveys and was shown to be successful.

Human-computer interaction error handling direct m↗