Open jinglin80 opened 3 years ago
Hi @jinglin80 Thank you very much for reporting this issue. Have you already found out what might lead to this behaviour?
Hi @beat-buesser I think the problem is related to the forward_step function (lines 180-195). If you add a print statement (print(new_attack)) to line 144, you will see the NaN.
Hi @jinglin80 Thank you very much!
@Yi-Zoey @Nathalie-B This issue is affecting one of the poisoning tools, what do you think?
Hi @jinglin80 I have been able to reproduce your results. At the moment I don't think it is caused by a bug, it looks like a numerical overflow is caused by extremely large activation values for the poison candidate. It looks like you are attacking a global_max_pooling2d
layer which might facilitate the overflow. Have you also observed the issue for other layers?
I notice that sometimes feature collision attack generates poison instances that are NaN. The following is the simplified version of the code, and the parameters are lr = 0.03, similarity = 540, and decay = 0.7:
The NaN output example:
The model used can be downloaded from here.