Search NASA⌕ Search

SEARCH · Search NASA

Results for “artifacts”

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 343 records · Page 19
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

Airborne Measurements of Carbonaceous Aerosols in Southern Africa during the Dry Biomass Burning Season

Particulate matter collected aboard the University of Washington's (UW) Convair-580 research aircrafi over southem Afiica during the dry biomass burning season was analyzed for total carbon (TC), organic carbon (OC), and black carbon (BC) contents using thermal and optical methods. Samples were collected in smoke plumes of burning savanna and in regional haze. A known artifact, produced by the adsorption of organic gases on the quartz filter substrates used to collect the particulate matter samples, comprised a significant portion of the TC collected. Consequently, conclusions derived from the data are greatly dependent on whether or not OC concentrations are corrected for this artifact. For example, the estimated aerosol coalbedo (1 - single scattering albedo (SSA)), which is a measure of aerosol absorption, of the biomass smoke samples is 60% larger using corrected OC concentrations. Thus, the corrected data imply that the biomass smoke is 60% more absorbing than do the uncorrected data. The BC to (corrected) OC mass ratio (BC/OC) of smoke plume samples (0.18 plus or minus 0.06) is lower than that of samples collected in the regional haze (0.25 plus or minus 0.08). The difference may be due to mixing of biomass smoke with background air characterized by a higher BC/OC ratio. A simple source apportionment indicates that biomass smoke contributes about three quarters of the aerosol burden in the regional haze, while other souxes (e.g., fossil fuel burning) contribute the remainder.

Kirchstetter, Thomas W.↗
NASA NTRS2005

Why is Light Text Harder to Read Than Dark Text?

Scharff and Ahumada (2002, 2003) measured text legibility for light text and dark text. For paragraph readability and letter identification, responses to light text were slower and less accurate for a given contrast. Was this polarity effect (1) an artifact of our apparatus, (2) a physiological difference in the separate pathways for positive and negative contrast or (3) the result of increased experience with dark text on light backgrounds? To rule out the apparatus-artifact hypothesis, all data were collected on one monitor. Its luminance was measured at all levels used, and the spatial effects of the monitor were reduced by pixel doubling and quadrupling (increasing the viewing distance to maintain constant angular size). Luminances of vertical and horizontal square-wave gratings were compared to assess display speed effects. They existed, even for 4-pixel-wide bars. Tests for polarity asymmetries in display speed were negative. Increased experience might develop full letter templates for dark text, while recognition of light letters is based on component features. Earlier, an observer ran all conditions at one polarity and then switched. If dark and light letters were intermixed, the observer might use component features on all trials and do worse on the dark letters, reducing the polarity effect. We varied polarity blocking (completely blocked, alternating smaller blocks, and intermixed blocks). Letter identification responses times showed polarity effects at all contrasts and display resolution levels. Observers were also more accurate with higher contrasts and more pixels per degree. Intermixed blocks increased the polarity effect by reducing performance on the light letters, but only if the randomized block occurred prior to the nonrandomized block. Perhaps observers tried to use poorly developed templates, or they did not work as hard on the more difficult items. The experience hypothesis and the physiological gain hypothesis remain viable explanations.

Scharff, Lauren V.↗
NASA NTRS2006

Critical Issues in the History of Spaceflight

At a May 1981 "Proseminar in Space History"held at the Smithsonian Institution's National Air and Space Museum (NASM) in Washington, DC, historians came together to consider the state of the discipline of space history. It was an historic occasion. The community of scholars interested in the history of spaceflight was not large; previously, well-meaning but untrained aficionados consumed with artifacts had dominated the field, to the exclusion of the larger context. At a fundamental level, this proseminar represented a "declaration of independence" for what might be called the "new aerospace history." In retrospect, it may be interpreted as marking the rise of space history as a recognizable subdiscipline within the field of U.S. history. Bringing together a diverse collection of scholars to review the state of the art in space history, this proseminar helped in a fundamental manner to define the field and to chart a course for future research. Its participants set about the task of charting a course for collecting, preserving, and disseminating the history of space exploration within a larger context of space policy and technology. In large measure, the course charted by the participants in this 1981 proseminar aided in advancing a very successful agenda of historical research, writing, and understanding of space history. Not every research project has yielded acceptable results, nor can it be expected to do so, but the sum of the effort since 1981 has been impressive. The opportunities for both the exploration of space and for recording its history have been significant. Both endeavors are noble and aimed at the enhancement of humanity. Whither the history of spaceflight? Only time will tell. But there has been an emergent "new aerospace history" of which space history is a central part that moves beyond an overriding concern for the details of the artifact to emphasize the broader role of the spacecraft. More importantly, it emphasizes the whole technological system, including not just the vehicle but also the other components that make up the aerospace climate, as an integral part of the human experience. It suggests that many unanswered questions spur the development of flight and that inquisitive individuals seek to know that which they do not understand.

