-
Notifications
You must be signed in to change notification settings - Fork 2
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
basic dataset #5
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
It looks like what we'd need to do is convert the dictconf into the dataclasses using https://omegaconf.readthedocs.io/en/latest/usage.html#omegaconf-to-object ? |
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.
Thanks for this PR. It cool that it can run !I've made small remarks.
For optimizer I don't understand why there is a duplicate.
About the type checking. How can we do type checking for data augmentation with hydra dataclasses ?
- task: ??? | ||
- models: ??? | ||
- data: ??? | ||
defaults: # loads default configs |
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.
Ok for now. Maybe in the future, we will change this to have multiple optimizers.
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.
I agree, eventually we should change the optimizer to be part of the model
package.
Btw I got this error:
|
for more information, see https://pre-commit.ci
That's strange about the error, can you send a stack trace? |
@humanpose1 let me know what you think... it's very crude but it at least runs.
Right now it will instantiate the s3dis1x1 dataset.
You can try running it with
python train.py model=default dataset=segmentation/s3dis/s3dis1x1.yaml
I think the first thing we should figure out is how to properly implement static typechecking for the configs (#4) or just abandon the
DataConfig
. It looks like pytorch lightning transformers implemented the dataconfig but didn't actually make it do any type checking...