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

Follow-up on Issue 83: Tracking drifting towards the end fo the samples #119

Closed
KomputerMaster64 opened this issue May 11, 2024 · 3 comments

Comments

@KomputerMaster64
Copy link

This is in continuation of the Issue #83

the bottom two images show a significant jump which is not very suitable for tracking. You can increase the camera frame rate if possible. Otherwise, you can also try with higher iter

parser.add_argument('--track_refine_iter', type=int, default=2)

Hi @wenbowen123

I am sorry for the delayed response.
I ran the experiments with values for track_refine_iter variable ranging from 2 to 50, however it was observed that the tracking invariably drifted towards the end samples (last 15 to 20 percent of the video).
I would be delighted to share the files.

Regards,
Prabhav

__
Edit: I am sharing the failure case for the case with track_refine_iter variable set to 50.

Remarks: For the shown case, the tracking failure happends towards the end of the samples. The tracking is optimal till image 1714129813249.png i.e. for the first 410 samples (Total of 619 image samples).

Additional Remarks: This is an improvement it to the first case where track_refine_iter variable was set to 2, and the tracking was optimal only upto the 157 image samples.

I have uploaded the new FoundationPose_demo_05_eri-5_tri-50.zip file here (this is corresponding to the track_refine_iter variable set to 50) in the Google Drive Folder.

Question/Note: The total size of the debugging directories for the 49 experiments is 7 GB. It would be great if you could confirm if it is required to share all of the experiments' files.

__
The last frame with the correct tracking (top), and the frame after which the trakcing was not optimal (bottom).
1714129813249
1714129813295

@wenbowen123
Copy link
Collaborator

I checked your logs. The object is moving too fast at 1714129813249. Your camera frequency is not fast enough.

@KomputerMaster64
Copy link
Author

KomputerMaster64 commented Jun 10, 2024

Thank you for the response. I will check for better camera hardware. Do you recommend performing actions at a slower pace?
I have been using the Depth Camera D435i - Intel RealSense.
I will be testing FoundationPose with the Depth Camera D455 - Intel RealSense.

@wenbowen123
Copy link
Collaborator

did you check how much fps is the camera images? The upper bound of realsense is 30hz, but sometimes it could be lower than that. In the video, you are ejecting the cube to perform free-form sliding, that moment the motion is really big.

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

2 participants