-
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
rename variables nb -> num #567
Conversation
@elliotwaite could you have look on this (proposed) changes... |
@Borda all of these changes need to be backward compatible though |
for that, I am not sure how to handle multiple methods with the same name just with changed parameter name... adding the past parameter name will crash while passing parameters with values only... :/ https://stackoverflow.com/questions/5079609/methods-with-the-same-name-in-one-class-in-python |
@williamFalcon it seems that method overloading will make it even worse... |
@Borda
|
@@ -31,7 +31,7 @@ def main(hparams): | |||
# ------------------------ | |||
trainer = Trainer( | |||
gpus=2, | |||
nb_gpu_nodes=2, | |||
num_gpu_nodes=2, |
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.
maybe shorten to:
num_nodes?
@@ -234,7 +234,7 @@ def main(hparams): | |||
trainer = pl.Trainer( | |||
default_save_path=hparams.save_path, | |||
gpus=hparams.gpus, | |||
max_nb_epochs=hparams.epochs, | |||
max_num_epochs=hparams.epochs, |
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.
add backward compatibility
not sure i follow. class A is lightningModule. B is the subclass |
I just do not understand what you suggest, adding subclass of |
changing def training_step(self, batch, batch_nb): to def training_step(self, batch, batch_idx): does not affect the user |
@Borda rebase? |
@williamFalcon done :] |
What does this PR do?
PARTIAL Fixes #534.
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.