Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #261 I had some questions about why a
spike is None
condition was necessary. In investigating that, I started refactoringAxon
to reduce the number of ways you could misuse it, as currently it requires you to construct it, then set thetarget
outside of theAxon
constructor, and then callset_compartment_axon_map
, and if you don't do one of those steps it will either fail or give you undocumented behavior.While I was able to alleviate those concerns, when I tired to remove the possibility of returning
None
instead of a spike it became obvious that several classes insideblock.py
have similar assumptions, and so several unit tests were failing (despite many integration tests passing). This made me think that there are likely several more issues in how the classes inblock.py
are designed versus how they are actually used in Nengo Loihi, and that seemed outside of the scope of the original issue, so I stopped there. We can pick up this refactoring later if we want.