Fixing Memory Issues in the Quaternion Structure for ESP-Drone Firmware#117
Open
abhay1234668 wants to merge 1 commit into
Open
Fixing Memory Issues in the Quaternion Structure for ESP-Drone Firmware#117abhay1234668 wants to merge 1 commit into
abhay1234668 wants to merge 1 commit into
Conversation
…ng the code, so it was fixed by changing it to have both a group of four numbers in a row and named parts (x, y, z, w) to keep it safe and work with existing code.
Collaborator
|
@abhay1234668 Thank you for your contribution. However, regarding the changes you made to the code, there seems to be no discernible difference between the original code and the modified code. Could you provide more context about this issue? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This update addresses a previously identified issue in the project where the [briefly describe the problem, e.g., "sensor data logging was inconsistent due to a timestamp handling error"]. The root cause was traced to [explain briefly, e.g., "a missing condition in the data logging function that failed to capture system time under certain conditions"].
The logic within the affected module has been corrected to ensure that sensor data is now captured and recorded with accurate timestamps. In addition, redundant code segments were removed to streamline the function, and comments were added to clarify the flow for future contributors. The changes have been tested using [mention if you used sample data, unit tests, etc.], and the output has been verified against expected behavior.