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

Sweep MVP #191

Merged
merged 7 commits into from
Apr 16, 2023
Merged

Sweep MVP #191

merged 7 commits into from
Apr 16, 2023

Conversation

norabelrose
Copy link
Member

You can now do stuff like
elk sweep --models gpt2 gpt2-medium gpt2-large gpt2-xl --datasets imdb amazon_polarity
and it'll run elicit on the Cartesian product of the models and datasets you list, storing it in a special folder ELK_DIR/sweeps/<memorable_name>.

Copy link
Collaborator

@lauritowal lauritowal left a comment

Choose a reason for hiding this comment

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

Looks good to me.
Although, don't we also want transfer evaluations e.g. gpt2 trained on imdb, but evaluated on ag_news and vice versa? Could be another task / pull-request for later...

@norabelrose
Copy link
Member Author

Looks good to me.

Although, don't we also want transfer evaluations e.g. gpt2 trained on imdb, but evaluated on ag_news and vice versa? Could be another task / pull-request for later...

Yeah we can add eval in the next PR. Also can you use bash brace expansion in the README example so that people know you can use it? For example
--models gpt2-{tiny,medium,large,xl}. This is just the shell expanding things out for you, I didn't have to write any code for it, but it's really convenient.

@norabelrose
Copy link
Member Author

Another thing for the next PR is probably to add like --config-path foo.yaml or some way of specifying nondefault hparams that are shared across the sweep

@norabelrose norabelrose merged commit 691d314 into main Apr 16, 2023
4 checks passed
@norabelrose norabelrose deleted the sweep branch April 16, 2023 17:54
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

Successfully merging this pull request may close these issues.

None yet

2 participants