Search NASA⌕ Search

SEARCH · Search NASA

Results for “Log data”

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

A Discrete Component Low-Noise Preamplifier Readout for a Linear (1x16) SiC Photodiode Array

A compact, low-noise and inexpensive preamplifier circuit has been designed and fabricated to optimally readout a common cathode (1x16) channel 4H-SiC Schottky photodiode array for use in ultraviolet experiments. The readout uses an operational amplifier with 10 pF capacitor in the feedback loop in parallel with a low leakage switch for each of the channels. This circuit configuration allows for reiterative sample, integrate and reset. A sampling technique is given to remove Johnson noise, enabling a femtoampere level readout noise performance. Commercial-off-the-shelf acquisition electronics are used to digitize the preamplifier analogue signals. The data logging acquisition electronics has a different integration circuit, which allows the bandwidth and gain to be independently adjusted. Using this readout, photoresponse measurements across the array between spectral wavelengths 200 nm and 370 nm are made to establish the array pixels external quantum efficiency, current responsivity and noise equivalent power.

low-noise preamplifier↗
NASA NTRS2018

Native Fluorescence Detection Methods, Devices, and Systems for Organic Compounds

Naphthalene, benzene, toluene, xylene, and other volatile organic compounds VOCs have been identified as serious health hazards. Embodiments of the invention are directed to methods and apparatus for near-real-time in-situ detection and accumulated dose measurement of exposure to naphthalene vapor and other hazardous gaseous VOCs. The methods and apparatus employ excitation of fluorophors native or endogenous to compounds of interest using light sources emitting in the ultraviolet below 300 nm and measurement of native fluorescence emissions in distinct wavebands above the excitation wavelength. The apparatus of some embodiments are cell-phone-sized sensor/dosimeter "badges" to be worn by personnel potentially exposed to hazardous VOCs. The badge sensor of some embodiments provides both real time detection and data logging of exposure to naphthalene or other VOCs of interest from which both instantaneous and accumulated dose can be determined.

Hug, William F.↗
NASA NTRSDate not supplied

Seeker 1.0 GNC Flight Performance (presentation)

Seeker is an automated extravehicular inspection spacecraft that was designed and built in-house at the NASA Johnson Space Center (JSC) over approximate-ly 18 months with a budget of $1.8 million. This first version of Seeker is in-tended to be an incremental development towards an advanced inspection ca-pability. Seeker launched onboard the NG-11 Cygnus mission in 2019 and de-ployed from Cygnus on September 16, 2019. Downlinked telemetry, imagery from the chaser and target spacecraft, and onboard engineering data logs are used to provide an analysis of the system’s performance. This paper reviews the performance of the Seeker vehicle with a focus on the guidance, navigation, and control (GNC) system. The results are presented with a discussion of the re-lated system design to highlight how decisions and applied methods culminated in the observed performance.

Sam Pedrotty↗
NASA NTRS2023

An Accelerated Life Testing Dataset for Lithium-Ion Batteries With Constant and Variable Loading Conditions

The dataset repository is organized into three main folders, each containing one group of life cycled battery packs. Within each folder individual battery packs own their dedicated csv file for continuous data logging, which are named with their respective battery pack number. The folders are named: - regular_alt_batteries: Containing one csv file for each battery pack cycled at the same load level or load range throughout lifetime - recommissioned_batteries: Containing one csv file for each battery pack cycled at different load levels at varying life stages - second_life_batteries: Containing one csv file for each second life battery pack cycled at constant current througout the second life

Li-ion Battery↗
NASA NTRS1985

Experimental study of main rotor tip geometry and tail rotor interactions in hover. Volume 2: Run log and tabulated data

A model scale hover test was conducted in the Sikorsky Aircraft Model Rotor hover Facility to identify and quantify the impact of the tail rotor on the demonstrated advantages of advanced geometry tip configurations. The existence of mutual interference between hovering main rotor and a tail rotor was acknowledged in the test. The test was conducted using the Basic Model Test Rig and two scaled main rotor systems, one representing a 1/5.727 scale UH-60A BLACK HAWK and the others a 1/4.71 scale S-76. Eight alternate rotor tip configurations were tested, 3 on the BLACK HAWK rotor and 6 on the S-76 rotor. Four of these tips were then selected for testing in close proximity to an operating tail rotor (operating in both tractor and pusher modes) to determine if the performance advantages that could be obtained from the use of advanced geometry tips in a main rotor only environment would still exist in the more complex flow field involving a tail rotor. This volume contains the test run log and tabulated data.

Balch, D. T.↗
NASA NTRS1991

Solar-A reformatted data files and observing log

An overview is presented of the Solar-A telemetry data files which are to be created and the format and organization which the files are to use. The organization chosen is to be efficient in space, to facilitate access to the data, and to allow the data to be transportable to different machines. An observing log file is to be created automatically, using the reformatted data files as the input. It will be possible to perform searches with the observing log to list cases where instruments are in certain modes and/or seeing certain signal levels. A user will be able to search the observing log and obtain a list of all cases where a given set of conditions are satisfied. An event log will be created listing the times when the instrument or spacecraft modes change.

Morrison, M. D.↗
NASA NTRS1982

Correlation of Preston-tube data with laminar skin friction (Log No. J12984)

Preston tube data within laminar boundary layers obtained on a sharp ten-degree cone in the NASA Ames eleven-foot transonic wind tunnel are correlated with the corresponding values of theoretical skin friction. Data were obtained over a Mach number range of 0.30 to 0.95 and unit Reynolds numbers of 9.84, 13.1, and 16.4 million per meter. The rms scatter of skin friction coefficient about the correlation is of the order of one percent, which is comparable to the reported accuracy for calibrations of Preston tubes in incompressible pipe flows. In contrast to previous works on Preston tube/skin friction correlations, which are based on the physical height of the probe's face, this satisfactory correlation for compressible boundary layer flows is achieved by accounting for the effects of a variable "effective" height of the probe. The coefficients, which appear in the correlation, are dependent on the particular tunnel environment. The general procedure can be used to define correlations for other wind tunnels.

Reed, T. D.↗
NASA NTRS1982

One Way of Testing a Distributed Processor

Launch processing for Space Shuttle is checked out, controlled, and monitored with new system. Entire system can be exercised by two computer programs--one in master console and other in each of operations consoles. Control program in each operations console detects change in status and begins task initiation. All of front-end processors are exercised from consoles through common data buffer, and all data are logged to processed-data recorder for posttest analysis.

Edstrom, R.↗
NASA NTRSDate not supplied

Assessment of Crew Time for Maintenance and Repairs Activities for Lunar Surface Missions

NASA is currently evaluating different methods to predict how much time crewmembers will spend conducting repair and maintenance activities on future space missions. As mission scope and spacecraft architectures change, it will be necessary to understand how crew repair and maintenance timelines are impacted by mission operations and technology changes. Past work has been done using historical ISS data to accurately predict crew habitation and operation timelines, resulting in the development of NASA’s Exploration Crew Time Model (ECTM). However, understanding crew maintenance and repair requirements has posed a unique challenge due to the complexity of available datasets, the probabilistic nature of sub-system failures, and the impacts of reliability growth on failure rates. This paper presents a methodology to collect and condition empirical repair and maintenance time data from available data sets, to extrapolate from that data to estimate projected maintenance and repair times for a lunar Surface Habitat, and to assess how uncertainty in repair time could impact utilization time on the lunar surface. NASA International Space Station (ISS) maintenance and crew time data are logged into two central databases, the Maintenance Data Collection (MDC) and the Operations Planning Timeline Integration System (OPTimIS) respectively. Separately, each of these two datasets capture only portions of the complete set of data required to generate an accurate assessment of crew time spent on maintenance activities at a sub-system level. MDC provides a detailed catalog of failure events and an overview of the failure’s required maintenance and OPTimIS provides a description of crew activities and crew time durations dedicated to maintenance. To create a more useful crew time estimate for maintenance timelines, the authors developed a methodology to capture relevant data from each set and combine and utilize that data by linking crew time requirements to specific components. The authors compare the failure logs in the MDC to crew activity logs pulled from OPTimIS and then process the data to estimate required repair times for each failure event. Data is also classified by the outcome of each repair event, whether the failed component was replaced or whether it was repaired in place. The entire maintenance activity dataset is then categorized based on the class of failed component to allow for a statistically significant sample size for each class and to provide accurate crew time estimates for any components lacking relevant data. This resultant component repair time data can be used in the future to generate Mean Time To Repair (MTTR) estimates and confidence intervals for each class of component based on a probabilistic distribution of documented maintenance events. These improved MTTR values can then be applied to candidate element sub-system architectures, along with component Mean Time Between Failure (MTBF) data to generate distributions for potential required system crew repair time estimates for a given mission. Repair time distributions can then be used to develop more accurate crew schedules and to assess potential available utilization time.

Crew Time↗
NASA NTRSDate not supplied

Assessment of Crew Time for Maintenance and Repair Activities for Lunar Surface Missions

NASA is currently evaluating different methods to predict how much time crewmembers will spend conducting repair and maintenance activities on future space missions. As mission scope and spacecraft architectures change, understanding how crew repair and maintenance timelines are impacted by mission operations and technology changes is vital for future mission planning. Past work has been done using historical International Space Station (ISS) data to accurately predict crew habitation and operation timelines, resulting in the development of NASA’s Exploration Crew Time Model (ECTM). However, understanding crew maintenance and repair requirements has posed a unique challenge due to the complexity of available datasets, the probabilistic nature of sub-system failures, and the impacts of reliability growth on failure rates. This paper presents a methodology to collect and condition empirical repair and maintenance time data from available datasets, to extrapolate from that data to estimate projected maintenance and repair times for a lunar Surface Habitat (SH), and to assess how uncertainty in repair time could impact utilization time on the lunar surface. NASA ISS maintenance and crew time data are logged into two central databases: the Maintenance Data Collection (MDC) and the Operations Planning Timeline Integration System (OPTimIS). Separately, each of these two datasets capture only portions of the complete set of data required to generate an accurate assessment of crew time spent on maintenance activities at a sub-system level. To create a more useful crew time estimate for maintenance timelines, the authors developed a methodology to capture relevant data from each set and combine and utilize that data by linking crew time requirements to specific components. The authors compare the failure logs in the MDC to crew activity logs pulled from OPTimIS and then process the data to estimate required repair time for each failure and repair event. The entire maintenance activity dataset is then categorized based on the class of failed component to ensure a significant sample size for each class and accurate crew time estimates for any components lacking relevant data. This resultant component repair time data can be used in the future to generate Mean Time to Repair (MTTR) estimates and confidence intervals for each class of component based on a probabilistic distribution of documented maintenance events. These improved MTTR values can then be applied to candidate element sub-system architectures, along with component Mean Time Between Failure (MTBF) data to generate distributions for potential required system crew repair time estimates for a given mission. The authors applied these modeling methods to a case study of a crewed mission to the planned SH and produced expected corrective maintenance crew time distributions. The results produced an expected corrective maintenance crew time at over 24 hours per mission, and a maintenance crew time distribution that reflects the importance of planning for sufficient maintenance requirements each mission. Repair time distributions can then be used to develop more accurate crew schedules and to assess potential available utilization time.

Crew Time↗
NASA NTRS2011

Data Mining of Network Logs

The statement of purpose is to analyze network monitoring logs to support the computer incident response team. Specifically, gain a clear understanding of the Uniform Resource Locator (URL) and its structure, and provide a way to breakdown a URL based on protocol, host name domain name, path, and other attributes. Finally, provide a method to perform data reduction by identifying the different types of advertisements shown on a webpage for incident data analysis. The procedures used for analysis and data reduction will be a computer program which would analyze the URL and identify and advertisement links from the actual content links.

Collazo, Carlimar↗
NASA NTRS2003

The Mobile Agents Integrated Field Test: Mars Desert Research Station April 2003

The Mobile Agents model-based, distributed architecture, which integrates diverse components in a system for lunar and planetary surface operations, was extensively tested in a two-week field "technology retreat" at the Mars Society s Desert Research Station (MDRS) during April 2003. More than twenty scientists and engineers from three NASA centers and two universities refined and tested the system through a series of incremental scenarios. Agent software, implemented in runtime Brahms, processed GPS, health data, and voice commands-monitoring, controlling and logging science data throughout simulated EVAs with two geologists. Predefined EVA plans, modified on the fly by voice command, enabled the Mobile Agents system to provide navigation and timing advice. Communications were maintained over five wireless nodes distributed over hills and into canyons for 5 km; data, including photographs and status was transmitted automatically to the desktop at mission control in Houston. This paper describes the system configurations, communication protocols, scenarios, and test results.

Clancey, William J.↗
NASA NTRS2019

Collecting and Processing Earth Science Data Metrics at NASA ESDIS

Since the launch of Terra satellite in 1999, the number of Earth Science remote sensing data products created and distributed by NASA's Earth Observing System (EOS) Data and Information System (EOSDIS) has increased from a few hundred to nearly ten thousand. NASA's Earth Science Data and Information System (ESDIS) Metrics System (EMS) collects metrics on data ingest, archive, and distribution by its Distributed Active Archive Centers (DAACs) and the Science Investigator-led Systems (SIPS), known as Data Providers. These metrics are critical in helping NASA management as well as data producers in resource planning and gaining a wide range of knowledge of data users and data usage.EMS receives flat files, or log files of data archive, ingest, and distribution either in their raw format, such as Apache web logs, or text files of log records formatted by the Data Providers. Tens of millions of records are processed each day to extract metrics on data products, user information, distribution protocols and services, and so on. The metrics are then made available to designated parties.This presentation provides an overview of the EMS processing workflow and improvement efforts made in recent years to handle ever-increasing number of data records and new metrics requirements, discusses several key steps including mapping log records to data products and identifying user communities along with geo-distribution, and demonstrates typical metrics capabilities produced by the EMS system. Challenges and potential approaches to improve the system are also discussed.

Pan, Jianfu↗
NASA NTRS2004

Hand-Eye Calibration of Robonaut

NASA's Human Space Flight program depends heavily on Extra-Vehicular Activities (EVA's) performed by human astronauts. EVA is a high risk environment that requires extensive training and ground support. In collaboration with the Defense Advanced Research Projects Agency (DARPA), NASA is conducting a ground development project to produce a robotic astronaut's assistant, called Robonaut, that could help reduce human EVA time and workload. The project described in this paper designed and implemented a hand-eye calibration scheme for Robonaut, Unit A. The intent of this calibration scheme is to improve hand-eye coordination of the robot. The basic approach is to use kinematic and stereo vision measurements, namely the joint angles self-reported by the right arm and 3-D positions of a calibration fixture as measured by vision, to estimate the transformation from Robonaut's base coordinate system to its hand coordinate system and to its vision coordinate system. Two methods of gathering data sets have been developed, along with software to support each. In the first, the system observes the robotic arm and neck angles as the robot is operated under external control, and measures the 3-D position of a calibration fixture using Robonaut's stereo cameras, and logs these data. In the second, the system drives the arm and neck through a set of pre-recorded configurations, and data are again logged. Two variants of the calibration scheme have been developed. The full calibration scheme is a batch procedure that estimates all relevant kinematic parameters of the arm and neck of the robot The daily calibration scheme estimates only joint offsets for each rotational joint on the arm and neck, which are assumed to change from day to day. The schemes have been designed to be automatic and easy to use so that the robot can be fully recalibrated when needed such as after repair, upgrade, etc, and can be partially recalibrated after each power cycle. The scheme has been implemented on Robonaut Unit A and has been shown to reduce mismatch between kinematically derived positions and visually derived positions from a mean of 13.75cm using the previous calibration to means of 1.85cm using a full calibration and 2.02cm using a suboptimal but faster daily calibration. This improved calibration has already enabled the robot to more accurately reach for and grasp objects that it sees within its workspace. The system has been used to support an autonomous wrench-grasping experiment and significantly improved the workspace positioning of the hand based on visually derived wrench position. estimates.

Nickels, Kevin↗
NASA NTRS2020

What Can We Learn from One Billion Ground System Log Messages?

Shortage of log-based data in a ground system they have traditionally been the under achievers in a satellite ground system. This is due to several factors: Once log messages scroll out of view on the TTC event console window they are soon forgotten. Application and system log files are scattered across directories within a system, across a multitude of servers, and across one or more databases making access cumbersome. Typical tools to perform log file content searching are generally crude and typically only employed as part of trouble-shooting exercises.As we move towards satellite constellations and fleets and add even more status information, the number of messages keeps growing. One mission now estimates that they could generate 3,000,000 messages per day 1 billion per year - for the life of their mission. What to do with those 1 billion messages? That is the challenge. With the recent technological advances in the management of large data sets, text-based processing, and data analytics, there are now capabilities that we can provide to the ground system engineers and satellite operators to address what we postulate are missed opportunities. Advanced real-time log analysis can allow us to be less reactionary in favor of being more proactive. Analytics goals include the ability to: Identify root cause of unexpected events, failures or error conditions enabled by correlating disparate data. Detect security breaches attempts before they are successful. Help admins ensure IT resources continue running optimally. Identify trends and patterns that may indicate impending failures or error conditions for valuable assets before they happen. Compare satellites in a fleet or constellation in terms of number of alarms, number of command sent to them, etc.. Answer questions like "Are the operations support needs increasing over the past year?" or "Have we seen this combination of alarm conditions before?" But really, once the tools are readily available the users will start realizing what can be done with their new powers. In this presentation we will show the results of analyzing millions of actual mission operations log messages, how the results can be displayed to the user, and how new products now available as open source can be applied to the challenges of large scale time-tagged text-based mission operations messages. Flight operations team members believe that this is a powerful new option for how they assess overall system and space asset health. Technical descriptions of the design, tools, and storage will be provided. One billion messages? Bring'em on!

Orsborne, Sharon↗
NASA NTRS1991

NASA/Ames Research Center DC-8 data system

In-flight facility data acquisition, distribution, and recording on the NASA Ames Research Center (ARC) DC-8 are performed by the Data Acquisition and Distribution System (DADS). Navigational and environmental data collected by the DADS are converted to engineering units and distributed real-time to investigator stations once per second. Selected engineering units data are printed and displayed on closed circuit television monitors throughout flights. An in-flight graphical display of the DC-8 flight track (with barbs indicating wind direction and magnitude) has recently been added to the DADS capabilities. Logging of data run starts/stops and commentary from the mission director are also provided. All data are recorded to hard disk in-flight and archived to tape medium post-flight. Post-flight, hard copies of the track map and mission director's log are created by the DADS. The DADS is a distributed system consisting of a data subsystem, an Avionic Serial Data-to-VMEbus (ASD2VME) subsystem, and a host subsystem. Each subsystem has a dedicated central processing unit (CPU) and is capable of stand-alone operation. All three subsystems are housed in a single 20-slot VME chassis and communicate with each other over the VMEbus. The data and host subsystems are briefly discussed, and the DC-8 DADS internal configuration and system block diagram are presented.

Cherniss, S. C.↗
NASA NTRS1975

Application of a dedicated micro-processor for automatic data acquisition of load strain and acoustic-emission data

This paper describes an automatic system for acquisition, logging and analysis of stress, strain and acoustic emission data. The complete system is a combination of several standard items of equipment and a newly developed intelligent data logger which has the capability to send data directly to a large scale computer for reduction and plotting. The data logging and all interfacing with peripheral equipment are accomplished using digital electronics. The heart of the system is a four-bit microprocessor and digital cassette tape unit. The system, which is controlled by instructions from a cathode ray tube terminal, has the capability to transmit data from the cassette unit to a large computer via a time sharing option. Typical results are presented for acoustic emission count rate and total count curves superimposed on stress-strain diagrams for boron/epoxy advanced composites.

Wilson, G. H.↗
NASA NTRS1972

On the mass-luminosity relation.

The results of a least-squares study of the mass-luminosity relation for eclipsing and visual binary stars consisting of main sequence components are presented. Two methods are discussed. First, the values of the coefficients A and B in the relation log M = A + BM sub BOL are determined. Then a technique which permits the determination of alpha and beta in the relation M = alpha L beta, when only the sum of the masses, and not the individual masses of each component, is known. The results and a comparison of the two methods are discussed. It is found that the following mass-luminosity relation represents the observational data satisfactorily: log M = 0.504 - 0.103 M sub BOL, -8 less than or equal to M sub BOL less than or equal to +10.5. A discussion of the data and of the possibility that separate mass-luminosity relations may exist for visual and eclipsing binaries is given. The possibility that more than one mass-luminosity relation is required in the range -8 less than or equal to M sub BOL less than or equal to +13 is also discussed.

Mccluskey, G. E., Jr.↗