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

True range only localisation #27

Open
Boubside opened this issue Jul 13, 2020 · 1 comment
Open

True range only localisation #27

Boubside opened this issue Jul 13, 2020 · 1 comment

Comments

@Boubside
Copy link

Hi,

I'm posting this issue to ask for some help regarding the use of the Tubex library for my robotics problem.
I'm trying to perform the range only localization of an agent relative to three beacons. Because the beacons are very close together, the computation of the position of the agent is very sensitive to measurement error. That's why I'd like to use constraints programming to combine multiple measurement at different times in order to compute an hopefully more precise trajectory.

Looking at the examples and documentation, they are programs working with range only measurements, but they make use of the estimated speed of the agent. I don't have access to this information. My need is rather to combine high frequency range data to estimate speed and position. Is there a way to do it with constrain programming as is in Tubex ? Maybe you would have so educated suggestion on the way to solve this ?

My other questions is about the way to use Tubex for online computation. The examples work with the entire trajectory and all measurements created at the beginning of the code before contracting the trajectory, so i have issues understanding how I can use Tubex to do some online localization. Basically how can I Asynchronously add a new measurement to refine the estimation from the couple last measurements.

Thanks a lot for you're help. Feel free to ask any more information. I have high hopes about this library being able to solve my precision issue.

@Boubside
Copy link
Author

To be more precise, the only assumption I can make about the speed is that it's continuous, it is in the range [-2;+2] in both dimensions and the acceleration is capped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant