Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add more information about acceleration/velocity parametrization in trajectory examples #251

Merged
merged 2 commits into from
Jan 24, 2025

Conversation

urfeex
Copy link
Member

@urfeex urfeex commented Jan 24, 2025

The examples were mainly using either time parametrization or implicit acc/vel parametrization using the default values.

This adds more explicit acc/vel parametrized motions to the examples with some explaining comments.

…rajectory examples

The examples were mainly using either time parametrization or implicit
acc/vel parametrization using the default values.

This adds more explicit acc/vel parametrized motions to the examples
with some explaining comments.
@urfeex urfeex requested a review from a team January 24, 2025 12:00
Copy link

codecov bot commented Jan 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.20%. Comparing base (2c12bee) to head (ad27e99).
Report is 10 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #251      +/-   ##
==========================================
+ Coverage   71.71%   73.20%   +1.49%     
==========================================
  Files          71       75       +4     
  Lines        2786     2889     +103     
  Branches      353      360       +7     
==========================================
+ Hits         1998     2115     +117     
+ Misses        596      587       -9     
+ Partials      192      187       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@urfeex urfeex changed the title Add more information about acceleration/velocity parametrization in t… Add more information about acceleration/velocity parametrization in trajectory examples Jan 24, 2025
Copy link
Member

@urrsk urrsk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See my comments as optional, though it took me a minut to understand why points.size() * 2

for (size_t i = 0; i < points.size(); i++)
{
// setting the cartesian parameter makes it interpret the 6d vector as a pose and use movel
g_my_driver->writeTrajectoryPoint(points[i], true, motion_durations[i], blend_radii[i]);
}

// Same motion, but parametrized with acceleration and velocity
motion_durations = { 0.0, 0.0 };
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should have some different "writeTrajecotryPoint() function. Like one without the duration, as it is optional to define it. When we do not need to have a zero vector here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might have to sit down and think about an API 2.0 at some point.

Co-authored-by: Rune Søe-Knudsen <41109954+urrsk@users.noreply.github.com>
@urfeex urfeex merged commit 2bab046 into UniversalRobots:master Jan 24, 2025
23 checks passed
@urfeex urfeex deleted the update_motion_examples branch January 24, 2025 13:32
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants