Question regarding CSI extraction implementation and Hardware dependency #8

Closed
opened 2025-12-26 21:23:30 +08:00 by ahmetaligul01 · 0 comments
ahmetaligul01 commented 2025-12-26 21:23:30 +08:00 (Migrated from github.com)

Hello,

Looking at the repo structure and documentation, it's pretty clear this was AI-generated. The extensive README and polished docs don't match up with what's actually in the code.

I've been trying to understand the actual implementation, but critical components seem to be missing:

  1. CSI Extraction: The project claims to be "hardware-agnostic" and work with "commodity routers," but real CSI extraction needs specific chipsets (Intel 5300, Atheros, etc.) with modified firmware/drivers. There's no low-level code for capturing actual CSI data from network interfaces.

  2. Signal Processing Logic: The core algorithm for mapping RF signals to pose coordinates is basically absent. There's no actual deep learning pipeline to process signal data into pose estimation - just mock interfaces and placeholder code.Could you clarify if this is just a conceptual prototype or AI-generated boilerplate? The "production-ready" claims in the README are misleading if the core functionality doesn't actually exist.

Thanks

Hello, Looking at the repo structure and documentation, it's pretty clear this was AI-generated. The extensive README and polished docs don't match up with what's actually in the code. I've been trying to understand the actual implementation, but critical components seem to be missing: 1. CSI Extraction: The project claims to be "hardware-agnostic" and work with "commodity routers," but real CSI extraction needs specific chipsets (Intel 5300, Atheros, etc.) with modified firmware/drivers. There's no low-level code for capturing actual CSI data from network interfaces. 2. Signal Processing Logic: The core algorithm for mapping RF signals to pose coordinates is basically absent. There's no actual deep learning pipeline to process signal data into pose estimation - just mock interfaces and placeholder code.Could you clarify if this is just a conceptual prototype or AI-generated boilerplate? The "production-ready" claims in the README are misleading if the core functionality doesn't actually exist. Thanks
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dearsky/wifi-densepose#8