Dick, Steven J.↗
NASA NTRS2006

Software Reuse Within the Earth Science Community

Scientific missions in the Earth sciences frequently require cost-effective, highly reliable, and easy-to-use software, which can be a challenge for software developers to provide. The NASA Earth Science Enterprise (ESE) spends a significant amount of resources developing software components and other software development artifacts that may also be of value if reused in other projects requiring similar functionality. In general, software reuse is often defined as utilizing existing software artifacts. Software reuse can improve productivity and quality while decreasing the cost of software development, as documented by case studies in the literature. Since large software systems are often the results of the integration of many smaller and sometimes reusable components, ensuring reusability of such software components becomes a necessity. Indeed, designing software components with reusability as a requirement can increase the software reuse potential within a community such as the NASA ESE community. The NASA Earth Science Data Systems (ESDS) Software Reuse Working Group is chartered to oversee the development of a process that will maximize the reuse potential of existing software components while recommending strategies for maximizing the reusability potential of yet-to-be-designed components. As part of this work, two surveys of the Earth science community were conducted. The first was performed in 2004 and distributed among government employees and contractors. A follow-up survey was performed in 2005 and distributed among a wider community, to include members of industry and academia. The surveys were designed to collect information on subjects such as the current software reuse practices of Earth science software developers, why they choose to reuse software, and what perceived barriers prevent them from reusing software. In this paper, we compare the results of these surveys, summarize the observed trends, and discuss the findings. The results are very similar, with the second, larger survey confirming the basic results of the first, smaller survey. The results suggest that reuse of ESE software can drive down the cost and time of system development, increase flexibility and responsiveness of these systems to new technologies and requirements, and increase effective and accountable community participation.

Marshall, James J.↗
NASA NTRS2005

Failure Assessment

Three questions to which software developers want accurate, precise answers are "How can the software system fail?", "mat bad things will happen if the software fails?t', and "How many failures will the software experience?". Numerous techniques have been devised to answer these questions; three of the best known are: 1) Software Fault Tree Analysis (SFTA) 2) Software Failure Modes, Effects, and Criticality Analysis (SFMECA 3) Software Fault/Failure Modeling. SFTA and SFMECA have been successfully used to analyze the flight software for a number of robotic planetary exploration missions, including Galileo, Cassini, and Deep Space 1. Given the increasing interest in reusing software components from mission to mission, one of us has developed techniques for reusing the corresponding portions of the SFTA and SFMECA, reducing the effort required to conduct these analyses. SFTA has also been shown to be effective in analyzing the security aspects of software systems; intrusion mechanisms and effects can easily be modeled using these techniques. The Bi- Directional Safety Analysis (BDSA) method combines a forward search (similar to SFMECA) from potential failure modes to their effects, with a backward search (similar to SFTA) from feasible hazards to the contributing causes of each hazard. BDSA offers an efficient way to identify latent failures. Recent work has extended BDSA to product-line applications such as flight-instrumentation displays and developed tool support for the reuse of the failure-analysis artifacts within a product line. BDSA has also been streamlined to support those projects having tight cost and/or schedule constraints for their failure analysis efforts. We discuss lessons learned from practice, describe available tools, and identi@ some future directions for the topic. A substantial amount of research has been devoted to estimating the number of failures that a software system will experience during test and operations, as well as the number of faults that have been inserted into that system during its development. One of us has found that the amount of structural change to a system during its development is strongly related to the number of faults inserted into it. Using techniques requiring no additional effort on the part of the development organization, the required measurements of structural evolution can be easily obtained from a development effort's configuration management system and readily transformed into an estimate of fault content. So far, structure-fault relationships have been identified for source code; current work seeks to examine artifacts available earlier in the lifecycle to determine if similar relationships between structure and fault content can be found. In particular, relationships between requirements change requests and the number of faults inserted into the implemented system would provide a significant improvement in our ability to control software quality during the early development phases.

fault tree↗
NASA NTRS2006

A Predictive Approach to Eliminating Errors in Software Code

NASA s Metrics Data Program Data Repository is a database that stores problem, product, and metrics data. The primary goal of this data repository is to provide project data to the software community. In doing so, the Metrics Data Program collects artifacts from a large NASA dataset, generates metrics on the artifacts, and then generates reports that are made available to the public at no cost. The data that are made available to general users have been sanitized and authorized for publication through the Metrics Data Program Web site by officials representing the projects from which the data originated. The data repository is operated by NASA s Independent Verification and Validation (IV&V) Facility, which is located in Fairmont, West Virginia, a high-tech hub for emerging innovation in the Mountain State. The IV&V Facility was founded in 1993, under the NASA Office of Safety and Mission Assurance, as a direct result of recommendations made by the National Research Council and the Report of the Presidential Commission on the Space Shuttle Challenger Accident. Today, under the direction of Goddard Space Flight Center, the IV&V Facility continues its mission to provide the highest achievable levels of safety and cost-effectiveness for mission-critical software. By extending its data to public users, the facility has helped improve the safety, reliability, and quality of complex software systems throughout private industry and other government agencies. Integrated Software Metrics, Inc., is one of the organizations that has benefited from studying the metrics data. As a result, the company has evolved into a leading developer of innovative software-error prediction tools that help organizations deliver better software, on time and on budget.

Source record↗
NASA NTRS2001

Method and apparatus for calibrating a tiled display

A display system that can be calibrated and re-calibrated with a minimal amount of manual intervention. To accomplish this, one or more cameras are provided to capture an image of the display screen. The resulting captured image is processed to identify any non-desirable characteristics, including visible artifacts such as seams, bands, rings, etc. Once the non-desirable characteristics are identified, an appropriate transformation function is determined. The transformation function is used to pre-warp the input video signal that is provided to the display such that the non-desirable characteristics are reduced or eliminated from the display. The transformation function preferably compensates for spatial non-uniformity, color non-uniformity, luminance non-uniformity, and other visible artifacts.

Johnson, Michael J.↗
NASA NTRS2001

Method and apparatus for calibrating a display using an array of cameras

The present invention overcomes many of the disadvantages of the prior art by providing a display that can be calibrated and re-calibrated with a minimal amount of manual intervention. To accomplish this, the present invention provides one or more cameras to capture an image that is projected on a display screen. In one embodiment, the one or more cameras are placed on the same side of the screen as the projectors. In another embodiment, an array of cameras is provided on either or both sides of the screen for capturing a number of adjacent and/or overlapping capture images of the screen. In either of these embodiments, the resulting capture images are processed to identify any non-desirable characteristics including any visible artifacts such as seams, bands, rings, etc. Once the non-desirable characteristics are identified, an appropriate transformation function is determined. The transformation function is used to pre-warp the input video signal to the display such that the non-desirable characteristics are reduced or eliminated from the display. The transformation function preferably compensates for spatial non-uniformity, color non-uniformity, luminance non-uniformity, and/or other visible artifacts.

Johnson, Michael J.↗
NASA NTRS2006

Validation of CALIPSO Lidar Observations Using Data From the NASA Langley Airborne High Spectral Resolution Lidar

