3 resultados para fault correction
em DigitalCommons@University of Nebraska - Lincoln
Resumo:
I. Gunter and Christmas (1973) described the events leading to the stranding of a baleen whale on Ship Island, Mississippi, in 1968, giving the species as Balaenopteru physalus, the Rorqual. Unfortunately the identification was in error, but fortunately good photographs were shown. The underside of the tail was a splotched white, but there was no black margin. The specimen also had fewer throat and belly grooves than the Rorqual, as a comparison with True’s (1904) photograph shows. Dr. James Mead (in litt.) pointed out that the animal was a Sei Whale, Balaenoptera borealis. This remains a new Mississippi record and according to Lowery’s (1974) count, it is the fifth specimen reported from the Gulf of Mexico. The stranding of a sixth Sei Whale on Anclote Keys in the Gulf, west of Tarpon Springs, Florida on 30 May 1974, was reported in the newspapers and by the Smithsonian Institution (1974). II. Gunter, Hubbs and Beal (1955) gave measurements on a Pygmy Sperm Whale, Kogia breviceps, which stranded on Mustang Island on the Texas coast and commented upon the recorded variations of proportional measurements in this species. Then according to Raun, Hoese and Moseley (1970) these questions were resolved by Handley (1966), who showed that a second species, Kogia simus, the Dwarf Sperm Whale, is also present in the western North Atlantic. Handley’s argument is based on skull comparisons and it seems to be rather indubitable. According to Raun et al. (op. cit.), the stranding of a species of Kogia on Galveston Island recorded by Caldwell, Ingles and Siebenaler (1960) was K. simus. They also say that Caldwell (in litt.) had previously come to the same conclusion. Caldwell et al. also recorded another specimen from Destin, Florida, which is now considered to have been a specimen of simus. The known status of these two little sperm whales in the Gulf is summarized by Lowery (op. cit.).
Resumo:
End users develop more software than any other group of programmers, using software authoring devices such as e-mail filtering editors, by-demonstration macro builders, and spreadsheet environments. Despite this, there has been little research on finding ways to help these programmers with the dependability of their software. We have been addressing this problem in several ways, one of which includes supporting end-user debugging activities through fault localization techniques. This paper presents the results of an empirical study conducted in an end-user programming environment to examine the impact of two separate factors in fault localization techniques that affect technique effectiveness. Our results shed new insights into fault localization techniques for end-user programmers and the factors that affect them, with significant implications for the evaluation of those techniques.
Resumo:
Test case prioritization techniques schedule test cases for regression testing in an order that increases their ability to meet some performance goal. One performance goal, rate offault detection, measures how quickly faults are detected within the testing process. In previous work we provided a metric, APFD, for measuring rate of fault detection, and techniques for prioritizing test cases to improve APFD, and reported the results of experiments using those techniques. This metric and these techniques, however, applied only in cases in which test costs and fault severity are uniform. In this paper, we present a new metric for assessing the rate of fault detection of prioritized test cases, that incorporates varying test case and fault costs. We present the results of a case study illustrating the application of the metric. This study raises several practical questions that might arise in applying test case prioritization; we discuss how practitioners could go about answering these questions.