-
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
Custom Checkpoint file extension #4963
Comments
Should it be part of the filename? |
Some previous discussion about this: #3163 (comment) |
I agree with @awaelchli, but just need to handle some edge cases (don;t think we should support "." in filenames anway, no?) |
If we define it as propose in the description, all behaviors stay the same for now... And if use overwrite it is, it is his decision and responsibility |
I thought so too, but what if user wants the default filename created by PL but with a different extension? In that case it should be |
well in such case you need to pass the instance of checkpoint call back anyway, so I would fo keeping untouched API inherit it...
so you can later pass |
as you agree with it I have reverted the description to the original one :] |
I'd suggest this one |
Ill happily work on this :) |
🚀 Feature
Atm, we have hardcoded
.ckpt
as a file extension for any checkpoint.https://github.com/PyTorchLightning/pytorch-lightning/blob/db69d169e868451c16a4ee418f2de835ccce146c/pytorch_lightning/callbacks/model_checkpoint.py#L429
Proposed solution 1:
Proposed solution 2:
The text was updated successfully, but these errors were encountered: