-
Notifications
You must be signed in to change notification settings - Fork 327
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
[jtc] Improve trajectory sampling efficiency #1297
[jtc] Improve trajectory sampling efficiency #1297
Conversation
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.
LGTM, thanks!
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1297 +/- ##
==========================================
+ Coverage 80.57% 80.63% +0.06%
==========================================
Files 109 109
Lines 9553 9594 +41
Branches 832 834 +2
==========================================
+ Hits 7697 7736 +39
Misses 1578 1578
- Partials 278 280 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
|
we have a deadlock now with the binaries: main fails because of the variants not being synced, and testing fails because of the broken API in the admittance controller 🙈 I triggered the debian image to be rebuilt, so we will have at least one green |
I'll merge that, the failing tests are already on master as well #1356 :/ |
--------- Co-authored-by: Christoph Fröhlich <[email protected]> Co-authored-by: Bence Magyar <[email protected]> (cherry picked from commit b0391e2)
--------- Co-authored-by: Christoph Fröhlich <[email protected]> Co-authored-by: Bence Magyar <[email protected]> (cherry picked from commit b0391e2)
--------- Co-authored-by: Christoph Fröhlich <[email protected]> Co-authored-by: Bence Magyar <[email protected]> (cherry picked from commit b0391e2) Co-authored-by: RobertWilbrandt <[email protected]>
--------- Co-authored-by: Christoph Fröhlich <[email protected]> Co-authored-by: Bence Magyar <[email protected]> (cherry picked from commit b0391e2)
This PR addresses the increasing effort required in
Trajectory::sample()
raised in #1293 by exploiting the monotonically increasing access time for any trajectory. Instead of scanning through the complete trajectory to find the relevant trajectory points for the current sampling time, theTrajectory
class keeps track of the last accessed index and only searches from there on. This supersedes the proposed binary search in #1294 and is based on #474.Based on the requests in #474, i added checks for the new trajectory state to existing tests and added a new test to make sure that the index is correctly reset when calling
Trajectory::update()
. I verified that this indeed solves the problem by re-running the trajectory from #1293 and again plotting the periods betweenwrite()
calls in my hardware interface:The upper plot shows the progression of the period before this change, the lower one the behavior wtih this PR applied. The large spikes at the beginning and end are the start and end of the trajectory, the spikes in the middle are probably a result of me testing this on my normal laptop without RT kernel and doing some things on the side.