Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New Benchmark Config and Benchmark script
Run Groups
For each model, you can specify any number of 'run groups' with a unique group id. Each run group allows you to specific a set of hyperparams to run the model with.
You can also include/exclude attacks, customize if they will be shown on the final benchmark graph etc.
Hyperparameters
Each hparams config is a dictionary where keys are json access paths in the base config of the model, and the value is an array of potential hparam values.
The cartesian product of hparam values is calculated and a model will be run on each. For K hparams, we will run N_0 * ... * N_K models where N_i is the length
of the values array for hparam i.
Attacks:
Which attacks to run on which defense can be configured using attack settings. These consist of
include
,exclude
and a special@all
token.Attacks can be included/excluded globally, per model, and per run group
Benchmark Config Fields:
TODOS: