Fix the nonlinear bug and add mnist example #110
Merged
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.
Add one more step in the nonlinear encoding: normalize the weight, which is similar to the random projection case.
To test it, I create a
mnist_nonlinear.py
in the examples.Without this normalization, the accuracy of running
python mnist_nonlinear.py
is 10.75%.After adding this normalization, the accuracy becomes 83.93%.
Another example that justify this change is in the
random_projection.py
example:This encoding function is doing nothing but first a random projection and then passing through the nonlinear encoding.
Since in the random projection, the weight has been normalized; thus in the nonlinear encoding, the weight should also be normalized.
Please let me know if you have any questions or concerns.