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

cudnn.deterministic been set while import, suggestion to avoid this kind of behavior #4117

Closed
mstczuo opened this issue Aug 27, 2021 · 3 comments
Assignees

Comments

@mstczuo
Copy link
Contributor

mstczuo commented Aug 27, 2021

torch.backends.cudnn.deterministic = True

This line of code executes when someone just import nni.algorithms.compression.pytorch.pruning, I suggest to move it into the constructor function of AMCPruner and reset cudnn.deterministic after training because it changed an import setting but does not tell the user.

@mstczuo mstczuo changed the title cudnn.deterministic being set while import, suggestion to avoid this kind of behavior cudnn.deterministic been set while import, suggestion to avoid this kind of behavior Aug 27, 2021
@scarlett2018
Copy link
Member

@mstczuo - would you like to submit a PR for the suggestion? thanks.

@mstczuo
Copy link
Contributor Author

mstczuo commented Sep 1, 2021

@mstczuo - would you like to submit a PR for the suggestion? thanks.

sure. I have submitted this PR: #4139

@mstczuo
Copy link
Contributor Author

mstczuo commented Sep 8, 2021

PR #4161 solved this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants