You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wanted to give a big thanks for putting together this library!
I included it in my esp8266 voltmeter (data logger) project and it improved the accuracy with very little extra effort on my part, just had to learn how to call your api - and that was pretty easy.
tiny suggestion: for things that are positive integers (like number of points), maybe make that more explicit that its unsigned int rather than it.
it would also be interesting to know what the memory needs/usage is, as you choose the number of points and order of the poly.
again, thanks for such a great contribution.
The text was updated successfully, but these errors were encountered:
Hey, glad you're finding it useful! I've not touched this in a long time.
Right now the memory allocated is static, IIRC to make sure it doesn't crash, as the memory usage can be huge for larger orders (i think it's n^3 ish)
But I do have some dynamic matrix code from a while back so could make memory not static. right now it relies on the MAX ORDER #define somewhere.
I think the "x" value can be negative, where the x values are the LHS of the y axis.
My bad - looking at the source it's all allocated on the stack - so there's no theoretical max order, just the size of your stack.
It could do with some cleaning up but if it works, it works!
Have you written a post about using it to calibrate your voltmeter? If so I could link to it on my blog https://workyourtech.com
wanted to give a big thanks for putting together this library!
I included it in my esp8266 voltmeter (data logger) project and it improved the accuracy with very little extra effort on my part, just had to learn how to call your api - and that was pretty easy.
tiny suggestion: for things that are positive integers (like number of points), maybe make that more explicit that its unsigned int rather than it.
it would also be interesting to know what the memory needs/usage is, as you choose the number of points and order of the poly.
again, thanks for such a great contribution.
The text was updated successfully, but these errors were encountered: