From dae82835ec043a54ed6bc775f0776e1a7ff99124 Mon Sep 17 00:00:00 2001 From: pantor Date: Sat, 4 May 2024 12:09:09 +0200 Subject: [PATCH] fix link to waypoint docs --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6e96d68..747840d 100644 --- a/README.md +++ b/README.md @@ -116,7 +116,7 @@ input.intermediate_positions = { ``` As soon as at least one intermediate positions is given, the Ruckig Community Version switches to the mentioned (of course, non real-time capable) cloud API. If you require real-time calculation on your own hardware, please contact us for the *Ruckig Pro Version*. -When using *intermediate positions*, both the underlying motion planning problem as well as its calculation changes significantly. In particular, there are some fundamental limitations for jerk-limited online trajectory generation regarding the usage of waypoints. Please find more information about these limitations [here](https://docs.ruckig.com/md_pages__intermediate_waypoints.html), and in general we recommend to use +When using *intermediate positions*, both the underlying motion planning problem as well as its calculation changes significantly. In particular, there are some fundamental limitations for jerk-limited online trajectory generation regarding the usage of waypoints. Please find more information about these limitations [here](https://docs.ruckig.com/md_pages_2__intermediate__waypoints.html), and in general we recommend to use ```.cpp input.intermediate_positions = otg.filter_intermediate_positions(input.intermediate_positions, {0.1, ...}); ```