#189 Add unpatch for dropout and consistent dropout #194
Conversation
This file contains 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
parmidaatg
approved these changes
Mar 18, 2022
|
|
||
| def forward(self, *args, **kwargs): | ||
| return self.parent_module.forward(*args, **kwargs) | ||
|
|
||
| def unpatch(self) -> torch.nn.Module: | ||
| return unpatch_module(self.parent_module) |
There was a problem hiding this comment.
this will make sure that self.parent_module is always patched but at every step the user can ask for an unpatched version right? its very useful just wanna make sure that if you call unpatch the internal module remains patched.
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary:
Add ability to unpatch modules to Dropout and Consistent dropout.
Not yet available for dropconnect as it is a bit more complicated.
Features:
WIP on #189
Checklist:
tests/documentation_test.py).