Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attack Overview with Properties #653

Open
jangop opened this issue Jan 28, 2022 · 4 comments
Open

Attack Overview with Properties #653

jangop opened this issue Jan 28, 2022 · 4 comments

Comments

@jangop
Copy link

jangop commented Jan 28, 2022

The table at foolbox.attacks is currently the closest thing to an overview of all implemented attacks. It could be an ideal place to list major defining properties, such as whether an attack minimizes perturbations and if it supports targeted attacks (or rather, which criteria it supports).

  1. Is it correct that no list with more detail exists?
  2. What other properties should be included?
  3. Could/should the overview be generated automatically, possibly by inspecting which classes (such as MinimizationAttack) a given attack inherits from?
@zimmerrol
Copy link
Member

zimmerrol commented Jan 31, 2022

  1. Yes, this is correct.
  2. I cannot think of any other properties at the moment - but that shouldn't mean that there aren't any. So I'm open to suggestions here:)
  3. Yes, it definitely should be generated automatically since we otherwise have the risk of inconsistencies across different attacks.

@jangop Do you think you can prepare a draft/PR for your suggestion? If so, I would assign the issue to you.

@zimmerrol
Copy link
Member

Is there an update on the status of this idea?

@jangop
Copy link
Author

jangop commented Apr 6, 2022

Yes. Update #1: I have absolutely no idea what I'm doing with sphinx, so it will result in an extra script that will spit out a table to be manually included in the documentation.

@kanak000
Copy link

kanak000 commented Jul 14, 2022

  1. Yes, this is correct.

    1. I cannot think of any other properties at the moment - but that shouldn't mean that there aren't any. So I'm open to suggestions here:)

    2. Yes, it definitely should be generated automatically since we otherwise have the risk of inconsistencies across different attacks.

@jangop Do you think you can prepare a draft/PR for your suggestion? If so, I would assign the issue to you.

hey @jangop , great to see that you were active here in past. Is it possible for you to post one proper Boundary Attack code from foolbox here. If you want i can help you, I am getting some errors while running it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants