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

Don't optimize one thing but measure another #17

Open
anishathalye opened this issue Mar 1, 2019 · 0 comments
Open

Don't optimize one thing but measure another #17

anishathalye opened this issue Mar 1, 2019 · 0 comments

Comments

@anishathalye
Copy link
Collaborator

I've seen this in a fair number of papers recently, where one quantity is optimized and another is measured.

Examples of this mismatch include:

  • conducting targeted attacks but measuring model accuracy (rather than success rate)
  • conducting untargeted attacks to change top-1 classification but measuring top-5 accuracy

A related issue includes comparing two attacks that are not directly comparable, for example:

  • conducting targeted attacks with (target = least likely class) and measuring accuracy, and comparing with prior work's results with accuracy on attacks of the form (target = random class)

It might be nice to include some text on this topic. Thoughts?

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

No branches or pull requests

1 participant