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

frame saliency #942

Merged
merged 4 commits into from
Nov 18, 2020
Merged

frame saliency #942

merged 4 commits into from
Nov 18, 2020

Conversation

davidslater
Copy link
Contributor

No description provided.

@lcadalzo lcadalzo self-assigned this Nov 17, 2020
@lcadalzo
Copy link
Contributor

After briefly looking through the attack paper, it seems like applying this to the Ucf101 scenario might be more fitting?

@lcadalzo
Copy link
Contributor

added a config for this. If I'm missing context though and there's a reason resisc was chosen, I'll delete. If not, and the purpose is simply to show an example usage of the attack, I think we can delete the resisc config

@davidslater
Copy link
Contributor Author

Yeah, that makes sense. I was just doing a simple test and didn't want to incur video compute costs.

@davidslater
Copy link
Contributor Author

If you're good, go ahead and merge.

@lcadalzo
Copy link
Contributor

I'm going to remove the resisc frame saliency config since I assume we don't need two examples, and the attack is more relevant for ucf

Copy link
Contributor

@lcadalzo lcadalzo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lcadalzo lcadalzo merged commit d9f1c35 into twosixlabs:master Nov 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants