This repository was archived by the owner on May 13, 2025. It is now read-only.
use set_() instead of setting .data directly #112
Closed
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.
Types of changes
Motivation and Context / Related issue
There is an issue with setting a torch tensor using the
.data
attribute here and here, those lines are throwing anAttributeError: can't set attribute
. My use-case uses PySyft which might be the cause of throwing that error but I believe that using.set_
instead won't affect the current implementation. I got the fix from a related issue pytorch/pytorch#30987How Has This Been Tested (if it applies)
A complete training of the same model in Tutorial7.
Checklist