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

First review, first issues. #1

Closed
3 tasks done
babsey opened this issue Sep 21, 2020 · 1 comment
Closed
3 tasks done

First review, first issues. #1

babsey opened this issue Sep 21, 2020 · 1 comment

Comments

@babsey
Copy link
Contributor

babsey commented Sep 21, 2020

Hello all,

I am using insite for my project to show a small demo of plotting of spike events.
For all of these issues, I used the develop branch.

docker-compose run
There, I tried setup these containers according to the instruction (https://github.com/VRGroupRWTH/insite/tree/develop).
First I executed this command: docker-compose up --build then I entered the command: docker-compose run insite-nest-module /example/brunel_simulation.py.
It works well but it produces this 500 Internal Server Error, when I call a request of localhost:8080/nest/spikes.
So, I keep starting insite with docker-compose up --build. It works well.

spikes of populations
Next issue, I am able to gather spikes from localhost:8080/nest/spikes. But for different dot colors of spikes in populations, I call ids of spikes localhost:8080/nest/populations, then I want to request spikes for different populations, it returns all spikes instead of the corresponding populations. As example, I called localhost:8080/nest/population/$5104784/spikes.

spikes from specific time
Anyway, I collected all spike but I would like to get spikes of a time window. You implemented from and to arguments.
I assume these arguments set the time window of getting spikes. When I call localhost:8080/nest/spikes?from=50&to=90. It return spikes from 0 to 90. I think to argument works but from argument doesn't.

I summarized these issues:

  • docker-compose run
  • spikes of populations
  • spikes from specific time.
@marcelkrueger
Copy link
Contributor

These issues, should be fixed in the newest versions. Thus, closing this old issue.

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

No branches or pull requests

2 participants