self._normalize() got NAN...
See original GitHub issueBug description
Sir, when I print upsampled_a in upsampled_a = self._normalize(self.hook_a, self.hook_a.ndim - 2)
I got NAN in some value. Is there any bug?
I set model to vgg19 target_layer1=‘features.35’ fc_layer1=‘classifier.6’
Code snippet to reproduce the bug
nan
Error traceback
nan
Environment
nan
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
How to prevent Normalization Formula to produce NaN values?
Explicitly compute mean and std for yourself and see what's going on. And check if any of the entries in the column is...
Read more >How to Repair and Normalize Data with Pandas?
First, let's get the count of the missing (NaN) values per column in our DataFrame. 1. Enter the following command: dataSet.isnull().sum(axis = ...
Read more >NaN when I use Group Normalization (GroupNorm) #40711
i was trying groupnormalization for efficientnet , my model code is : out_dim = 5 enet_type = 'efficientnet-b0' pretrained_model ...
Read more >How to Drop Rows with NaN Values in Pandas DataFrame?
In this article, we will discuss how to drop rows with NaN values. We can drop Rows having NaN Values in Pandas DataFrame...
Read more >Training data becomes nan after several epochs - vision
Hi everyone, In a semantic segmentation network, I use a type of data, normalized between 0 and 1, saved as pickle. After 23...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @lars-nieradzik 👋
Thanks for the specifics, I managed to reproduce the bug. I think I identified the problem, so I opened a PR #185 which should fix this!
The problem was:
eps
during the division part of the normalizationI can confirm this NaN bug. It mostly occurs for ScoreCAM.
Error happens as follows:
self.hook_a
contains NaNFor other (model, CAM) combinations, numerical instabilities may also occur.
800 images: