Automated classification of self-grooming in mice using open-source software

2017 ◽  
Vol 289 ◽  
pp. 48-56 ◽  
Author(s):  
Bastijn J.G. van den Boom ◽  
Pavlina Pavlidi ◽  
Casper J.H. Wolf ◽  
Adriana H. Mooij ◽  
Ingo Willuhn
2012 ◽  
Vol 4 (1) ◽  
pp. 37-59 ◽  
Author(s):  
Megan Squire

Artifacts of the software development process, such as source code or emails between developers, are a frequent object of study in empirical software engineering literature. One of the hallmarks of free, libre, and open source software (FLOSS) projects is that the artifacts of the development process are publicly-accessible and therefore easily collected and studied. Thus, there is a long history in the FLOSS research community of using these artifacts to gain understanding about the phenomenon of open source software, which could then be compared to studies of software engineering more generally. This paper looks specifically at how the FLOSS research community has used email artifacts from free and open source projects. It provides a classification of the relevant literature using a publicly-available online repository of papers about FLOSS development using email. The outcome of this paper is to provide a broad overview for the software engineering and FLOSS research communities of how other researchers have used FLOSS email message artifacts in their work.


2009 ◽  
pp. 361-370
Author(s):  
Javier Soriano ◽  
Rafael Fernández ◽  
Miguel Jiménez

Traditionally, collaboration has been a means for organizations to do their work. However, the context in which they do this work is changing, especially in regards to where the work is done, how the work is organized, who does the work, and with this the characteristics of collaboration. Software development is no exception; it is itself a collaborative effort that is likewise affected by these changes. In the context of both open source software development projects and communities and organizations that develop corporate products, more and more developers need to communicate and liaise with colleagues in geographically distant places about the software product they are conceiving, designing, building, testing, debugging, deploying and maintaining. Thus, work teams face sizeable collaborative challenges, for which they have need of tools that they can use to communicate and coordinate their work efficiently.


On the occasion of completion of ten years of Open Source Systems (OSS) conferences, this paper studies its contribution to the extension of Free and Open Source Software (FOSS) research. An existing taxonomy was used to initially classify the 347 full and short papers presented in the conferences. Because there were many new categories, which did not fit, in existing system, the taxonomy was revised and the reclassified papers are presented in this paper. The analysis of locations, themes, participants and citations of successive conferences results in interesting observation. The major takeaway of this ongoing study is to demonstrate that the goal of OSS conferences, as mentioned in the first edition, “to promote the exchange of new ideas, research and applications in the emerging field of Open Source Software,” is more than successful.


Author(s):  
M. A. Brovelli ◽  
H. Wu ◽  
M. Minghini ◽  
M. E. Molinari ◽  
C. E. Kilsedar ◽  
...  

<p><strong>Abstract.</strong> Land Cover (LC) maps represent key resources to understand, model and address many global and local dynamics affecting our planet. They are usually derived from the classification of satellite imagery, after which a validation or intercomparison process is performed to assess their accuracy. This paper presents the project “Capacity Building for High-Resolution Land Cover Intercomparison and Validation”, an educational initiative funded by the International Society for Photogrammetry and Remote Sensing (ISPRS) and mainly targeting developing countries. First, with the help of two open surveys, an analysis of the state of the art was performed which assessed the overall good awareness on LC maps and the needs and requirements for validating and comparing them, as well as the rich availability of educational material on this topic. The second task, currently under finalization, is the development of new educational material, based on open source software and released under an open access license, consisting of: an introduction to the GlobeLand30 (GL30) LC map and its online platform; a desktop GIS procedure showing two use cases on GL30 validation; and an application to collect LC data on the field to be used for validation. Finally, this educational material will be tested in practice in three workshops during the second half of the project, two of which held in developing countries: Dar es Salaam, Tanzania and Nairobi, Kenya.</p>


Author(s):  
Yunwen Ye ◽  
Kumiyo Nakakoji ◽  
Yasuhiro Yamamoto ◽  
Kouichi Kishida

Because a Free and Open Source Software (F/OSS) project is unlikely to sustain a long-term success unless there is an associated community that provides the platform for developers, users, and user-turned-developers to collaborate with each other, understanding the well-observed phenomenon that F/OSS systems experience “natural product evolution” cannot be complete without understanding the structure and evolution of their associated communities. This chapter examines the structure of F/OSS communities and the co-evolution of F/OSS systems and communities based on a case study. Although F/OSS systems and communities generally co-evolve, they co-evolve differently depending on the goal of the system and the structure of the community. A systematic analysis of the differences leads us to propose a classification of F/OSS projects into three types: Exploration-Oriented, Utility-Oriented, and Services-Oriented. Practical implications of realizing the co-evolution and recognizing the different types of F/OSS projects are discussed to provide guidance for F/OSS practitioners.


2008 ◽  
pp. 3765-3776
Author(s):  
Yunwen Ye ◽  
Kumiyo Nakakoji ◽  
Yasuhiro Yamamoto ◽  
Kouichi Kishida

Because a Free and Open Source Software (F/OSS) project is unlikely to sustain a long-term success unless there is an associated community that provides the platform for developers, users, and user-turned-developers to collaborate with each other, understanding the well-observed phenomenon that F/OSS systems experience “natural product evolution” cannot be complete without understanding the structure and evolution of their associated communities. This chapter examines the structure of F/OSS communities and the co-evolution of F/OSS systems and communities based on a case study. Although F/OSS systems and communities generally co-evolve, they co-evolve differently depending on the goal of the system and the structure of the community. A systematic analysis of the differences leads us to propose a classification of F/OSS projects into three types: Exploration-Oriented, Utility-Oriented, and Services-Oriented. Practical implications of realizing the co-evolution and recognizing the different types of F/OSS projects are discussed to provide guidance for F/OSS practitioners.


Author(s):  
Javier Soriano ◽  
Rafael Fernández ◽  
Miguel Jiménez

Traditionally, collaboration has been a means for organizations to do their work. However, the context in which they do this work is changing, especially in regards to where the work is done, how the work is organized, who does the work, and with this the characteristics of collaboration. Software development is no exception; it is itself a collaborative effort that is likewise affected by these changes. In the context of both open source software development projects and communities and organizations that develop corporate products, more and more developers need to communicate and liaise with colleagues in geographically distant places about the software product they are conceiving, designing, building, testing, debugging, deploying and maintaining. Thus, work teams face sizeable collaborative challenges, for which they have need of tools that they can use to communicate and coordinate their work efficiently.


Maintenance of open source software is a hectic task as the number of bugs reported is huge. The number of projects, components and versions in an open source project also contribute to the number of bugs that are being reported. Classification of bugs based on priority and identification of the suitable engineers for assignment of bugs for such huge systems still remains a major challenge. Bugs that are misclassified or assigned to engineers who don’t have the component expertise, drastically affect the time taken towards bug resolution. In this paper we have explored the usage of data mining techniques on the classification of bugs and assignment of bugs to engineers.Our focus was on classifying bugs as either severe or non-severe and identification of engineers who have the right expertise to fix the bugs. The prediction of bug severity and identification of engineers were done by mining bug reports from JIRA, an open source software bug tracking tool. The mining process yielded positive results and will be a decision enhancer for severe bugs in the maintenance phase


Sign in / Sign up

Export Citation Format

Share Document