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

Meaning of the annotation_dict entry of CoTracker3_Kubric data #152

Open
zw615 opened this issue Feb 4, 2025 · 1 comment
Open

Meaning of the annotation_dict entry of CoTracker3_Kubric data #152

zw615 opened this issue Feb 4, 2025 · 1 comment

Comments

@zw615
Copy link

zw615 commented Feb 4, 2025

Hi, thanks for the great work!

I just started to play with the newly released CoTracker3_Kubric dataset. However, I found that there are three different entries associated with depth. There are "coords_depth" and "depth" in the annotation_dict (e.g. 0000.npy) of each sample , and there is also a depth folder where it looks like the depth of each frame is stored in different npy files (e.g. 000.npy-119.npy).

My preliminary exploration sort of indicate the annot_dict["depth"] uses the absolute 512x512 depth map, and annot_dict["depth"] stores the relative depth of each tracked point. However, what is the difference between annot_dict["depth"] and the npy fils under the depth folder? Could you please elaborate on the meaning of these entries?

Moreover, I wonder how did you convert the classic Kubric TFDS format into the current format. I see it in your previous post you used traj_annots = {"coords": data["target_points"], "visibility": data["occluded"]}, but the other important entries like depth or camera or other important meta infos are missing. I wonder if you could show how the conversion between TFDS Kubric data and CoTracker3_Kubric data?

Thanks a lot!

@Charles-Lu
Copy link

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