Avoid division in JD calc, when possible #17945
Merged
Conversation
This file contains 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
There's no need for a division, if the axis is not limiting. This solution typically requires four multiplications instead of four divisions. In the worst case (all axis limiting in descending order), four divisions + four multiplications can be necessary, but that should be exceedingly rare.
|
Now, to just make those curves smoother somehow… |
vgadreau
pushed a commit
to vgadreau/Marlin
that referenced
this pull request
May 29, 2020
jmp0x0000
pushed a commit
to jmp0x0000/Marlin
that referenced
this pull request
Aug 7, 2020
njibhu
pushed a commit
to njibhu/Marlin
that referenced
this pull request
Aug 24, 2020
HairingX
pushed a commit
to HairingX/Marlin
that referenced
this pull request
Jun 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
There's no need for a division, if the axis is not limiting. This solution typically requires three to four multiplications instead of three to four divisions. In the worst case (all axis limiting in descending order), four divisions + four multiplications can be necessary, but that should be exceedingly rare.
Technically, the
if (unit_vec[idx]) {check is not required anymore, since a divide by zero is avoided bylimit_value * ABS(unit_vec[idx]) > settings.max_acceleration_mm_per_s2[idx]. I kept the check nonetheless, to avoid another multiplication when possible.Benefits
Typically saves three to four divides per block planned and only requires three to four multiplications in return.
Related Issues
None.