If you create a weight update component with in impulse input, rather than an event input, then you can't put it into a projection - the compilation fails:
[seb@seb-T460s 08:39:37 0]$ ./build
component.cpp: In member function ‘virtual brahms::Symbol dev_spineml_wu_ConnectionListImpulseWeight_0::event(brahms::Event*)’:
component.cpp:659:7: error: ‘delayedImpulseVals’ was not declared in this scope
delayedImpulseVals[(delayBufferIndex+delayForConn[DATAin[i_BRAHMS_LOOP][j
^
component.cpp:681:23: error: ‘delayedImpulseVals’ was not declared in this scope
in[num_BRAHMS] = delayedImpulseVals[delayBufferIndex][i_BRAHMS];
^
component.cpp:707:5: error: ‘delayedImpulseVals’ was not declared in this scope
delayedImpulseVals[delayBufferIndex].clear();
^
Assuming an impulse input to a weight update component is permitted by SpineML, then this should be fairly easy to resolve.
If you create a weight update component with in impulse input, rather than an event input, then you can't put it into a projection - the compilation fails:
Assuming an impulse input to a weight update component is permitted by SpineML, then this should be fairly easy to resolve.