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

Consider removal of destroySegment #574

Open
breznak opened this issue Jul 18, 2019 · 0 comments
Open

Consider removal of destroySegment #574

breznak opened this issue Jul 18, 2019 · 0 comments
Labels
code code enhancement, optimization, cleanup..programmer stuff question Further information is requested

Comments

@breznak
Copy link
Member

breznak commented Jul 18, 2019

Off Topic: I think that the HTM would work just as well if we never allowed for destroying segments (untested). Instead of destroying segments just remove all of the synapses. The use-case for destroying segments is when the TM is full and you want to add a new thing to it. In this situation, the destroyed segment will immediately recreated with different synapses. This would allow us to get rid of the segmentOrdinals and segment.id ~ @ctrl-z-9000-times

A thing to try, would be nice simplification of the code.

From #537 , related #161

@breznak breznak added question Further information is requested code code enhancement, optimization, cleanup..programmer stuff labels Jul 18, 2019
@breznak breznak mentioned this issue Jul 18, 2019
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code code enhancement, optimization, cleanup..programmer stuff question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant