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

Fixes issues #437, #442, #445, #451, #465 #466

Closed
wants to merge 0 commits into from
Closed

Fixes issues #437, #442, #445, #451, #465 #466

wants to merge 0 commits into from

Conversation

appukuttan-shailesh
Copy link
Contributor

This PR fixes issues #437, #442, #445, #451, #465.
Test cases developed for all except #465. Pending implementation of feature in NEST.

@coveralls
Copy link

Coverage Status

Coverage decreased (-8.4%) to 53.498% when pulling 96a569d on appukuttan-shailesh:master into 45f348d on NeuralEnsemble:master.

@apdavison
Copy link
Member

@appukuttan-shailesh Why did you close this?

@coveralls
Copy link

Coverage Status

Coverage decreased (-8.4%) to 53.498% when pulling 3c282ba on appukuttan-shailesh:master into 45f348d on NeuralEnsemble:master.

@appukuttan-shailesh
Copy link
Contributor Author

appukuttan-shailesh commented Mar 17, 2017

@apdavison Was trying to undo commits on my repo (not sure if I needed to); and I think the PR got closed because the corresponding commits were lost?! Have initiated a new PR now.

@apdavison
Copy link
Member

@appukuttan-shailesh oh, I see, the number of commits dropped to zero. In general, you can just push new commits to a branch and the PR will be automatically updated.

So, this PR replaced by #467

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

Successfully merging this pull request may close these issues.

None yet

3 participants