-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fix OPF prediction models #3665
Conversation
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.
I had one comment, otherwise 👍 💯.
src/nupic/regions/record_sensor.py
Outdated
description="The field to be predicted. This will result in the " | ||
"outputs actValueOut and bucketIdxOut not being " | ||
"populated.", | ||
dataType="Byte", |
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.
The dataType
is confusing because it's a string. Should the description say "The field name to be predicted..."?
@rhyolight - Added a major commit that removes the CLAClassifier and derivatives. Tests for CLAClassifier are removed but other usages are replaced with the SDRClassifier. |
Great, assuming you get tests passing, LTGM. |
I'm going to wait until #3669 is merged, revalidate this PR, and then merge. |
This changes "predictedFieldIdx" to just "predictedField" so network clients don't have to try to figure out the index of the predicted field (which may vary based on the dataSource in the encoder). Additionally, missing links for the HTMPredictionModel classifier are added to fix broken prediction capability.
@ywcui1990 - fyi, not sure if this conflicts with your changes
fixes NUP-2448