forked from numenta/nupic.core-legacy
-
Notifications
You must be signed in to change notification settings - Fork 82
SDRClassifier: fix precision by using Real64 for PDF #667
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
Merged
Merged
Changes from 4 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
ccf7e10
SDRClassifier: fix precision by using Real64 for PDF
breznak d437a6a
Classifier: more fixes
breznak d34d0cd
Classifier: make infer const
breznak bf5123b
Predictor: make infer const
breznak 2609617
Merge branch 'master_community' into predictor_precision_fix
breznak 22d6664
review: formatting
breznak 4fd8fbb
Merge branch 'master_community' into predictor_precision_fix
breznak 767f89a
Merge branch 'master_community' into predictor_precision_fix
breznak 2aedac2
Predictor: use hashmap
breznak 4d8708d
Classifier: simplify asserts
breznak df7ae4e
Predictor: remove numRecord arg, fixes
breznak File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ctrl-z-9000-times please have a look on the last 1,(2) commits, I intended to make
inferconst, as it imho should have been. For Classifier that was easy, for Predictor I had to remove theupdateHistory_from infer (no tests visibly broken).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does it matter if infer is constant? I doubt it will have any performance impact, and I don't think this will prevent any programming mistakes.
Consider the following chain of events:
The method
updateHistorystores the given SDR inside of the predictor. Previously the call tolearnwould have associatedSDR-AwithLabelssince that SDR was given to infer with. Now that will not happen.Also, these changes allow the timestamps to the infer method to go backwards.
I'm not saying the new behavior is wrong, just that it changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right, there won't be any performance gains, and the behavior has changed. I think it adds (expected) semantics, and better separates responsibilities of those 2 functions:
learn()infer() constanytime without any worry of changing the state (comes with loosened requirement for monotonic timestamps)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, that makes sense +1