[docs] added num_directions explanation to docstrings#10786
Closed
rohan-varma wants to merge 1 commit intopytorch:masterfrom
Closed
[docs] added num_directions explanation to docstrings#10786rohan-varma wants to merge 1 commit intopytorch:masterfrom
rohan-varma wants to merge 1 commit intopytorch:masterfrom
Conversation
zou3519
reviewed
Aug 22, 2018
| :func:`torch.nn.utils.rnn.pack_sequence` for details. | ||
| - **h_0** of shape `(num_layers * num_directions, batch, hidden_size)`: tensor | ||
| containing the initial hidden state for each element in the batch. | ||
| If the RNN is bidirectional, num_directions should be 2, else it should be 1. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
zou3519
approved these changes
Aug 22, 2018
Contributor
Author
|
@pytorchbot test this please |
Contributor
|
@pytorchbot retest this please |
Contributor
facebook-github-bot
left a comment
There was a problem hiding this comment.
zou3519 has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
PenghuiCheng
pushed a commit
to PenghuiCheng/pytorch
that referenced
this pull request
Sep 11, 2018
Summary: Resolving [https://github.com/pytorch/pytorch/issues/10741](https://github.com/pytorch/pytorch/issues/10741). The current docs use `num_directions` quite a bit, without any explanation for them. `num_directions` is set to 2 if the RNN is bidirectional, or 1 otherwise. This change simply adds that to the docs. Pull Request resolved: pytorch#10786 Differential Revision: D9480235 Pulled By: zou3519 fbshipit-source-id: f61d1b0d2b943f84d5b7ff83df6fe0965a508a5e
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolving #10741. The current docs use
num_directionsquite a bit, without any explanation for them.num_directionsis set to 2 if the RNN is bidirectional, or 1 otherwise. This change simply adds that to the docs.