Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
GeoComb is a desktop application for detecting honeycomb cells and classifying their contents in frame photographs. This repository provides supporting data, trained model weights, analysis scripts, and Windows applications for the GeoComb study. The data archive includes 52 in-house frame images and annotations, divided into 39 training, 7 validation, and 6 test images; ROI annotation records and dataset inventories; and reference annotations, saved predictions, and analysis data for the 29-image benchmark comprising 13 DeepBee, 10 FAIRHive, and 6 in-house images. Supporting analyses cover geometric detection stages, frame-level cell counts and content composition, and comparison of the hierarchical classifier with a single eight-class classifier. Scripts and figure source data are included for reproducing the reported analyses. Model files include the ROI segmentation model, three hierarchical classification models, and the single eight-class baseline model. Windows CPU and NVIDIA CUDA applications are provided as separate archives. Data package version 1.0.1 updates dataset documentation and adds supporting analysis materials. The four deployment models and reported evaluation values are unchanged. The Windows applications accompany GeoComb software version 1.0.0. DeepBee and FAIRHive source images are available from their original providers. DeepBee-derived training crops and GeoComb-corrected DeepBee training annotations are not redistributed. Source code: https://github.com/zlddh95-eng/GeoComb Licensing: Original images, annotations, analysis results, and documentation created by the GeoComb authors are licensed under CC BY 4.0. GeoComb source code is licensed under AGPL-3.0-only. Third-party data, model components, and bundled dependencies retain their respective licenses and notices.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.