vrgrouprwth / insite Goto Github PK

When the simulation is finished and the frontend requests the last frame from access node.
The lastFrame indicates that there is no further data after this request.
But the lastFrame seems not working correctly. It only shows false.

The time based filtering for spikes does not work. Even if to and from parameter are provided the returned spikes are always all the spikes that are in the ring buffer.

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.

Expose NEST server in the docker build such that both the Insite access node and NEST server are reachable from outside

List of NEST & Insite properties/metrics that would be useful to query via Insite:

• Ringbuffer of population rates
• memory usage
• CPU usage
• power usage
• spikes per process (current load of communication structure)
• pyNest timers (duration last communication step, ...)

Currently the data in the ring buffer isn't reset between new simulations. Thus, data from older runs are still available in the new run.

What has to be configurable:

So far:

• Access Node Port
• Ring Buffer Size