Preoperative predictive factors for opaque bubble layer formation and area during small-incision lenticule extraction: predictive models based on machine learning
We aimed to develop exploratory machine learning (ML)-based predictive models for the occurrence and area of an opaque bubble layer (OBL) during small-incision lenticule extraction (SMILE) and identify associated preoperative and surgical-planning factors. This retrospective study included 216 eyes (72 with an OBL, 144 controls) that underwent SMILE at the Zhongshan Ophthalmic Center between August 2024 and August 2025, which were matched 1:2 by age and sex. Comprehensive preoperative ocular examinations were performed using a Pentacam HR camera system and standard equipment. The OBL area was quantified from intraoperative videos using ImageJ software. Fifty-four preoperative and surgical features were used to develop the ML models: 15 classification algorithms for OBL occurrence, and 19 regression algorithms for the relative OBL area. Shapley additive explanations analysis was applied for model interpretability. The Extra Trees model achieved optimal performance for predicting OBL occurrence (area under the receiver operating characteristic curve = 0.885, accuracy = 0.820). The top five key factors included femtosecond laser energy, intraocular pressure, residual stromal thickness, 10-mm corneal volume, and total astigmatism, all of which showed positive correlations. For OBL area prediction, the random forest regression model performed best in the test sets (mean absolute error = 2.89%, root mean square error = 3.37%). Corneal optical density (within the central 2-mm zone of the anterior 120-μm corneal layer) and age were negatively associated with OBL area, whereas keratoconus index showed the strongest positive association. The ML models showed exploratory predictive ability for OBL occurrence and area during SMILE using preoperative and surgical-planning parameters. External validation and recalibration in consecutive cohorts with a natural OBL prevalence are required before clinical use.
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.