This poster focuses on preliminary comparisons of data from the Cloud-Aerosol Lidar with Orthogonal Polarization (CALIOP) instrument on the Cloud-Aerosol Lidar and Infrared Pathfinder Satellite Observations (CALIPSO) spacecraft with data acquired by the NASA Langley Airborne High Spectral Resolution Lidar (HSRL). A series of 20 aircraft validation flights was conducted from 14 June through 27 September 2006, under both day and night lighting conditions and a variety of aerosol and cloud conditions. This poster presents comparisons of CALIOP measurements of attenuated backscatter at 532 and 1064 nm and depolarization at 532 nm with near coincident measurements from the Airborne HSRL as a preliminary assessment of CALIOP calibration accuracy. Note that the CALIOP data presented here are the pre-release version. These data have known artifacts in calibration which have been corrected in the December 8 CALIPSO data release which was not available at the time the comparisons were conducted for this poster. The HSRL data are also preliminary. No artifacts are known to exist; however, refinements in calibration and algorithms are likely to be implemented before validation comparisons are made final.

Hostetler, Chris↗
NASA NTRS2006

Effect of DC Offset on the T-Wave Residuum Parameter

The T-wave residuum (TWR) is a relatively new 12-lead ECG parameter that may reflect cardiac repolarization heterogeneity. TWR shows clinical promise and may become an important diagnostic tool if accurate, consistent, and convenient methods for its calculation can be developed. However, there are discrepancies between the methods that various investigators have used to calculate TWR, as well as some questions about basic methodology and assumptions that require resolution. The presence of a DC offset or very low frequency AC component to the ECG is often observed. Many researchers have attempted to compensate for these by high pass filters and by median beat techniques. These techniques may help minimize the contribution of a low frequency AC component to the TWR, but they will not eliminate a DC offset inherent within the instrumentation. The present study examined the presence of DC offsets in the ECG record, and their effect on TWR. Specifically, in healthy individuals, a DC offset was added to all 8 channels collectively or to each channel selectively. Even with offsets that were relatively small compared to T-wave amplitude, the addition of either collectively or individually applied offsets was observed to produce very significant changes in the TWR, affecting its value by as much as an order of magnitude. These DC offsets may arise from at least two possible sources: a transient artifact from EMG or electrode movement resulting in a transient baseline offset in one or more channels. Since highpass filters have a settling time of several seconds, these artifacts will contribute to a transitory baseline offset lasting 1020 cycles. The machine hardware may also introduce an offset. Regardless of the cause or source of a DC offset, this study demonstrates that offsets have a very significant impact on TWR, and that future studies must not ignore their presence, but rather more appropriately compensate for them.

Scott, N.↗
NASA NTRS2008

Residual Strahls in Solar Wind Electron Dropouts: Signatures of Magnetic Connection to the Sun, Disconnection, or Interchange Reconnection?

A recent assessment of suprathermal electron heat flux dropouts (HFDs) in the solar wind eliminated 90% as possible signatures of field lines disconnected from the Sun at both ends (Pagel et al., 2005b). The primary reason for elimination was the presence of a residual field-aligned strahl presumably signaling field lines connected to the Sun. Using high-time-resolution data from the Wind spacecraft, this paper tests whether the residual strahls were an artifact of averaging over pitch angle distributions (PADs) with and without strahls. An automated search for PADs without strahls (flat PADs) yields an occurrence rate of only 14% within HFDs, but a detailed case study shows that these flat PADs are imbedded within intervals of nearly flat PADs, that is, PADS with residual strahls that cannot be artifacts of averaging. An attractive alternative is that the residual strahls result from intermixing of originally back-scattered fluxes (haloes) of unequal intensities on field lines that have either disconnected or interchange reconnected at the Sun. A reevaluation of reported streaming of higher-energy electrons in HFDs suggests a similar cause. While the high-time-resolution data show high variability of PAD profiles within HFDs, this paper reopens the possibility that a substantial fraction signal disconnection or interchange reconnection. Estimated occurrence rates of fields having undergone these processes based upon published HFD rates are of the same order of magnitude as the surprisingly low values of 1-5% recently predicted by a model of a balanced heliospheric flux budget (Owens and Crooker, 2007).

Crooker, N. U.↗
NASA NTRS2010

Sensitivity of Aerosol Multi-Sensor Daily Data Intercomparison to the Level 3 Dataday Definition

