Engineering topics

Knight, John

Publications and source records attributed to Knight, John.

5 records

DOE OSTI2021

EGS Collab Experiment 2: Core Photographs and Descriptions

This submission contains photographs of rock core collected from EGS Collab Experiment 2 (and 3) boreholes. Cores were generally photographed in about 1-foot sections using Nikon D3300 DSLR cameras from two angles about 90 degrees apart, wet and dry. Core photos are provided here in .zip files for each well, organized in subfolders by depth interval. Panoramic photographs of the rock cores as well as description and anomaly logs are also available here.

15 GEOTHERMAL ENERGY↗

DOE OSTI2020

Initial Field Testing in the Deep Subsurface for the Thermal Breakout Project for Measuring In Situ Stress

The current state-of-the-art technology for in situ stress measurements involves an integrated approach that combines borehole breakout observations, drilling-induced tensile fractures, and hydraulic fracturing tests (i.e., mini-fracs); however, this methodology has several limitations that often prevent successful in situ stress measurements. One major limitation is that breakouts do not appear in every borehole and are generally a natural occurrence that cannot easily be controlled. Because borehole breakouts are used to measure the maximum horizontal in situ stress magnitude, the absence of borehole breakouts presents a major data gap for in situ stress measurements. As a response to this data gap a new thermal breakout technology is being developed that will provide a method for thermally inducing borehole breakouts and obtaining consistent measurements of the maximum horizontal stress magnitude. This thermal breakout technology involves heating the borehole and increasing the thermoelastic compressive stress in the rock until a breakout develops, which is directly correlated to the maximum horizontal stress magnitude. An initial component of the thermal breakout project involves developing a prototype downhole tool and performing field testing in the deep subsurface. The primary objective of the initial tool development and field testing is to provide a physical proof of concept for the thermal breakout technology. Three thermal breakout field tests were performed at approximately 4850 feet deep in the Sanford Underground Research Facility. Each test was performed in a borehole that had been previously used for overcoring stress measurements. The third and final test successfully created two diametrically opposed breakouts after deploying the thermal breakout tool for approximately 3 hours of continuous heating. Post-analysis of the thermally induced breakouts confirmed that the thermal breakout orientation directly corresponds to the known in situ stress orientation and magnitude.

Voegeli, Sam↗

NASA NTRS2010

Formal Verification of Large Software Systems

We introduce a scalable proof structure to facilitate formal verification of large software systems. In our approach, we mechanically synthesize an abstract specification from the software implementation, match its static operational structure to that of the original specification, and organize the proof as the conjunction of a series of lemmas about the specification structure. By setting up a different lemma for each distinct element and proving each lemma independently, we obtain the important benefit that the proof scales easily for large systems. We present details of the approach and an illustration of its application on a challenge problem from the security domain

Yin, Xiang↗

NASA NTRS1990

Analysis of faults detected in a large-scale multi-version software development experiment

In a multiversion software experiment, twenty programs were built to the same specification of an inertial navigation problem. The programs were then subjected to a three-phase testing and debugging process: an acceptance test, a certification test, and an operational test. Less than 20 percent of the faults discovered during the certification and operational testing were nonunique, i.e., the same or very similar faults would be found in more than one program. However, some of these common faults spanned as many as half of the versions. Faults discovered during the certification testing were due to specification errors and ambiguities, inadequate programmer background knowledge, insufficient programming experience, incomplete analysis, and insufficient acceptance testing. Faults discovered during the operational testing were of a more subtle nature, and were mostly due to various programmer knowledge defects and incomplete analysis errors. Techniques that might have prevented the observed faults are discussed.

Vouk, Mladen A.↗

NASA NTRS1985

Preliminary design of the redundant software experiment

The goal of the present experiment is to characterize the fault distributions of highly reliable software replicates, constructed using techniques and environments which are similar to those used in comtemporary industrial software facilities. The fault distributions and their effect on the reliability of fault tolerant configurations of the software will be determined through extensive life testing of the replicates against carefully constructed randomly generated test data. Each detected error will be carefully analyzed to provide insight in to their nature and cause. A direct objective is to develop techniques for reducing the intensity of coincident errors, thus increasing the reliability gain which can be achieved with fault tolerance. Data on the reliability gains realized, and the cost of the fault tolerant configurations can be used to design a companion experiment to determine the cost effectiveness of the fault tolerant strategy. Finally, the data and analysis produced by this experiment will be valuable to the software engineering community as a whole because it will provide a useful insight into the nature and cause of hard to find, subtle faults which escape standard software engineering validation techniques and thus persist far into the software life cycle.

Campbell, Roy↗