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

NuPIC Needs Integration Test Illustrating Correct Output To Use #2684

Open
cogmission opened this Issue Oct 20, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@cogmission
Contributor

cogmission commented Oct 20, 2015

@rhyolight @subutai @scottpurdy @chetan51 @breznak

There needs to be an example developers can refer to which illustrates how interaction between the algorithms is accomplished.

This issue author is proof of that need.

Being the most official porter of NuPIC code, and therefore the most objective test for correct interpretation of NuPIC, the fact that I had no reference and mistakenly used the incorrect output when utilizing and implementing the interaction between algorithms - is proof of this need.

  • The test should show getting data from Encoders, SpatialPoolers, TemporalMemories, Classifiers, Anomaly(s), AnomalyLikelihood(s) and feeding that data into the appropriate subsequent algorithm or algorithm(s) in the case where output can be sent into multiple subsequent algorithm types.
@breznak

This comment has been minimized.

Member

breznak commented Oct 20, 2015

👍 I've burned my fingers when getting some TP output and passing it manually to Anomaly!

  • this could be an example as well, instead of a i-test.
  • I'd like to point out to #2536 which got kindof stalled, this would be one of the usecases.
@cogmission

This comment has been minimized.

Contributor

cogmission commented Oct 20, 2015

@breznak I agree, however I think that mentioning that here may be distracting. It's probably better to mention this Issue from #2536 rather than have a discussion of that here. This issue should probably remain pure so that it doesn't get coopted by off-topic conversation (as I have been guilty of doing too!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment