-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Bugfix/4156 filter hparams for yaml - fsspec #4158
Conversation
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.
Nice! Does this mean we could do self.save_hyperparameters()
by default now?
Codecov Report
@@ Coverage Diff @@
## master #4158 +/- ##
======================================
Coverage 93% 93%
======================================
Files 103 103
Lines 7805 7813 +8
======================================
+ Hits 7239 7247 +8
Misses 566 566 |
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.
Great PR ! Would you mind adding support for numpy array and tensors conversion to list ?
hparams_allowed = {} | ||
# drop paramaters which contain some strange datatypes as fsspec | ||
for k, v in hparams.items(): | ||
try: |
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.
Hey @Borda, I was wondering if it makes sense to force dumping to yaml file. It might break reproducibility for some use cases. But for the yaml format, we could also support some conversion like: tensor and numpy array to list, etc...
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.
so how else would you test that some value/data are not possible to dum, I have not found any method like is_dumpable
and most examples use this construct...
This pull request is now in conflict... :( |
Co-authored-by: Justus Schock <[email protected]>
839e655
to
75a2134
Compare
What does this PR do?
Fixes #4156
BTW, this is needed for unblocking Bolts
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