scholarly journals Introduction of an automatic and open‐source radio‐tracking system for small animals

2019 ◽  
Vol 10 (12) ◽  
pp. 2163-2172
Author(s):  
Jannis Gottwald ◽  
Ralf Zeidler ◽  
Nicolas Friess ◽  
Marvin Ludwig ◽  
Christoph Reudenbach ◽  
...  
2016 ◽  
Vol 3 (1) ◽  
pp. 107-128
Author(s):  
Syed Nadeem Ahsan ◽  
Muhammad Tanvir Afzal ◽  
Safdar Zaman ◽  
Christian Gütel ◽  
Franz Wotawa

During the evolution of any software, efforts are made to fix bugs or to add new features in software. In software engineering, previous history of effort data is required to build an effort estimation model, which estimates the cost and complexity of any software. Therefore, the role of effort data is indispensable to build state-of-the-art effort estimation models. Most of the Open Source Software does not maintain any effort related information. Consequently there is no state-of-the-art effort estimation model for Open Source Software, whereas most of the existing effort models are for commercial software. In this paper we present an approach to build an effort estimation model for Open Source Software. For this purpose we suggest to mine effort data from the history of the developer’s bug fix activities. Our approach determines the actual time spend to fix a bug, and considers it as an estimated effort. Initially, we use the developer’s bug-fix-activity data to construct the developer’s activity log-book. The log-book is used to store the actual time elapsed to fix a bug. Subsequently, the log-book information is used to mine the bug fix effort data. Furthermore, the developer’s bug fix activity data is used to define three different measures for the developer’s contribution or expertise level. Finally, we used the bug-fix-activity data to visualize the developer’s collaborations and the involved source files. In order to perform an experiment we selected the Mozilla open source project and downloaded 93,607 bug reports from the Mozilla project bug tracking system i.e., Bugzilla. We also downloaded the available CVS-log data from the Mozilla project repository. In this study we reveal that in case of Mozilla only 4.9% developers have been involved in fixing 71.5% of the reported bugs.


Author(s):  
Liguo Yu

Android is an operating system for mobile devices. Its development is led by Google and some other companies. Because of the open-source property of Android, anyone can report a bug through its online bug tracking system. In this paper, we analyze the bug reports of Android operating systems. Specifically, through this study, we would like to answer the following questions regarding Android development and its project management: (1) Could Android bug reports be handled on time? (2) What is the distribution of different maintenance activities initiated by Android bug reports? (3) How long does it take to handle an Android bug report? (4) Are the number of followers and the number of following messages of an Android bug report related to the effort spent on handling this bug report? Through answering these questions, this paper presents a comprehensive study of Android bug reporting and handling process. The information and knowledge obtained through this case study could help us better understand open-source software project, such as its development process and project management.


2009 ◽  
pp. 1079-1110 ◽  
Author(s):  
Kevin Crowston ◽  
Barbara Scozzi

Free/Libre open source software (FLOSS, e.g., Linux or Apache) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards, yet some how profit from the advantages and evade the challenges of distributed software development. In this article we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research.


2009 ◽  
pp. 797-828
Author(s):  
Kevin Crowston ◽  
Barbara Scozzi

Free/Libre open source software (FLOSS, e.g., Linux or Apache) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards, yet some how profit from the advantages and evade the challenges of distributed software development. In this article we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research.


2017 ◽  
Vol 13 (5) ◽  
pp. e1005530 ◽  
Author(s):  
Benjamin Risse ◽  
Dimitri Berh ◽  
Nils Otto ◽  
Christian Klämbt ◽  
Xiaoyi Jiang

1963 ◽  
Vol 27 (1) ◽  
pp. 9 ◽  
Author(s):  
William W. Cochran ◽  
Rexford D. Lord

Author(s):  
Shigeru Yamada ◽  
Masakazu Yamaguchi

A software development paradigm for open source software (OSS) project has been rapidly spread in recent years. On the other hand, an effective method of quality management has not been established due to the unique development characteristics such as no testing phase. In this paper, we assume that the number of fault-detections observed on the bug tracking system tends to infinity, and discuss a method of statistical process control (SPC) for OSS projects by applying the logarithmic Poisson execution time model as a software reliability growth model (SRGM) based on a nonhomogeneous Poisson process (NHPP). Then, we propose a control chart method based on the logarithmic Poisson execution time model for judging the statical stability state, and estimating the additional development time for attaining the objective software failure intensity, i.e., the target value of the instantaneous fault-detection rate per unit time. We also discuss an optimal software release problem for determining the optimum time when to stop OSS development and to transfer it to user operation. Further, numerical illustrations for SPC are shown by applying the actual fault-count data observed on the bug tracking system.


2017 ◽  
Author(s):  
Udit Arora ◽  
Sohit Verma ◽  
Sarthak Sahni ◽  
Tushar Sharma

Several ball tracking algorithms have been reported in literature. However, most of them use high-quality video and multiple cameras, and the emphasis has been on coordinating the cameras or visualizing the tracking results. This paper aims to develop a system for assisting the umpire in the sport of Cricket in making decisions like detection of no-balls, wide-balls, leg before wicket and bouncers, with the help of a single smartphone camera. It involves the implementation of Computer Vision algorithms for object detection and motion tracking, as well as the integration of machine learning algorithms to optimize the results. Techniques like Histogram of Gradients (HOG) and Support Vector Machine (SVM) are used for object classification and recognition. Frame subtraction, minimum enclosing circle, and contour detection algorithms are optimized and used for the detection of a cricket ball. These algorithms are applied using the Open Source Python Library - OpenCV. Machine Learning techniques - Linear and Quadratic Regression are used to track and predict the motion of the ball. It also involves the use of open source Python library VPython for the visual representation of the results. The paper describes the design and structure for the approach undertaken in the system for analyzing and visualizing off-air low-quality cricket videos.


2020 ◽  
Vol 40 (3) ◽  
pp. 379-391 ◽  
Author(s):  
Andrea S. Griffin ◽  
Culum Brown ◽  
Bradley K. Woodworth ◽  
Guy-Anthony Ballard ◽  
Stuart Blanch ◽  
...  

Technologies for remotely observing animal movements have advanced rapidly in the past decade. In recent years, Australia has invested in an Integrated Marine Ocean Tracking (IMOS) system, a land ecosystem observatory (TERN), and an Australian Acoustic Observatory (A2O), but has not established movement tracking systems for individual terrestrial animals across land and along coastlines. Here, we make the case that the Motus Wildlife Tracking System, an open-source, rapidly expanding cooperative automated radio-tracking global network (Motus, https://motus.org ) provides an unprecedented opportunity to build an affordable and proven infrastructure that will boost wildlife biology research and connect Australian researchers domestically and with international wildlife research. We briefly describe the system conceptually and technologically, then present the unique strengths of Motus, how Motus can complement and expand existing and emerging animal tracking systems, and how the Motus framework provides a much-needed central repository and impetus for archiving and sharing animal telemetry data. We propose ways to overcome the unique challenges posed by Australia’s ecological attributes and the size of its scientific community. Open source, inherently cooperative and flexible, Motus provides a unique opportunity to leverage individual research effort into a larger collaborative achievement, thereby expanding the scale and scope of individual projects, while maximising the outcomes of scant research and conservation funding.


Sign in / Sign up

Export Citation Format

Share Document