-
-
Notifications
You must be signed in to change notification settings - Fork 300
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
Dynamic Sfusion #363
base: main
Are you sure you want to change the base?
Dynamic Sfusion #363
Conversation
…nocom/SlimeVR-Tracker-ESP into random-dev-branch-do-not-use
…nocom/SlimeVR-Tracker-ESP into random-dev-branch-do-not-use
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not finished yet...
Don't overclock official slimes Co-authored-by: Eiren Rain <[email protected]>
d4cdeaf
to
4ff6e1b
Compare
float zroChangeOverTemperature = 0; | ||
|
||
void handleTemperatureMeasurement(float temperature, float timeStep) { | ||
#if USE_NONBLOCKING_CALIBRATION |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No C define blocks in softfusion core please :<
Should be separated as different (replaceable) calibration implementation, or at least separated in less spaghetti way :<
#include "../SensorFusionRestDetect.h" | ||
#include "../nonblockingcalibration/NonBlockingCalibration.h" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is subjective but I'm not the fan of "nonblocking" name for that. I think something like "auto" or "self-learning" is more descriptive for what it is.
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
THE SOFTWARE. | ||
*/ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not related strictly to the code, I would like to have some description (in PR I guess) about how that autocalibration works (both gyro and especially accel).
|
||
// Temperature stability constant - how many degrees of temperature for the bias to | ||
// change by 0.01 Though I don't know if it should be 0.1 or 0.01, this is a guess | ||
// and seems to work better than 0.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's neither 0.01 nor 0.1 for any sensor.
Co-authored-by: Eiren Rain <[email protected]>
This PR makes the following changes: