-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use for accelerometers and other embedded projects #24
Comments
Hi! Thanks for this, I appreciate it. 🙇♂️ I think the Users won't mind; they will mind however if they picked Assuming If I were to start a project on an embedded platform with a need to get accelerometer data, I'd be way more interested in a collection of snippets that shows me how to get the data myself for that hardware; then I would use whichever data type I need or want (f32 ? u16 ? i16 ? depends on context), whichever math library I want, whichever error crate I want, and then write my app with all of that. To quote John Carmack : To me the most interesting part is in your #20 is sadly not trivially fixable, if you're willing to go down the rabbit hole that leads to transcendantal functions causing overflow panics; I'm not surprised that this is not progressing ;) |
That may be true for now, but I'd like to add a lot more functionality, e.g.: https://github.com/NeoBirth/accelerometer.rs/pull/6/files My goal with this is to have orientation tracking which is generic over all 3-axis accelerometers. To do that I really need a standard vector type. I'm also trying to add noise smoothing through statistical analysis (outlier culling), which in the above implementation is generic across all accelerometer types whose vectors implement my current
Oh really, that's unfortunate to hear. My understanding is the |
Guess I'll close this out as it's blocked on #20. Will keep an eye on that issue though. |
Hello! This is just a heads up that I mentioned
vek
in an issue I opened on the Rust Embedded WG about anaccelerometer
crate:rust-embedded/wg#340
It looks like
vek
might potentially be nice for these applications, aside from #20 which I think looks trivially fixable (I could potentially send a PR).Anyway, if you have any thoughts on this I'd be curious, otherwise feel free to close this issue.
The text was updated successfully, but these errors were encountered: