<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sensor-Driven ML Pipelines on Embedded Systems Development</title><link>https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/</link><description>Recent content in Sensor-Driven ML Pipelines on Embedded Systems Development</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/index.xml" rel="self" type="application/rss+xml"/><item><title>Time-Series Classification</title><link>https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/time-series-classification/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/time-series-classification/</guid><description>&lt;h1 id="time-series-classification"&gt;Time-Series Classification&lt;a class="anchor" href="#time-series-classification"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Time-series classification maps a fixed-length window of sensor data to a discrete class label — a gesture type, an activity state, a machine operating condition. The input is a sequence of sensor readings sampled at a known rate, and the output is a categorical decision: swipe left, swipe right, walking, running, bearing fault, normal operation. Unlike image classification where spatial structure is the dominant signal, time-series classification depends on temporal patterns — the shape, frequency content, and evolution of the signal over the window duration.&lt;/p&gt;</description></item><item><title>Anomaly Detection</title><link>https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/anomaly-detection/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/anomaly-detection/</guid><description>&lt;h1 id="anomaly-detection"&gt;Anomaly Detection&lt;a class="anchor" href="#anomaly-detection"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Anomaly detection learns what &amp;ldquo;normal&amp;rdquo; looks like and flags deviations. Unlike classification, which requires labeled examples of every category, anomaly detection requires only normal data for training — a form of one-class learning. The model builds a representation of normal operating conditions, and anything that falls outside that representation is flagged as anomalous. This property makes anomaly detection particularly valuable for industrial and embedded applications where collecting labeled fault data is expensive, dangerous, or impossible (a machine cannot be intentionally run to failure just to collect training data).&lt;/p&gt;</description></item><item><title>Predictive Maintenance</title><link>https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/predictive-maintenance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/predictive-maintenance/</guid><description>&lt;h1 id="predictive-maintenance"&gt;Predictive Maintenance&lt;a class="anchor" href="#predictive-maintenance"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Predictive maintenance estimates when a machine component will fail, enabling maintenance scheduling after most useful life is consumed but before failure occurs. The distinction from reactive maintenance (fix after failure) and preventive maintenance (replace on a fixed schedule regardless of condition) is that predictive maintenance uses actual sensor measurements to forecast the remaining useful life (RUL) of a component, optimizing the trade-off between maintenance cost and downtime risk.&lt;/p&gt;</description></item><item><title>Sensor Preprocessing for ML</title><link>https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/sensor-preprocessing/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://applied-ee.github.io/embedded/docs/edge-ai/sensor-ml-pipelines/sensor-preprocessing/</guid><description>&lt;h1 id="sensor-preprocessing-for-ml"&gt;Sensor Preprocessing for ML&lt;a class="anchor" href="#sensor-preprocessing-for-ml"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Sensor preprocessing is the bridge between raw sensor hardware and the ML model input tensor. The sensor produces a continuous stream of ADC samples or digital readings at a fixed rate. The model expects a specific fixed-size, normalized tensor at each inference cycle. Between these two endpoints lies a pipeline of buffering, windowing, normalization, and format conversion — and any mismatch between the preprocessing applied during training (in Python on a desktop) and the preprocessing applied during deployment (in C on an MCU) silently degrades model accuracy without producing any error message.&lt;/p&gt;</description></item></channel></rss>