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

clean v2 docs #691

Merged
merged 87 commits into from
Jan 17, 2020
Merged

clean v2 docs #691

merged 87 commits into from
Jan 17, 2020

Conversation

williamFalcon
Copy link
Contributor

Copy link
Member

@Borda Borda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be a bit more specific...

@@ -14,6 +14,8 @@ tests/save_dir
default/
lightning_logs/
tests/tests/
*.rst
/docs/source/*.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just thinking about making the copy of the github pages to a sub-folder so then we we can write the ignore more specific...

@@ -14,6 +14,8 @@ tests/save_dir
default/
lightning_logs/
tests/tests/
*.rst
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather write

pl_examples.rst
pl_examples.*.rst
pytorch_lightning.rst
pytorch_lightning.*.rst

@williamFalcon williamFalcon changed the title updated gitignore [WIP] clean v2 docs [WIP] Jan 15, 2020
@Borda
Copy link
Member

Borda commented Jan 16, 2020

Pls could you rebase it on #685 since this is a kind of follow-up and check #687

@Borda Borda added this to the 0.6.0 milestone Jan 16, 2020
Copy link
Member

@Borda Borda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what docs style are we going to use?

verbose: verbosity mode, 0 or 1.
save_top_k: if `save_top_k == k`,
r"""

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rather start just after """

training will stop when the quantity
monitored has stopped decreasing; in `max`
mode it will stop when the quantity
monitored has stopped increasing; in `auto`
mode, the direction is automatically inferred
from the name of the monitored quantity.

Example:
>>> from pytorch_lightning import Trainer
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pls remove >>> or keep it and shift left so it become a doctest

>>> # save epoch and val_loss in name
>>> ModelCheckpoint(filepath='{epoch:02d}-{val_loss:.2f}.hdf5')
>>> # saves file like: /path/epoch_2-val_loss_0.2.hdf5
monitor (str): quantity to monitor.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shall decide what kind of documentation we are going to use...
https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html

@@ -1,3 +1,14 @@
"""
The LightningModule is the "system recipe." It groups the following in one file:
- computational system definition
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that it needs a blank line to be treated as a list, be aware that reStructuredText and MarkDown formatting is a bit different...
http://www.unexpected-vortices.com/doc-notes/markdown-and-rest-compared.html

williamFalcon and others added 8 commits January 16, 2020 06:04
* flake8

* fix typo

* fix tensorboardlogger
drop test_tube dependence

* formatting

* fix tensorboard & tests

* upgrade Tensorboard

* test formatting separately

* try to fix JIT issue

* add tests for 1.4
@williamFalcon williamFalcon changed the title clean v2 docs [WIP] clean v2 docs Jan 17, 2020
@williamFalcon
Copy link
Contributor Author

@Borda ready for review!
These aren't 100% where I think they should be but I propose the following:

  1. merge asap
  2. deploy to docs url
  3. work on examples, tutorials and common use cases over the next few days. Some of those are because I'm not super familiar with this formatting for those sections.

@williamFalcon williamFalcon merged commit bc67689 into master Jan 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants