-
Notifications
You must be signed in to change notification settings - Fork 9
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
Connection of ports between any Components #46
Comments
Would this be the same as a |
Ah, I see the connection is onto the synapse. Could we perhaps allow |
I would be against this, as it becomes an unimplementable nightmare if a On 26 March 2015 at 05:39, Tom Close notifications@github.com wrote:
Alex Cope |
As long as there aren't circular references (which of would have to be invalid) it shouldn't be too difficult to resolve should it? I agree that it is a little messy but then what you are asking to be able to do is a bit out there in terms of typical models. |
The Committee decided that the solution to this issue and additionally to the issue of Hierarchical Components is a NineML Core comprising only the simplest network primitives. These are: ComponentArray: <ComponentArray name="">
<Size>X</Size>
<Prototype>
<Reference url="">AComponentName</Reference>
</Prototype>
</ComponentArray> ConnectionGroup: <ConnectionGroup>
<Terminus>
<Reference>AComponentArrayName</Reference>
<AnalogPortConnection sender="APort" receiver="AnotherPort"/>
<EventPortConnection sender="BPort" receiver="BnotherPort"/>
</Terminus>
<Terminus>
<Reference>AnotherOrTheSameComponentArray</Reference>
<AnalogPortConnection sender="APort2" receiver="AnotherPort2"/>
<EventPortConnection sender="BPort2" receiver="BnotherPort2"/>
</Terminus>
<ConnectionList>
<One of ExplicitList, OneToOne or AllToAll (see issue #72)>
</ConnectionList>
</ConnectionGroup> |
In the above example we decided to use |
I some circumstances it is useful to connect ports between any pairs of Components. One example is a Dopamine source that is global to the model, but can influence plasticity in several synapses.
Do we want this? It will make implementation more difficult...
The text was updated successfully, but these errors were encountered: