Comparability of automated drusen volume measurements in age-related macular degeneration: a MACUSTAR study report

Drusen are hallmarks of early and intermediate age-related macular degeneration (AMD) but their quantification remains a challenge. We compared automated drusen volume measurements between different OCT devices. We included 380 eyes from 200 individuals with bilateral intermediate (iAMD, n = 126), early (eAMD, n = 25) or no AMD (n = 49) from the MACUSTAR study. We assessed OCT scans from Cirrus (200 × 200 macular cube, 6 × 6 mm; Zeiss Meditec, CA) and Spectralis (20° × 20°, 25 B-scans; 30° × 25°, 241 B-scans; Heidelberg Engineering, Germany) devices. Sensitivity and specificity for drusen detection and differences between modalities were assessed with intra-class correlation coefficients (ICCs) and mean difference in a 5 mm diameter fovea-centered circle. Specificity was > 90% in the three modalities. In eAMD, we observed highest sensitivity in the denser Spectralis scan (68.1). The two different Spectralis modalities showed a significantly higher agreement in quantifying drusen volume in iAMD (ICC 0.993 [0.991–0.994]) than the dense Spectralis with Cirrus scan (ICC 0.807 [0.757–0.847]). Formulae for drusen volume conversion in iAMD between the two devices are provided. Automated drusen volume measures are not interchangeable between devices and softwares and need to be interpreted with the used imaging devices and software in mind. Accounting for systematic difference between methods increases comparability and conversion formulae are provided. Less dense scans did not affect drusen volume measurements in iAMD but decreased sensitivity for medium drusen in eAMD. Trial registration: ClinicalTrials.gov NCT03349801. Registered on 22 November 2017

KEMNAD: A Knowledge Engineering Methodology for Negotiating Agent Development

Automated negotiation is widely applied in various domains. However, the development of such systems is a complex knowledge and software engineering task. So, a methodology there will be helpful. Unfortunately, none of existing methodologies can offer sufficient, detailed support for such system development. To remove this limitation, this paper develops a new methodology made up of: (1) a generic framework (architectural pattern) for the main task, and (2) a library of modular and reusable design pattern (templates) of subtasks. Thus, it is much easier to build a negotiating agent by assembling these standardised components rather than reinventing the wheel each time. Moreover, since these patterns are identified from a wide variety of existing negotiating agents(especially high impact ones), they can also improve the quality of the final systems developed. In addition, our methodology reveals what types of domain knowledge need to be input into the negotiating agents. This in turn provides a basis for developing techniques to acquire the domain knowledge from human users. This is important because negotiation agents act faithfully on the behalf of their human users and thus the relevant domain knowledge must be acquired from the human users. Finally, our methodology is validated with one high impact system

Automated Fixing of Programs with Contracts

This paper describes AutoFix, an automatic debugging technique that can fix faults in general-purpose software. To provide high-quality fix suggestions and to enable automation of the whole debugging process, AutoFix relies on the presence of simple specification elements in the form of contracts (such as pre- and postconditions). Using contracts enhances the precision of dynamic analysis techniques for fault detection and localization, and for validating fixes. The only required user input to the AutoFix supporting tool is then a faulty program annotated with contracts; the tool produces a collection of validated fixes for the fault ranked according to an estimate of their suitability. In an extensive experimental evaluation, we applied AutoFix to over 200 faults in four code bases of different maturity and quality (of implementation and of contracts). AutoFix successfully fixed 42% of the faults, producing, in the majority of cases, corrections of quality comparable to those competent programmers would write; the used computational resources were modest, with an average time per fix below 20 minutes on commodity hardware. These figures compare favorably to the state of the art in automated program fixing, and demonstrate that the AutoFix approach is successfully applicable to reduce the debugging burden in real-world scenarios.Comment: Minor changes after proofreadin

Overcoming Language Dichotomies: Toward Effective Program Comprehension for Mobile App Development

Mobile devices and platforms have become an established target for modern software developers due to performant hardware and a large and growing user base numbering in the billions. Despite their popularity, the software development process for mobile apps comes with a set of unique, domain-specific challenges rooted in program comprehension. Many of these challenges stem from developer difficulties in reasoning about different representations of a program, a phenomenon we define as a "language dichotomy". In this paper, we reflect upon the various language dichotomies that contribute to open problems in program comprehension and development for mobile apps. Furthermore, to help guide the research community towards effective solutions for these problems, we provide a roadmap of directions for future work.Comment: Invited Keynote Paper for the 26th IEEE/ACM International Conference on Program Comprehension (ICPC'18