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

Rename TemporalMemory extra to externalPredictiveInputs #519

Merged
merged 3 commits into from
Jun 20, 2019

Conversation

ctrl-z-9000-times
Copy link
Collaborator

There was confusion about what this feature does so I renamed it
for clarity.

See also issue #512.

There was confusion about what this feature does so I renamed it
for clarity.
breznak
breznak previously approved these changes Jun 18, 2019
Copy link
Member

@breznak breznak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks!
Consider some more details for the description..?

src/htm/algorithms/TemporalMemory.hpp Show resolved Hide resolved
Copy link
Member

@breznak breznak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Improved doc and clearer code is always the best!
Thanks

@@ -99,6 +99,11 @@ class TemporalMemory : public Serializable
* @param predictedSegmentDecrement
* Amount by which segments are punished for incorrect predictions.
*
* Note: A good value is just a bit larger than
* (the column-level sparsity * permanenceIncrement). So, if column-level
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OT: #279 it would be nice to reduce the number of parameters for the algorithms, especially in cases like this where a good-enough value can be derived from other settings. Do you think this would be a reasonable candidate to hard-code?
Pros:

  • less space for user to mess up
  • faster parm optimizations
    Cons:
  • removes a bit of configurability

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, but here are two more potential issues:

  1. Is this advice always good? I think it would need further investigation before we remove the parameter in favor of this heuristic.
  2. We would have to modify every instance of the TM to omit this parameter. It would be a lot of work.

@breznak breznak merged commit 81902c0 into master Jun 20, 2019
@breznak breznak deleted the rename-tm-extra branch June 20, 2019 06:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants