Skip to content
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

Fixed typo in docs for optimizer_idx #5310

Merged
merged 2 commits into from
Dec 31, 2020
Merged

Fixed typo in docs for optimizer_idx #5310

merged 2 commits into from
Dec 31, 2020

Conversation

sugatoray
Copy link
Contributor

@sugatoray sugatoray commented Dec 30, 2020

There were four instances where optimizer_idx was the argument for optimizer_step() under Step optimizers at arbitrary intervals. However, instead of using it what was being used inside (erroneously) was optimizer_i.

Screenshot of Typo

What does this PR do?

This fixes some typos as explained above and in issue #5309.

Before submitting

  • Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
    This was discussed in slack under channel #documentation. Link to discussion
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes [if needed]?
  • Did you write any new necessary tests [no need for typos, docs]? No test needed for typo correction in docs.
  • Did you verify new and existing tests pass locally with your changes? NA: typo correction in docs
  • If you made a notable change (that affects users), did you update the CHANGELOG? NA: typo correction in docs

PR review

Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified
  • Check that target branch and milestone are aligned!

Did you have fun?

Make sure you had fun coding 🙃

There were four instances where `optimizer_idx` was the argument for **`optimizer_step()`** under [Step optimizers at arbitrary intervals][#link-to-docs]. However, instead of using it what was being used inside (erroneously) was `optimizer_i`. 

[#link-to-docs]: https://pytorch-lightning.readthedocs.io/en/latest/optimizers.html#step-optimizers-at-arbitrary-intervals
@Borda Borda added the docs Documentation related label Dec 30, 2020
@Borda Borda added this to the 1.1.x milestone Dec 30, 2020
@Borda Borda self-assigned this Dec 30, 2020
@codecov
Copy link

codecov bot commented Dec 30, 2020

Codecov Report

Merging #5310 (0ba134c) into master (4913cbb) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #5310   +/-   ##
======================================
  Coverage      93%     93%           
======================================
  Files         134     134           
  Lines        9950    9950           
======================================
  Hits         9261    9261           
  Misses        689     689           

@s-rog s-rog merged commit dd98a60 into Lightning-AI:master Dec 31, 2020
@s-rog s-rog linked an issue Dec 31, 2020 that may be closed by this pull request
Borda pushed a commit that referenced this pull request Jan 6, 2021
There were four instances where `optimizer_idx` was the argument for **`optimizer_step()`** under [Step optimizers at arbitrary intervals][#link-to-docs]. However, instead of using it what was being used inside (erroneously) was `optimizer_i`.

[#link-to-docs]: https://pytorch-lightning.readthedocs.io/en/latest/optimizers.html#step-optimizers-at-arbitrary-intervals

(cherry picked from commit dd98a60)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Typo correction in optimizers documentation
5 participants