cedargrovestudios / circuitpython_rangeslicer Goto Github PK

Hi,

After I heard you at the CircuitPython podcast talking about this library, and it got me thinking about a little project of mine. I'm tinkering with an old Wheel controller from the 90s—just a couple of potentiometers and a bunch of buttons. When I first tackled the project, I scaled the potentiometer values between -127 and 127 based on their min and max readings. But, just like you mentioned in the podcast, the potentiometer noise started messing with my values.

I've been playing around with the library for a few days now. To get a handle on things, I collected data on registered values for 50 reads without touching the potentiometer. Check out the results below:

• slice: Value of the slice argument.
• hyst: Value of the hyst argument
• avg_slicer: Average value returned by the range_slicer method.
• avg_scaled: Average value resulted of directly scaling the potentiometer value
• avg_slicer_diff: Average absolute difference between two consecutive values returned by the range_slicer method
• avg_scaled_diff: Average absolute difference between two consecutive scaled values

Looking to the data, I get the following conclusions:

1. The value of slice changes the output value scale without an impact in the noise.
2. The hyst value plays a bigger role in the sliced value. Values below 1 get me results closer to a regular scale.
3. RangeSlicer produces less noise.
4. There is not direct relation between values of slice and hyst, and the noise produced.

When do you think it's smarter to go with RangeSlicer instead of the usual scaling method or a filter? Would you have some tips for selecting a good slice and hyst?

data.csv

Best,
Manuel

Happened to notice you updated this library on my feed, and saw that the latest build failed. Happy to dig into it and fix it, if you'd like - I'm trying to find common issues and their solutions so I can eventually document them.