Showing papers by "Sebastian Elbaum published in 2015"
30 Aug 2015
TL;DR: Light is shed into how developers search for code through a case study performed at Google, using a combination of survey and log-analysis methodologies, to provide insights into what developers are doing and trying to learn when forming a search, search scope, query properties, and what a search session under different contexts usually entails.
Abstract: With the advent of large code repositories and sophisticated search capabilities, code search is increasingly becoming a key software development activity. In this work we shed some light into how developers search for code through a case study performed at Google, using a combination of survey and log-analysis methodologies. Our study provides insights into what developers are doing and trying to learn when per- forming a search, search scope, query properties, and what a search session under different contexts usually entails. Our results indicate that programmers search for code very frequently, conducting an average of five search sessions with 12 total queries each workday. The search queries are often targeted at a particular code location and programmers are typically looking for code with which they are somewhat familiar. Further, programmers are generally seeking answers to questions about how to use an API, what code does, why something is failing, or where code is located.
222 citations
TL;DR: It is found that even winds of 5.8 m/s have little impact on the water sampling system and that the samples collected are consistent with traditional techniques for most properties.
Abstract: Obtaining spatially separated, high-frequency water samples from rivers and lakes is critical to enhance our understanding and effective management of freshwater resources. In this work, we present an aerial water sampler and assess the system through field experiments. The aerial water sampler has the potential to vastly increase the speed and range at which scientists obtain water samples while reducing cost and effort. The water sampling system includes 1 a mechanism to capture three 20i¾?ml samples per mission, 2 sensors and algorithms for altitude approximation over water, and 3 software components that integrate and analyze sensor data, control the vehicle, drive the sampling mechanism, and manage risk. We validate the system in the lab, characterize key sensors, develop a framework for quantifying risk, and present results of outdoor experiments that characterize the performance of the system under windy conditions. In addition, we compare water samples from local lakes obtained by our system to samples obtained by traditional sampling techniques. We find that even winds of 5.8i¾?m/s have little impact on the water sampling system and that the samples collected are consistent with traditional techniques for most properties. These experiments show that despite the challenges associated with flying precisely over water, it is possible to quickly obtain scientifically useful water samples with an unmanned aerial vehicle.
111 citations
Patent•
[...]
TL;DR: In this paper, an aerial propulsion system, an altitude sensor system, a water sampling system, and a water pump are used to pump water from a water source into one or more water sample receptacles through the water sampling extension while the vehicle is in flight over the water source.
Abstract: In one aspect, a vehicle includes an aerial propulsion system, an altitude sensor system, a water sampling system, and a control system. The water sampling system includes a water sampling extension configured to extend away from the vehicle, one or more water sample receptacles, and a water pump. The control system is configured to perform operations including: guiding, using the aerial propulsion system, the vehicle over a water source; causing, using sensor data from the altitude sensor system, the vehicle to descend towards the water source so that the water sampling extension contacts the water source; and causing, using the water sampling system, the water pump to pump water from the water source into the one or more water sample receptacles through the water sampling extension while the vehicle is in flight over the water source.
18 citations
TL;DR: In this paper, UAVs have been used to collect environmental data, however, they are largely relegated to collecting data while other humans collect data, such as data collection and data analysis.
Abstract: Increasingly, Unmanned Aerial Systems (UASs) are changing the way that scientists and practitioners collect environmental data. Current UASs, however, are largely relegated to collecting data while...
14 citations
09 Nov 2015
TL;DR: This work explores whether lightweight static analyses can be cost-effective in pinpointing patterns associated with faults tests, and found that several patterns, detectable through simple and efficient static analyses of just the test code, can detect faults with a low false positive rate.
Abstract: Tests are increasingly specified as programs. Expressing tests as code is advantageous in that developers are comfortable writing and running code, and tests can be automated and reused as the software evolves. Tests expressed as code, however, can also contain faults. Some test faults are similar to those found in application code, while others are more subtle, caused by incorrect implementation of testing concepts and processes. These faults may cause a test to fail when it should not, or allow program faults to go undetected. In this work we explore whether lightweight static analyses can be cost-effective in pinpointing patterns associated with faults tests. Our exploration includes a categorization and explanation of test patterns, and their application to 12 open source projects that include over 40K tests. We found that several patterns, detectable through simple and efficient static analyses of just the test code, can detect faults with a low false positive rate, while other patterns would require a more sophisticated and extensive code analysis to be useful.
14 citations
Proceedings Article•
16 May 2015
TL;DR: The ICSE 2015 program spans from Saturday May 16th to Sunday May 24th, following the traditional structure of the core main conference from Wednesday to Friday, complemented by four days of pre-conference and two days of post-conference meetings as discussed by the authors.
Abstract: The ICSE 2015 program spans from Saturday May 16th to Sunday May 24th, following the traditional structure of the core main conference from Wednesday to Friday, complemented by four days of pre-conference and two days of post-conference meetings. The heart of the multi-track main conference is the prestigious Technical Research Paper track, which is accompanied by several other tracks offering altogether stimulating sessions for all tastes.
3 citations
28 Aug 2015
1 citations
Proceedings Article•
16 May 2015
TL;DR: The ICSE 2015 program spans from Saturday May 16th to Sunday May 24th, following the traditional structure of the core main conference from Wednesday to Friday, complemented by four days of pre-conference and two days of post-conference meetings.
Abstract: The ICSE 2015 program spans from Saturday May 16th to Sunday May 24th, following the traditional structure of the core main conference from Wednesday to Friday, complemented by four days of pre-conference and two days of post-conference meetings. The heart of the multi-track main conference is the prestigious Technical Research Paper track, which is accompanied by several other tracks offering altogether stimulating sessions for all tastes.