Suppress RuntimeWarnings caused by NaNs in keypoint data #150
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request suppresses the following warning that was appearing repeatedly in the GUI:
These warnings were triggered when the dataframe contains
NaNvalues, which is a normal and expected situation during the labels refinement stage, where the model may predictNaNfor some keypoint coordinates.The warning is harmless and does not affect functionality, but cluttered the console and could confuse users.
The suppression is implemented in the plugin’s
__init__.pyusing Python’swarningsmodule, targeting only this specific RuntimeWarning so that other warnings remain visible.No changes to plugin functionality or data handling have been made.