Skip to content
This repository has been archived by the owner on Aug 3, 2021. It is now read-only.

timescale of cf.starttrajectory conmmand in test_high_level.py #172

Open
Allenhanbo opened this issue Feb 23, 2020 · 1 comment
Open

timescale of cf.starttrajectory conmmand in test_high_level.py #172

Allenhanbo opened this issue Feb 23, 2020 · 1 comment

Comments

@Allenhanbo
Copy link

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?

@whoenig
Copy link
Owner

whoenig commented Feb 26, 2020

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants