-
Notifications
You must be signed in to change notification settings - Fork 17
[hydra-configs-torch] torch1.6 data configs #44
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
Conversation
One other change in this PR: I've moved the configen source confs to include separate folders per project.
->
It might be better if these were just |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm.
There was also the problem with the missing type annotation you encountered, right?
can you also file an issue for that one?
data.IterableDataset(), | ||
id="IterableDatasetConf", | ||
), | ||
# TODO: investigate asterisk in signature instantiation limitation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you file an issue on the repo so we don't lost track?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You saw the rest of the issues, but here:
facebookresearch/hydra#1243
Will get the minimal repro for this one. The others, once we nail them down, we can get minimal repros for those as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a chance that this will one will be difficult to solve. Let's assume we need a workaround.
Adds configs for
Dataset
variants andSampler
variants.Adds tests for all configs except:
TensorDatasetConf
andDistributedSamplerConf
.The former has a funny issue with instantiation due to the asterisk in it's signature which I'm investigating. The latter requires setting up a distributed env to test instantiation. Not sure about the cleanest way to automate this test yet.
Addresses: #1, #45