Topics include: why people use Level 3 products, why someone might go wrong with Level 3 products, differences in L3 from different sensors, Level 3 data day definition, MODIS vs. MODIS, AOD MODIS Terra vs. Aqua in Pacific, AOD Aqua MODIS vs. MISR correlation map, MODIS vs MISR on Terra, MODIS atmospheric data day definition, orbit time difference for Terra and Aqua 2009-01-06, maximum time difference for Terra (Calendar day), artifact explains, data day definitions, local time distribution, spatial (local time) data day definition, maximum time difference between Terra and Aqua, Removing the artifact in 16-day AOD correlation, MODIS cloud top pressure, and MODIS Terra and Aqua vs. AIRS cloud top pressure.

Leptoukh, Gregory↗
NASA NTRS2010

Configuring the Orion Guidance, Navigation, and Control Flight Software for Automated Sequencing

The Orion Crew Exploration Vehicle is being designed with greater automation capabilities than any other crewed spacecraft in NASA s history. The Guidance, Navigation, and Control (GN&C) flight software architecture is designed to provide a flexible and evolvable framework that accommodates increasing levels of automation over time. Within the GN&C flight software, a data-driven approach is used to configure software. This approach allows data reconfiguration and updates to automated sequences without requiring recompilation of the software. Because of the great dependency of the automation and the flight software on the configuration data, the data management is a vital component of the processes for software certification, mission design, and flight operations. To enable the automated sequencing and data configuration of the GN&C subsystem on Orion, a desktop database configuration tool has been developed. The database tool allows the specification of the GN&C activity sequences, the automated transitions in the software, and the corresponding parameter reconfigurations. These aspects of the GN&C automation on Orion are all coordinated via data management, and the database tool provides the ability to test the automation capabilities during the development of the GN&C software. In addition to providing the infrastructure to manage the GN&C automation, the database tool has been designed with capabilities to import and export artifacts for simulation analysis and documentation purposes. Furthermore, the database configuration tool, currently used to manage simulation data, is envisioned to evolve into a mission planning tool for generating and testing GN&C software sequences and configurations. A key enabler of the GN&C automation design, the database tool allows both the creation and maintenance of the data artifacts, as well as serving the critical role of helping to manage, visualize, and understand the data-driven parameters both during software development and throughout the life of the Orion project.

Odegard, Ryan G.↗
NASA NTRS2010

The Effect of Satellite Observing System Changes on MERRA Water and Energy Fluxes

Because reanalysis data sets offer state variables and fluxes at regular space / time intervals, atmospheric reanalyses have become a mainstay of the climate community for diagnostic purposes and for driving offline ocean and land models. Although one weakness of these data sets is the susceptibility of the flux products to uncertainties because of shortcomings in parameterized model physics, another issue, perhaps less appreciated, is the fact that continual but discreet changes in the evolving observational system, particularly from satellite sensors, may also introduce artifacts in the time series of quantities. In this paper we examine the ability of the NASA MERRA (Modern Era Retrospective Analysis for Research and Applications) and other recent reanalyses to determine variability in the climate system over the satellite record (approximately the last 30 years). In particular we highlight the effect on the reanalysis of discontinuities at the junctures of the onset of passive microwave imaging (Special Sensor Microwave Imager) in late 1987 as well as improved sounding and imaging with the Advanced Microwave Sounding Unit, AMSU-A, in 1998. We first examine MERRA fluxes from the perspective of how physical modes of variability (e.g. ENSO events, Pacific Decadal Variability) are contaminated by artificial step-like trends induced by the onset of new moisture data these two satellite observing systems. Secondly, we show how Redundancy Analysis, a statistical regression methodology, is effective in relating these artifact signals in the moisture and temperature analysis increments to their presence in the physical flux terms (e.g. precipitation, radiation). This procedure is shown to be effective greatly reducing the artificial trends in the flux quantities.

Robertson, Franklin R.↗
NASA NTRS2006

State Analysis Database Tool

