Velocity attribution in orbit.py (Orbit Trajectory) multirotor code example

[arielingrid]

In orbit.py airsim example code for orbit trajectory, I would like to understand why the calculation of velocity (that will be passed to moveByVelocityAsync func) is done as the subtraction of coordinate position values?

Position coordinates is returned by the following function:

Ubuntu 18.04, AirSim v1.4.0

[jonyMarino]

Hi @arielingrid! I didn't go too deep into the code, but I understand that it is correct because the speed is that distance per second, if the modulus of the distance is always the same, then the modulus of the speed in that trajectory will be too

[arielingrid]

Hi @jonyMarino, thanks for reply.
The problem is that the code attributes the difference of distances (lookahead_x, pos.x_val, etc) to a velocity (vx, vy). Velocity and distance have different units (m/s and m). One possible explanation could be the fact that the time would be 1 sec. Still don't understanding...