Error while launching an experiment


#1

Hello,

I’ve finished my installation. When I open http://localhost:9000/#/esv-web and launch an experiment, the following error shows up:

ERROR TYPE

rospy.ServiceException

ERROR CODE

-1

MESSAGE

Error starting the simulation. (host: localhost)

DATA

service [/ros_cle_simulation/create_new_simulation] responded with an error: error processing request: No module named nest

STACK TRACE

Error
at new ClbError (http://localhost:9000/bower_components/angular-hbp-collaboratory/angular-hbp-collaboratory.js:2697:17)
at Object.error (http://localhost:9000/bower_components/angular-hbp-collaboratory/angular-hbp-collaboratory.js:2738:14)
at controller (http://localhost:9000/bower_components/angular-hbp-collaboratory/angular-hbp-collaboratory.js:4434:29)
at Object.invoke (http://localhost:9000/bower_components/angular/angular.js:4570:17)
at extend.instance (http://localhost:9000/bower_components/angular/angular.js:9445:34)
at resolveSuccess (http://localhost:9000/bower_components/angular-bootstrap/ui-bootstrap-tpls.js:4154:34)
at processQueue (http://localhost:9000/bower_components/angular/angular.js:15122:28)
at http://localhost:9000/bower_components/angular/angular.js:15138:27
at Scope.$eval (http://localhost:9000/bower_components/angular/angular.js:16384:28)
at Scope.$digest (http://localhost:9000/bower_components/angular/angular.js:16200:31)

Could you help me fix this? Thanks!


#2

Hi,

Your Nest build seems to have gone wrong (Step 7 in https://bitbucket.org/hbpneurorobotics/neurorobotics-platform)
Maybe you missed the make install command in that step?

You should have a nest directory in ~/.local/lib/python2.7/site-packages containing the required module files:

__init__.py
lib/
pynest-init.sli
pynestkernel.la*
pynestkernel.so*
raster_plot.py
tests/
topology/
visualization.py
voltage_trace.py

Also, check /home//.local/lib/python2.7/site-packages is in your PYTHONPATH:

echo $PYTHONPATH

This should be the case by default though.

Hope this helps,
Axel


#3

Hi Axel,

I reinstalled nest, and it works now. Thank you!

Shuo


#4

Hi Axel,

I got another problem when I launch an experiment:

ERROR TYPE

General error
ERROR CODE

-1
MESSAGE

Internal server error: No module named requests (host: localhost)
STACK TRACE

Error
at new ClbError (http://localhost:9000/bower_components/angular-hbp-collaboratory/angular-hbp-collaboratory.js:2697:17)
at Object.error (http://localhost:9000/bower_components/angular-hbp-collaboratory/angular-hbp-collaboratory.js:2738:14)
at controller (http://localhost:9000/bower_components/angular-hbp-collaboratory/angular-hbp-collaboratory.js:4434:29)
at Object.invoke (http://localhost:9000/bower_components/angular/angular.js:4570:17)
at extend.instance (http://localhost:9000/bower_components/angular/angular.js:9445:34)
at resolveSuccess (http://localhost:9000/bower_components/angular-bootstrap/ui-bootstrap-tpls.js:4154:34)
at processQueue (http://localhost:9000/bower_components/angular/angular.js:15122:28)
at http://localhost:9000/bower_components/angular/angular.js:15138:27
at Scope.$eval (http://localhost:9000/bower_components/angular/angular.js:16384:28)
at Scope.$digest (http://localhost:9000/bower_components/angular/angular.js:16200:31)

Could you please help me fix this? Thank you!


#5

Hi Shuo,

Can you try to do
cd $NRP/ExDFrontend
npm install

Regards,
Manos


#6

Hi Manos,

thanks for answering.

I tried what you wrote, and i got this:

exdfrontend@1.3.1 postinstall /home/shuo/Documents/NRP/ExDFrontend

rm -rf node_modules/grunt-contrib-uglify/node_modules/uglify-js/

exdfrontend@1.3.1 /home/shuo/Documents/NRP/ExDFrontend
└─┬ grunt-contrib-uglify@2.1.0
└── uglify-js@2.7.5

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
npm WARN exdfrontend@1.3.1 license should be a valid SPDX license expression

And I still can’t launch the experiment.

Regards,
Shuo


#7

Hi Shuo,

You seem to be missing the “requests” python package.

  1. check if there is a directory called “requests” in $HOME/.opt/platform_venv/lib/python2.7/site-packages
  2. if NOT, try to rebuild by running $HBP/user-scripts/update_nrp build (request is a requirement of ExDBackend and should be installed in .opt)
  3. if this requests directory is still not in $HOME/.opt/platform_venv/lib/python2.7/site-packages, then it might be that you have a system-level requests installed by pip, Try uninstalling it: sudo pip uninstall requests
  4. rebuild the NRP : $HBP/user-scripts/update_nrp build
  5. if finally the requests directory is in .opt, then reinstall your system requests to be safe: sudo pip install requests
  6. test your NRP platform again

Cheers,
Axel


#8

Just figured out python-requests is managed by apt…

Instead of pip uninstalling it, try rather to

sudo apt-get remove python-requests

and reinstall it later after succesfully fixing the NRP.

sudo apt-get install python-requests

To list dependencies you might have on requests:

apt-cache search python-requests