cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with AFS tool on MEMS Studio -- bad data?

rbmarcus
Associate II

Tools/Software/etc:

  • SensorTile.box PRO with DATALOG2_Release firmware
  • STBLE Sensor app (to trigger data collection)
  • hsdatalog_to_unico.py
  • MEMS Studio v1.4.1
  • Ubuntu Linux 24.04

I watched a handful of webinars and read through tutorials related to the LSM6DSV16X's machine learning core. Most of these covered the basics, but only the basics (as in, they only show the most barebones demonstration with a single sample of a single simple movement). When attempting to generate a decision tree on my own using custom data, I ran into several problems.

First, I collected 4 samples of a basic jab motion and labeled the data "strike" and "retract" for each. Everything worked up to the point where I generated the decision tree and got a confidence value of 0%. Then, I attempted to simplify the data and only use one sample of one movement (just the strike component). At this point, I began to see the error below when running the AFS tool. 

Screenshot from 2024-12-03 12-51-46.png

I collected new samples, this time a simpler and slower bicep curl movement:

Screenshot from 2024-12-03 13-38-06.png

Even with the new data, I continue seeing the same error when running the AFS tool. Is this a bug, or something I'm doing wrong? My goal is to eventually detect baseball swings and use the interrupt from the MLC as a trigger for storing high-frequency IMU data, but at the moment I'm not able to successfully produce a configuration for the MLC using simple movements.

10 REPLIES 10
Miroslav BATEK
ST Employee

Thank you. I was able to replicate the issue and we are analyzing it.

It seems the error is triggered if you want to calculate Windows length + Filters + Features, but in case of separate Windows length and Filters + Features calculation the error doesn't appear. Maybe you can use this two step approach as temporary workaround.