Skip to content
This repository has been archived by the owner on Sep 1, 2023. It is now read-only.

SpatialPooler initialization with constructor vs initialize() results in different SP state #1386

Closed
breznak opened this issue Jan 12, 2018 · 0 comments · May be fixed by htm-community/htm.core#5
Closed

SpatialPooler initialization with constructor vs initialize() results in different SP state #1386

breznak opened this issue Jan 12, 2018 · 0 comments · May be fixed by htm-community/htm.core#5
Labels
subject:algorithms type:bug

Comments

@breznak
Copy link
Member

breznak commented Jan 12, 2018

No description provided.

@breznak breznak mentioned this issue Jan 12, 2018
Closed
2 tasks
@breznak breznak mentioned this issue Jan 19, 2018
Open
1 task
lscheinkman added a commit to lscheinkman/nupic.core-legacy that referenced this issue Feb 9, 2018
@lscheinkman
NUP-2492: Add constructor vs initialize test regarding Issue numenta#…
70d43da 
…1386
@lscheinkman lscheinkman mentioned this issue Feb 9, 2018
Merged
lscheinkman added a commit that referenced this issue Feb 9, 2018
@lscheinkman
Merge pull request #1397 from lscheinkman/NUP-2492
8343255 
NUP-2492: Add constructor vs initialize test regarding Issue #1386
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
subject:algorithms type:bug
Projects
None yet
Milestone
No milestone
1 participant
@breznak