Fix calibration initialization issue in calibrate() #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, calibrationData[3][2] was set to zeros since read() was not called before getX(), getY(), and getZ(). This caused incorrect calibration when any axis had consistently positive or negative values, resulting in max/min values being zero.
This fix removes the unnecessary assignment to calibrationData[3][2], ensuring proper calibration.