Skip to content

Conversation

@cdtwigg
Copy link
Contributor

@cdtwigg cdtwigg commented Sep 29, 2025

Summary:
We have two functions, trackPosesPerframe and trackPosesForFrames, which are largely identical. This kept messing me up because I would add functionality in one of the functions or the other and then be confused why nothing had changed.

Looking at the two functions, they perform the same function, we just need to pass in the appropriate set of frames into trackPosesForFrames and add support for temporal coherence.

Reviewed By: jeongseok-meta

Differential Revision: D82688034

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Meta Open Source bot. label Sep 29, 2025
@facebook-github-bot
Copy link
Contributor

@cdtwigg has exported this pull request. If you are a Meta employee, you can view the originating diff in D82688034.

cdtwigg added a commit that referenced this pull request Oct 7, 2025
Summary:

We have two functions, trackPosesPerframe and trackPosesForFrames, which are largely identical.  This kept messing me up because I would add functionality in one of the functions or the other and then be confused why nothing had changed.  

Looking at the two functions, they perform the same function, we just need to pass in the appropriate set of frames into trackPosesForFrames and add support for temporal coherence.

Reviewed By: jeongseok-meta

Differential Revision: D82688034
facebook-github-bot pushed a commit that referenced this pull request Nov 5, 2025
Summary:

We have two functions, trackPosesPerframe and trackPosesForFrames, which are largely identical.  This kept messing me up because I would add functionality in one of the functions or the other and then be confused why nothing had changed.  

Looking at the two functions, they perform the same function, we just need to pass in the appropriate set of frames into trackPosesForFrames and add support for temporal coherence.

Reviewed By: jeongseok-meta

Differential Revision: D82688034
facebook-github-bot pushed a commit that referenced this pull request Nov 5, 2025
Summary:

We have two functions, trackPosesPerframe and trackPosesForFrames, which are largely identical.  This kept messing me up because I would add functionality in one of the functions or the other and then be confused why nothing had changed.  

Looking at the two functions, they perform the same function, we just need to pass in the appropriate set of frames into trackPosesForFrames and add support for temporal coherence.

Reviewed By: jeongseok-meta

Differential Revision: D82688034
cdtwigg added a commit that referenced this pull request Nov 5, 2025
Summary:
Pull Request resolved: #609

We have two functions, trackPosesPerframe and trackPosesForFrames, which are largely identical.  This kept messing me up because I would add functionality in one of the functions or the other and then be confused why nothing had changed.

Looking at the two functions, they perform the same function, we just need to pass in the appropriate set of frames into trackPosesForFrames and add support for temporal coherence.

Reviewed By: cstollmeta, jeongseok-meta

Differential Revision: D82688034
@meta-codesync
Copy link
Contributor

meta-codesync bot commented Nov 5, 2025

@cdtwigg has exported this pull request. If you are a Meta employee, you can view the originating Diff in D82688034.

facebook-github-bot pushed a commit that referenced this pull request Nov 10, 2025
Summary:

We have two functions, trackPosesPerframe and trackPosesForFrames, which are largely identical.  This kept messing me up because I would add functionality in one of the functions or the other and then be confused why nothing had changed.  

Looking at the two functions, they perform the same function, we just need to pass in the appropriate set of frames into trackPosesForFrames and add support for temporal coherence.

Reviewed By: cstollmeta, jeongseok-meta

Differential Revision: D82688034
Summary:

I find myself wanting to add text labels to things in the image, currently the only way to do that is to fork out to OpenCV.  It would be neat if we could write text to the image but support z-buffer checking, and if we didn't have to fork out to a separate library.

Reviewed By: jeongseok-meta, cstollmeta

Differential Revision: D85690037
Summary:

We have two functions, trackPosesPerframe and trackPosesForFrames, which are largely identical.  This kept messing me up because I would add functionality in one of the functions or the other and then be confused why nothing had changed.  

Looking at the two functions, they perform the same function, we just need to pass in the appropriate set of frames into trackPosesForFrames and add support for temporal coherence.

Reviewed By: cstollmeta, jeongseok-meta

Differential Revision: D82688034
@meta-codesync
Copy link
Contributor

meta-codesync bot commented Nov 11, 2025

This pull request has been merged in 6195b6e.

@jeongseok-meta jeongseok-meta deleted the export-D82688034 branch November 12, 2025 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Meta Open Source bot. fb-exported Merged meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants