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

Kidnapped T265 #4288

Closed
JimmyFroost opened this issue Jun 25, 2019 · 10 comments
Closed

Kidnapped T265 #4288

JimmyFroost opened this issue Jun 25, 2019 · 10 comments
Labels
T260 series Intel® T265 library

Comments

@JimmyFroost
Copy link

JimmyFroost commented Jun 25, 2019

|---------------------------------|------------------------------------------- |
| Camera Model | T265 |
| Operating System & Version | Windows 10 | |
| Platform | PC |
| Language | Matlab |

Hi

After experimenting T265 for a few months now, I've witnessed the phenomenom where the camera loses its way and finds it back.
Here is a small example where we see that the trajectory shifts a bit to the left and gets back to normal a few moments later :

image

Camera was set on a small cart, approximately 50cm above the ground.

My question is : if the camera is able to relocate itself , what can we do about false coordinates that we get during it's being kidnapped ?
The confidence is high (=3) but we still have bad positioning ?
Is there any way to fix the bad xyz that have been recorded ?

I cannot find any clear information about this on Intel's website , only a few general and vague stuff here

I read :

Our How-Tos and video tutorials cover everything from basics to advanced techniques.

but I can't find anything. Hopefully I am mistaken and someone can help me ?

I also have a D415, can the use of both of them improve this?

thank you

@dorodnic dorodnic added the T260 series Intel® T265 library label Jun 25, 2019
@ArtlyStyles
Copy link

how fast was the cart moving?

@JimmyFroost
Copy link
Author

I was walking and pushing the cart quite slowly, slower than a usual walking speed.
I don't need to go fast for the project I'm working on, I'd rather say the slower the better

@JimmyFroost
Copy link
Author

JimmyFroost commented Jun 27, 2019

Another day, some other tests, some other kidnapping events !

Let me add this question :
How come the confidence value is still 3 (ie high) when the camera loses its way ? Is there no indicator that allows to understand:

  • camera IMU is getting "moving state" value
  • camera fisheyes see that new elements are coming in display, aka camera is moving

and yet the trajectory is still, or speed is almost null ?

@PaulKrush
Copy link

See issue #3516 and PR #4321

There are two different ways to look at this. Some people want the jump not to happen. I am like you and I want to pose history updated so the jump does not exist in the recorded path.

@radfordi
Copy link
Contributor

Yes, I think you'll want to disable jumping once #4321 gets merged and the firmware gets updated.

@JimmyFroost
Copy link
Author

Thank you @PaulKrush & @radfordi , I remember seeing this #4321 indeed.

Hopefully we'll have it in an update soon !

@RealSenseCustomerSupport
Copy link
Collaborator


The "pose jumping" option integrated in 2.25.0.

@JimmyFroost
Copy link
Author

Sorry for "re-opening" this issue, but I'm not sure if this is possible with Matlab ?
I'm understanding it's not yet.

@radfordi
Copy link
Contributor

Thanks for pointing out that the Matlab wrappers needed updating @JimmyFroost. Here's a PR to address that: #4666.

@JimmyFroost
Copy link
Author

Thanks 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T260 series Intel® T265 library
Projects
None yet
Development

No branches or pull requests

6 participants