Enable specifying of margin in HingeEmbeddingLoss#1378
Merged
soumith merged 1 commit intopytorch:masterfrom Apr 28, 2017
macaodha:patch-1
Merged
Enable specifying of margin in HingeEmbeddingLoss#1378soumith merged 1 commit intopytorch:masterfrom macaodha:patch-1
soumith merged 1 commit intopytorch:masterfrom
macaodha:patch-1
Conversation
Previously it was not possible to set a value for the margin in the HingeEmbeddingLoss in the constructor. This patch fixes the issue and makes the loss behave as it is described in the docs. A discussion of this issue can be viewed here: https://discuss.pytorch.org/t/issue-with-setting-margin-for-hingeembeddingloss/2088
soumith
approved these changes
Apr 28, 2017
Collaborator
|
thanks for fixing this! |
Member
|
Hi,
|
Contributor
Author
|
I can look into this. Do we also need to add |
Contributor
|
Yes, they should all use it |
Jiaming-Liu
pushed a commit
to Jiaming-Liu/pytorch
that referenced
this pull request
May 18, 2017
Previously it was not possible to set a value for the margin in the HingeEmbeddingLoss in the constructor. This patch fixes the issue and makes the loss behave as it is described in the docs. A discussion of this issue can be viewed here: https://discuss.pytorch.org/t/issue-with-setting-margin-for-hingeembeddingloss/2088
jjsjann123
added a commit
to jjsjann123/pytorch
that referenced
this pull request
Jan 26, 2022
1. extend buildShapeExpression for squeeze_copy/unsqueeze_copy ops. 2. patching broadcastSizes insertion point for buildShapeExpression to avoid graph::copy() linter assert. 3. adding tests 4. supports no-op squeeze (squeezing on dimension that's not size-1) TODO (in follow up PRs): 1. extend buildShapeExpression to view_copy and reshape_copy as well 2. refactor broadcastSizesExpression to allow graceful failure instead of hard assert
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
5 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.
Previously it was not possible to set a value for the margin in the HingeEmbeddingLoss in the constructor. This patch fixes the issue and makes the loss behave as it is described in the docs.
A discussion of this issue can be viewed here:
https://discuss.pytorch.org/t/issue-with-setting-margin-for-hingeembeddingloss/2088