You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2020. It is now read-only.
The idea here is to get rid of the bizarre global variables that serve to associate some sort of information with a particular node in the network. In particular, we have
That would be an option, but I don't think there's a decision yet as to what net.get('name') should return. Basically, if we include net.get() as part of our API, then we have to define an API for what functions are expected to be callable on that returned object, regardless of whether we're using the Java or Theano or whatever version. Personally, I'd prefer to not have net.get() and to not have net.make* return anything at all. But that's a whole other discussion. :)
The idea here is to get rid of the bizarre global variables that serve to associate some sort of information with a particular node in the network. In particular, we have
hrr.Vocabulary.registered
timeview.watches.FuncRepWatchConfig.config
which can both grow without bound, and have no way of removing elements when a network is closed.
This capability would also be able to get rid of the setDocumentation abuse that happens in spa.bg and spa.thalamus
Another use case is storing the x/y/z location of a node
This system should also have an interface to the nef API, allowing something like:
The text was updated successfully, but these errors were encountered: