This repository has been archived by the owner on Nov 22, 2022. It is now read-only.
Avoid edge cases with quantization by setting a known seed #1295
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: Stress test reveals some cases where the model returns NaN (https://our.intern.facebook.com/intern/testinfra/diagnostics/3377699742969609.844424947441516.1585199924/). My guess is that some initializations play badly with quantization, so forcing a known seed to try and fix it.
Differential Revision: D20673784