<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Industrial Vision | Dat Viet Thanh Nguyen</title><link>https://datvtn.github.io/tags/industrial-vision/</link><atom:link href="https://datvtn.github.io/tags/industrial-vision/index.xml" rel="self" type="application/rss+xml"/><description>Industrial Vision</description><generator>Hugo Blox Builder (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Thu, 01 Apr 2021 00:00:00 +0000</lastBuildDate><image><url>https://datvtn.github.io/media/icon_hu82c06b08a282889123d30d9b11b05ced_13465_512x512_fill_lanczos_center_3.png</url><title>Industrial Vision</title><link>https://datvtn.github.io/tags/industrial-vision/</link></image><item><title>Industrial Surface Defect Detection</title><link>https://datvtn.github.io/project/surface-defect-detection/</link><pubDate>Thu, 01 Apr 2021 00:00:00 +0000</pubDate><guid>https://datvtn.github.io/project/surface-defect-detection/</guid><description>&lt;p>&lt;strong>Jan 2021 – Apr 2021&lt;/strong>&lt;/p>
&lt;h2 id="problem">Problem&lt;/h2>
&lt;p>Industrial defect inspection is an unbalanced detection problem with an unforgiving cost function: defects are rare, visually subtle, and vary in severity, while a false negative ships a bad part and a false positive stops a line. The output the customer needs is not just &lt;em>defect / no defect&lt;/em> but a &lt;strong>grade&lt;/strong> — how severe, and therefore what to do about it.&lt;/p>
&lt;h2 id="approach">Approach&lt;/h2>
&lt;p>I built the detection and grading models, and — the part that shaped the project most — the integration path.&lt;/p>
&lt;p>The customer&amp;rsquo;s existing inspection software was a .NET application, not a Python stack. Rather than standing up a separate inference service and forcing a network hop into a line-rate process, the model was packaged as a &lt;strong>.NET-consumable DLL&lt;/strong> so it could be called directly from the existing application. That removed a whole class of latency and deployment failure modes, at the cost of doing the native packaging and memory-management work properly.&lt;/p>
&lt;p>On the modelling side, the emphasis was on the severity grading step: getting a reliable ordering of defect severity out of a detector matters more to the operator than squeezing the last point of detection mAP.&lt;/p>
&lt;h2 id="tech-stack">Tech stack&lt;/h2>
&lt;p>&lt;code>PyTorch&lt;/code> · &lt;code>LibTorch&lt;/code> · &lt;code>C++&lt;/code> · &lt;code>.NET DLL integration&lt;/code> · &lt;code>OpenCV&lt;/code>&lt;/p>
&lt;h2 id="outcome">Outcome&lt;/h2>
&lt;p>Delivered as an integrated component of the customer&amp;rsquo;s existing inspection application.&lt;/p>
&lt;!-- TODO: add defect classes covered, grading accuracy, and throughput per part if these can be shared publicly. --></description></item></channel></rss>