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

Impulse ports #93

Open
mondus opened this issue Apr 1, 2015 · 1 comment
Open

Impulse ports #93

mondus opened this issue Apr 1, 2015 · 1 comment

Comments

@mondus
Copy link

mondus commented Apr 1, 2015

The current version 1 spec does not support impulse ports (as defined in SpineML). Previously this was assumed to be supported via a coupled event and analogue port however this is syntactically unclear.

A suggestion is that we should either support impulse ports (an event with a payload value) or alternatively events should support an optional payload value.

@NineML-Committee
Copy link
Contributor

The committee decided that the addition of one or multiple values to events should be supported as an option for event ports.

Example

<EventSendPort name="MyEventPort">
 <ValueSend name="srcname" source="mySV_par_or_Alias_or_OutputAnalog"/>
 <ValueSend .../>
</EventSendPort>

<EventReceivePort name="MyEventPort">
 <ValueReceive name="dstname" unit=""/>
 <ValueReceive .../>
</EventSendPort>

<PortConnection source="" destination="">
 <ValueConnection source="srcname" destination="dstname"/>
 <ValueConnection .../>
</PortConnection>

The ValueReceive named variables are only valid in the scope of the corresponding OnEvent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants