[CLOSED] Quick start guide for NRP 3.2_Unknown exception occured


#1

I am following this tutorial: https://neurorobotics.net/Documentation/latest/nrp/quickStartGuide.html#qsg-fig11.
During

Step 7. Monitor neuronal activity during the simulation with the ‘Spiketrain Monitor’

I see the error:


#2

I rerun the whole tutorial until 7 and couldn’t reproduce your issue. Did you use the exact same code for transfer functions and brain model as in the tuto?
Check your sense() and act() TF code by comparing it to the screenshots in 6) and 7). Also, be sure to copy and paste the exact brain code from the light green code box in 4) in a blank brain editor.


#4

5.3 Perform some basic testing

c. See and verify that the “joints” variable holds an object of type “RosSubscribedTopic”.

Where and how can I verify it?

The iCub waves their hand. But still, Step 7 does not work.
I set the type of the device to “Spike Recorder”. But it does not show anything in the “Spiketrain” Monitor.
Then I reloaded the experiment by getting back to the landing page and then entering the experiment again.
It is probably a bug because it shows the type of the device: Alpha-shaped Leaky Integrator but I changed it to “Spike Recorder”.

I tried a few times to reload the simulation by getting back to the landing page and by creating monitor2 – it is the same issue: after reloading it shows the type of the device: Alpha-shaped Leaky Integrator.

How to proceed?

Thank you.


#5

To your question about 5.3:
c. See and verify that the “joints” variable holds an object of type “RosSubscribedTopic”.
-> when you print out joints in the clientLogger from the sense() function, you should see the type of the ROS topic in the Log console.

To your second question: I restarted my simulation and it didn’t change the type of the brain device in the monitor() function. I changed it to Alpha-shaped Leaky Integrator, ran it (of course the spike logger did not output anything), then restarted. It was still an set to Alpha. I changed back to SpikeRecorder and the spike logger worked again. So I can’t reproduce your issue unfortunately. It might be that you forgot clicking the green check next to the monitor function when you changed the device type.

image

When you click it, wait for 1-2 seconds and it should disappear, meaning the change was taken into account and be permanent, even after restarting.


#6

It worked.

I am wondering what “population_0” means. Here is what I did: