SShortSingh.
Back to feed

Developer catches data-pooling bug that flipped results in wearable IMU activity classifier

0
·2 views

A developer testing the vaas-x zero-config channel classifier on the UCI Daily and Sports Activities dataset — covering 8 subjects wearing five IMU units across 45 sensor channels — initially got physically implausible results, with sitting appearing more active than basketball. The bug was traced to pooling all subjects' data together, which caused between-subject sensor baseline differences to inflate variance for low-motion activities like sitting. Once the test was corrected to profile each subject independently, results aligned with physical reality: sitting averaged 14.8 stable channels versus basketball showing significantly higher channel activity. The fix also better reflects real-world deployment, where a single wearable streams data from one person continuously. The author notes the methodological error is more instructive than the final result, highlighting how test design flaws can silently corrupt machine learning validation.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Google Renames NotebookLM as Gemini Notebook, Integrates It Across Gemini Ecosystem

Google officially renamed NotebookLM to Gemini Notebook on July 16, 2026, repositioning the research tool as part of its broader Gemini ecosystem. The renamed product will sync notebooks across the Gemini app and Google Search, allowing users to organize sources, chats, and AI-assisted analysis in one connected workflow. The rollout is staged and will extend to both Workspace customers and personal account holders. Gemini Notebook supports a wide range of file formats including PDFs, Google Docs, DOCX, PPTX, XLSX, and images, though legacy Microsoft Word .doc files are not confirmed as supported. Google has not announced any pricing or plan changes alongside the rebrand.

0
ProgrammingDEV Community ·

100% Test Coverage Did Not Prevent a Production Outage — Here Is Why

A developer working on Flutter projects where AI models generate much of the codebase discovered that achieving 100% test coverage did not prevent a production failure. The core issue was that coverage tools like lcov only measure which lines were executed, not whether those lines were meaningfully verified by assertions. AI-generated tests frequently run through code without asserting correct outcomes, creating the illusion of thorough testing. The author addresses this by manually reviewing generated tests and deliberately breaking functions to check whether tests actually catch failures. He also excludes auto-generated files, constants, and framework wiring from coverage calculations, while warning that such exclusion lists can easily be misused to inflate scores artificially.

0
ProgrammingDEV Community ·

Apache Polaris 1.7.0 Fixes Data Loss Bug and Tightens Catalog Reliability

Apache Polaris 1.7.0 was released on August 2, 2026, tagged by JB Onofré, addressing a critical data loss scenario where a network drop during a Spark table commit could cause clients to delete metadata files that were already successfully recorded in the catalog. The release introduces idempotent writes to prevent such failures caused by retry logic after ambiguous network responses. Beyond the data loss fix, the update includes a new beta API for semantic models, stricter credential vending and location validation, and improved orphan file cleanup. Although the changelog is dominated by dependency updates giving it the appearance of a routine maintenance release, the core changes focus on catalog correctness rather than new features. Apache Polaris is an open-source Iceberg REST catalog, originally co-created with Snowflake and donated to the Apache Software Foundation, graduating as a Top-Level Project in February 2026.

0
ProgrammingDEV Community ·

Open-Source Tool 'Waste' Streams Giant AI Models from NVMe to Cut RAM Use

A new open-source GitHub project called 'Waste' offers a way to run extremely large AI models, such as the 2.78-trillion-parameter Kimi K3, on hardware with limited RAM. Instead of loading an entire model into memory, Waste streams only the required weights directly from NVMe storage during inference. Written in C and designed to be dependency-free, the tool is intended to integrate easily into existing development workflows. The approach could benefit engineers working in resource-constrained environments like edge devices, IoT systems, or low-memory cloud instances. However, developers are cautioned that streaming weights from storage may introduce latency, making performance benchmarking essential before production deployment.