Oct 2026· Zenodo (CERN European Organization for Nuclear Research)
Water Quality Monitoring Technologies
Abstract
This reproducibility package accompanies the manuscript “An autonomous imaging system for reef fish monitoring in the southern Gulf of Mexico”, submitted to Frontiers in Marine Science. Version 2.0.0 corresponds to the revised analytical workflow developed during peer review. The package contains the data, analytical inputs, R code, supplementary tables, reference figures, and documentation required to reproduce the final analyses and publication outputs presented in the revised manuscript, including Figures 2–8 and Supplementary Figures S1–S2 and Tables S1–S3. The package includes a documented, branch-based reproducibility workflow; machine-readable data and analytical matrices; portable R scripts; software-environment and data-dictionary documentation; a file manifest and SHA-256 checksums; and final reference outputs for validation. Figure 5 was generated in R, including the final nMDS ordinations and graphical production. The nested ANOSIM analyses reported with Figure 5 were performed in PRIMER v8. The author-created PRIMER workspace and corresponding open-format inputs and results are included to preserve reproducibility of that statistical component; PRIMER software is not distributed. Computer-vision-derived ecological analyses use frozen inference outputs from the RF-DETR Medium model archived separately in the canonical RF-DETR v1.0.1 reproducibility release (DOI: 10.5281/zenodo.23005643). Reproduction of the ecological analyses does not require model retraining or re-inference. Image preprocessing and sampling provenance is linked to cam2model v0.3.0 (tag v0.3.0; commit ba757e7d4fbbb48582d1168c48d1a48c3bcf3e9a). Historical random sampling does not need to be rerun to reproduce the published analyses. The complete reproducibility package is distributed as SAMP_reproducibility_v2.0.0.zip. See the included README.md, RUN_ORDER.md, DATA_DICTIONARY.md, MANIFEST.csv, and CHECKSUMS.sha256 for package structure, execution order, data definitions, provenance, and integrity verification.
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
It is proved that any global minimizer of the trajectory balance objective can define a policy that samples exactly from the target distribution, and empirically demonstrate the benefits of the trajectories balance objective for GFlowNet convergence, diversity of generated samples, and robustness to long action sequenc...
Esmeralda S. Whitammer, Moksh Jain, Emmanuel Bengio et al.· Neural Information Processin...· 302 citations· ⚡60
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.