Closed roomrys closed 4 months ago
[!IMPORTANT]
Review skipped
Auto reviews are disabled on base/target branches other than the default branch.
Please check the settings in the CodeRabbit UI or the
.coderabbit.yaml
file in this repository. To trigger a single review, invoke the@coderabbitai review
command.You can disable this status message by setting the
reviews.review_status
tofalse
in the CodeRabbit configuration file.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Attention: Patch coverage is 50.00000%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 74.10%. Comparing base (
42ffe4e
) to head (f85e2f6
).
Files | Patch % | Lines |
---|---|---|
sleap/io/cameras.py | 50.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Description
This PR is a quick fix to the fact that
CameraGroup.optim_points
from the aniposelib library does not handle nan values very well. Theoptim_points
function is only called when we have aSkeleton
with > 20Node
s.If upon triangulating, the user had some
Point
s set as not visible (there are less than 2 visible labels for the same node), then we would get projections that look like so:Overwriting the culprit
CameraGroup.optim_points
to simply pass through the 3D points instead of trying to optimize them yields the desired result:And, when we double click, the non-visible node is initialized closeby:
This PR is just a quick fix to allow people to continue labeling with high-node skeletons until we get a PR (non-existent atm) merged into aniposelib to fix this issue at the source.
Types of changes
Does this address any currently open issues?
[list open issues here]
Outside contributors checklist
Thank you for contributing to SLEAP!
:heart: