You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The implementation relies on in-place modification of the momentum variable as a side effect, which doesn't always seem to work as expected (see [FIX Enhancement] FGM and PGD: fix L1 and extend to Lp #2382 (comment)). As such, I believe that the current momentum iterative attack is actually only BIM!
The first issue should be fixed by #2382, while the second should be independently investigated and fixed, as it may require some refactoring. Furthermore, it could be well-advised to add a test for a different decay value.
Edit:It looks like the tensorflow framework doesn't work with the in-place modification.
The text was updated successfully, but these errors were encountered:
eliegoudout
changed the title
Attack > Evasion > BIM: Momentum issues
Attack > Evasion > Momentum Iterative Method: major issues
Apr 27, 2024
Stumbled upon 2 issues regarding the implementation of the momentum for Fast Gradient Method adversarial attack:
FGM
andPGD
: fix L1 and extend to Lp #2382 (comment));momentum
variable as a side effect, which doesn't always seem to work as expected (see [FIX Enhancement]FGM
andPGD
: fix L1 and extend to Lp #2382 (comment)). As such, I believe that the current momentum iterative attack is actually only BIM!The first issue should be fixed by #2382, while the second should be independently investigated and fixed, as it may require some refactoring. Furthermore, it could be well-advised to add a test for a different decay value.
Edit: It looks like the tensorflow framework doesn't work with the in-place modification.
The text was updated successfully, but these errors were encountered: