I'm ok with that because we are all ready using column, cell, synapse, etc. But for a true cortex we will need thousands, or millions of HTMS linked up :-) Might as well start right now.
Last edit: David Ragazzi 2013-04-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually the Cortex term is also used for reference a specific area of the cortex as whole. Vision area, by example, is called Visual Cortex which is composed by V1, V2.. V6 regions (ok, I now all you know that, but we´re just remembering.. :-) )
So an HTM is a cortex which can be integrated with other cortexs in same way that visual cortex is conected to associative cortex which is conected to auditory cortex, and so on.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Your right. Cortex it is. I will change the class name and soon integrate into the IDE where the current three default regions are set up. I think after that I will add a ticket for a future UI that will allow for arranging an arbitrary number of regions, not just the three we set up now.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
//TODO: need to wire up Cortex and set the input region to the bottom region in the tree
// Under our current setup, the cortex tree would be three regions deep with no sibling nodes
//and 1 to 1 mapping of input / output bits (Region1xy output = region2xy input)
and there's another near Region.GetOutput() by Barry, I guess:
The output data will be a 2d array
/// of dimensions corresponding the column grid for this <see cref="Region">.
/// Note: the Numenta doc suggests the <see cref="Region"> output should potentially
/// include bits for each individual cell.</see></see>
So, we need to consider if there will be any losses if we build feed-froward stream with 1 bit/column output.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I saw Doug already working on that, so I made the ticket
Hi Doug and all,
How about we change the "RegionHierarchy" class name to "Cortex" since that its concept means the own cortex? :-)
David
I'm ok with that because we are all ready using column, cell, synapse, etc. But for a true cortex we will need thousands, or millions of HTMS linked up :-) Might as well start right now.
Last edit: David Ragazzi 2013-04-08
Actually the Cortex term is also used for reference a specific area of the cortex as whole. Vision area, by example, is called Visual Cortex which is composed by V1, V2.. V6 regions (ok, I now all you know that, but we´re just remembering.. :-) )
So an HTM is a cortex which can be integrated with other cortexs in same way that visual cortex is conected to associative cortex which is conected to auditory cortex, and so on.
Your right. Cortex it is. I will change the class name and soon integrate into the IDE where the current three default regions are set up. I think after that I will add a ticket for a future UI that will allow for arranging an arbitrary number of regions, not just the three we set up now.
Hi Doug,
I saw your comment
and there's another near Region.GetOutput() by Barry, I guess:
So, we need to consider if there will be any losses if we build feed-froward stream with 1 bit/column output.
I guess, this is finished. Now we need to connect the hierarchy with IDE features such as GUI and file saving.
Are we closing this?
Last edit: Nick 2013-05-29