The State Analysis Database Tool software establishes a productive environment for collaboration among software and system engineers engaged in the development of complex interacting systems. The tool embodies State Analysis, a model-based system engineering methodology founded on a state-based control architecture (see figure). A state represents a momentary condition of an evolving system, and a model may describe how a state evolves and is affected by other states. The State Analysis methodology is a process for capturing system and software requirements in the form of explicit models and states, and defining goal-based operational plans consistent with the models. Requirements, models, and operational concerns have traditionally been documented in a variety of system engineering artifacts that address different aspects of a mission s lifecycle. In State Analysis, requirements, models, and operations information are State Analysis artifacts that are consistent and stored in a State Analysis Database. The tool includes a back-end database, a multi-platform front-end client, and Web-based administrative functions. The tool is structured to prompt an engineer to follow the State Analysis methodology, to encourage state discovery and model description, and to make software requirements and operations plans consistent with model descriptions.

Rasmussen, Robert↗
NASA NTRS2006

Improvement in Recursive Hierarchical Segmentation of Data

A further modification has been made in the algorithm and implementing software reported in Modified Recursive Hierarchical Segmentation of Data (GSC- 14681-1), NASA Tech Briefs, Vol. 30, No. 6 (June 2006), page 51. That software performs recursive hierarchical segmentation of data having spatial characteristics (e.g., spectral-image data). The output of a prior version of the software contained artifacts, including spurious segmentation-image regions bounded by processing-window edges. The modification for suppressing the artifacts, mentioned in the cited article, was addition of a subroutine that analyzes data in the vicinities of seams to find pairs of regions that tend to lie adjacent to each other on opposite sides of the seams. Within each such pair, pixels in one region that are more similar to pixels in the other region are reassigned to the other region. The present modification provides for a parameter ranging from 0 to 1 for controlling the relative priority of merges between spatially adjacent and spatially non-adjacent regions. At 1, spatially-adjacent-/spatially- non-adjacent-region merges have equal priority. At 0, only spatially-adjacent-region merges (no spectral clustering) are allowed. Between 0 and 1, spatially-adjacent- region merges have priority over spatially- non-adjacent ones.

Tilton, James C.↗
NASA NTRS2010

Separating Real and Apparent Effects of Cloud, Humidity, and Dynamics on Aerosol Optical Thickness near Cloud Edges

Aerosol optical thickness (AOT) is one of aerosol parameters that can be measured on a routine basis with reasonable accuracy from Sun-photometric observations at the surface. However, AOT-derived near clouds is fraught with various real effects and artifacts, posing a big challenge for studying aerosol and cloud interactions. Recently, several studies have reported correlations between AOT and cloud cover, pointing to potential cloud contamination and the aerosol humidification effect; however, not many quantitative assessments have been made. In this study, various potential causes of apparent correlations are investigated in order to separate the real effects from the artifacts, using well-maintained observations from the Aerosol Robotic Network, Total Sky Imager, airborne nephelometer, etc., over the Southern Great Plains site operated by the U.S. Department of Energy's Atmospheric Radiation Measurement Program. It was found that aerosol humidification effects can explain about one fourth of the correlation between the cloud cover and AOT. New particle genesis, cloud-processed particles, atmospheric dynamics, and aerosol indirect effects are likely to be contributing to as much as the remaining three fourth of the relationship between cloud cover and AOT.

Jeong, Myeong-Jae↗
NASA NTRS2011

Requirement Assurance: A Verification Process

Requirement Assurance is an act of requirement verification which assures the stakeholder or customer that a product requirement has produced its "as realized product" and has been verified with conclusive evidence. Product requirement verification answers the question, "did the product meet the stated specification, performance, or design documentation?". In order to ensure the system was built correctly, the practicing system engineer must verify each product requirement using verification methods of inspection, analysis, demonstration, or test. The products of these methods are the "verification artifacts" or "closure artifacts" which are the objective evidence needed to prove the product requirements meet the verification success criteria. Institutional direction is given to the System Engineer in NPR 7123.1A NASA Systems Engineering Processes and Requirements with regards to the requirement verification process. In response, the verification methodology offered in this report meets both the institutional process and requirement verification best practices.

Alexander, Michael G.↗