You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 3, 2021. It is now read-only.
Hi WHoenig, I have a question about the timescale in cf.starttrajectory of test_high_level.py.
As we know, the trajectory we designd using your uav_trajectory package is a 7th order polynomial. And each time of segment in trajectory we designed is fixed, which means the whole trajectory time is already fixed when it was designed.
I found in test_high_level.py, there's a timescale option in cf.starttrajectory. If I set the timescale = 1.0, which means the drone's flying time is equal the trajectory time we design?
The text was updated successfully, but these errors were encountered:
Yes - it's essentially a factor. So 1.0 means "real-time", a number less than 1 makes the execution faster, and a number larger than 1 makes it slower.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi WHoenig, I have a question about the timescale in cf.starttrajectory of test_high_level.py.
As we know, the trajectory we designd using your uav_trajectory package is a 7th order polynomial. And each time of segment in trajectory we designed is fixed, which means the whole trajectory time is already fixed when it was designed.
I found in test_high_level.py, there's a timescale option in cf.starttrajectory. If I set the timescale = 1.0, which means the drone's flying time is equal the trajectory time we design?
The text was updated successfully, but these errors were encountered: