-
Notifications
You must be signed in to change notification settings - Fork 48
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
Add Mini Well #15
Comments
That seems reasonable - I think we'd want it to function like a secondary Well path so if the mini flag is the only difference that seems like a good option. Maybe we'd want to add a "are you sure?" prompt with an explanation in case people accidentally elect to overwrite the full path which would be pretty painful. Although then maybe the better option would be to inherently write to a "mini" directory so that someone would really have to work to overwrite the full well. |
That sounds like a good idea! Like we just modify |
Actually maybe something better is we just modify all the dataset names? Like |
Yeah, I like that actually. We'd just want to make sure anything that's parsing the registry would know the difference, but that might be the safest option and also help avoid mistakes where someone is benchmarking on mini and thinks they're on full. |
I'm in favor of adding
|
This is a to-do item to add the "mini well" dataset. It's already generated on my user account; we just need to put it somewhere it can be downloaded.
Q: @rubenohana @LTMeyer @mikemccabe210 do you have a preferred API design for this? Perhaps the easiest is:
where the
--mini
flag would enable the mini versions instead.I suppose it should also be available on HF datasets since it's only 5 GB total?
The text was updated successfully, but these errors were encountered: