ruckig
ruckig copied to clipboard
Motion Generation for Robots and Machines. Real-time. Jerk-constrained. Time-optimal.
 The method `Trajectory::get_position_extrema()` returns extrema which are way off for certain trajectories. An example is shown in the screenshot, where the trajectory starts at x=760,y=384 and ends at x=760,y=762....
I get sometimes "array subscript out of range" exception for very short trajectories. Here's what I've found in the debugger:  Might this be a numerical issue not properly handled...
Possible solution for #212 . How the output looks like running the script now: ``` Trajectory duration: 3.8796 [s] Position at time 1.0000 [s]: [0.6388750444233515, -1.1631409505208554, -0.11589549559277784] Positions at times...
Input: ``` inp.control_interface = ControlInterface.Velocity inp.synchronization = Synchronization.No inp.current_position = [0] inp.current_velocity = [5] inp.current_acceleration = [-1] inp.target_position = [20] inp.target_velocity = [4] inp.target_acceleration = [-3] inp.max_velocity = [5] inp.max_acceleration...
Hi, How can one modify at_time to accept a vector of times to obtain a whole trajectory at once? I am using the Python wrapper Thanks in advance