Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

navigator_main: reference update for local position #9119

Closed
wants to merge 1 commit into from

Conversation

Stifael
Copy link
Contributor

@Stifael Stifael commented Mar 20, 2018

This method is not used anywhere yet. The next step is to free
the position controller from any gloabal computation.

It is a much smaller version of #7432.

This method is not used anywhere yet. The next step is to free
the position controller from any gloabal computation.
@Stifael Stifael force-pushed the navigator_send_local_triplets branch from 734f2de to c4feb9c Compare March 21, 2018 14:27
@dagar
Copy link
Member

dagar commented Mar 21, 2018

This looks good. Short term we should probably make sure all these reprojection calls aren't too expensive in the cases where the position setpoint triplet is continuously updating.

@LorenzMeier
Copy link
Member

We need to review this carefully. The system is built to work with long flight paths right now and moving everything to local would destroy this as the tangent plane runs away from the spherical coordinate frame.

@Stifael
Copy link
Contributor Author

Stifael commented Mar 22, 2018

@LorenzMeier there is no difference between this implementation and the legacy one, except that that mapping from global to local happens in the navigator.

@dagar
Copy link
Member

dagar commented Mar 22, 2018

Why don't we have navigator periodically update the position setpoint triplet (at a very low rate)? Navigator will operate in whichever coordinate system required. Most missions will be global, but local could become possible. At position setpoint triplet update time the transformation to local is performed.

@Stifael
Copy link
Contributor Author

Stifael commented Mar 22, 2018

Why don't we have navigator periodically update the position setpoint triplet (at a very low rate)?

Do you mean to correct for the earth curvature? Sure.

If I understand it correctly @LorenzMeier refers to the fact that line-tracking in local frame is not as accurate as line-tracking in global-frame where the curvature of the earth is to some extend taken care of (it depends on the projection). I completely agree with this. However, it is important to know that currently for MC the line tracking already happens in local frame anyway and therefore nothing would change with this PR and with any other PR that frees the MC position controller from global frame.

What would be the benefit of having MC running in global frame as well? IMHO that would be a huge downgrade because in contrast to fixedwings, MCs will become more important indoors as well. For MC, mission mode does not have to be only gps dependent, but could very well be supported for local coordinate frame state estimates as well. In addition, there is always the alternative to update the global waypoints more regularly to compensate for the earth curvature (as @dagar suggested?)

@dagar
Copy link
Member

dagar commented Mar 22, 2018

Perhaps we should take a step back and define the basic requirements. From there we can determine an appropriate strategy.

@stale
Copy link

stale bot commented Jan 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@dagar
Copy link
Member

dagar commented Jan 30, 2019

Closing this PR as stale, but I definitely want to prioritize finding a general solution this year.

@dagar dagar closed this Jan 30, 2019
@dagar dagar deleted the navigator_send_local_triplets branch February 6, 2019 03:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants