fix a confusing message for freeze_bn_stats#3166
Merged
deruyter92 merged 2 commits intoDeepLabCut:mainfrom Jan 9, 2026
Merged
Conversation
deruyter92
approved these changes
Jan 9, 2026
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
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 fixes a very confusing message: According to your model configuration, you're training with batch size 1 and/or freeze_bn_stats=false. This is not an optimal setting if you have powerful GPUs.
The condition that triggers this message is
loader.model_cfg["model"].get("freeze_bn_stats", False). Therefore, the user can see this message only whenfreeze_bn_stats=true. This pull request flips the boolean value to give the correct message.DeepLabCut/deeplabcut/pose_estimation_pytorch/apis/training.py
Lines 170 to 188 in ee866cc