TRV-2026-1989Certified recordPeer-reviewed

Development of a YOLO-guided automated (microplastic) particle analysis workflow

Microplastics (MPs) are an emerging pollutant of global concern, creating an urgent need for rapid and accurate monitoring workflows. Deep learning-based computer vision has demonstrated strong performance in finding particles in microscopy images, but its use as a front-end module for automated IR/Raman microscope-based MP analysis remains insufficiently developed, particularly in workflows that convert image-level particle detection results into microscope-executable operations for particle morphological chara…

Climate · The Trace — both readings · certified 2026-10-20 · v1 · article view · machine-readable

Current reading — gain

A YOLO11 instance segmentation model found reference microplastic particles in microscope images with an F1 of 0.89, beating a threshold method (0.25) and Mask R-CNN (0.84), and was built into an automated analysis workflow.

Current reading — problem

Particle detection performance dropped when image backgrounds were dirtier, as seen in commercial salt samples, which limits reliability on messy real samples.

What this doesn’t fix

Detection performance decreased with dirtier image backgrounds, as shown on a commercial salt sample, so the workflow's accuracy is weaker on less clean real-world samples.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1989, v1: “Development of a YOLO-guided automated (microplastic) particle analysis workflow.” Truvace, 2026-10-20. /record/TRV-2026-1989 (accessed at citation time). sha256 9367ab4af48c899b…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv19367ab4af48c…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1989 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.