Any tips on how can this be solved? And where? Since LTL-SPORE is based on vanilla pattern matching experiment from spore-nest-module, would it be easier to adapt the optimizer? On the other hand optimizers should be decoupled from optimizees.
$ python3 -m scoop bin/ltl-pm-gd.py
[2017-06-01 13:05:02,949] launcher INFO SCOOP 0.7 1.1 on linux using Python 3.5.2 (default, Nov 17 2016, 17:05:23) [GCC 5.4.0 20160609], API: 1013
[2017-06-01 13:05:02,949] launcher INFO Deploying 4 worker(s) over 1 host(s).
[2017-06-01 13:05:02,949] launcher INFO Worker distribution:
[2017-06-01 13:05:02,950] launcher INFO 127.0.0.1: 3 + origin
All output can be found in file /home/dsalaj/Documents/CI_project/LTL-SPORE/results/LTL-PatternMatching-GD/run-no-test/results/output.log
Change the values in logging.yaml to control log level and destination
e.g. change the handler to console for the loggers you're interesting in to get output to stdout
MainProcess STDOUT INFO Established redirection of `stdout`.
MainProcess snn_utils.comm.zmq INFO Subscribing to tcp://127.0.0.1:8001
Traceback (most recent call last):
File "./zmq_proxy_node_py3.py", line 7, in <module>
ZMQProxyNode().main()
File "/home/dsalaj/Documents/CI_project/LTL-SPORE/spore/snn_utils/comm/music/node/__init__.py", line 75, in main
self._setup(self._music_setup)
File "/home/dsalaj/Documents/CI_project/LTL-SPORE/spore/zmq_proxy_node.py", line 57, in _setup
self._server = Publisher(music_zmq_proxy_config['communication']['port'])
File "/home/dsalaj/Documents/CI_project/LTL-SPORE/spore/snn_utils/comm/zmq/__init__.py", line 29, in __init__
self._sock.bind(address)
File "zmq/backend/cython/socket.pyx", line 495, in zmq.backend.cython.socket.Socket.bind (zmq/backend/cython/socket.c:5653)
File "zmq/backend/cython/checkrc.pxd", line 25, in zmq.backend.cython.checkrc._check_rc (zmq/backend/cython/socket.c:10014)
zmq.error.ZMQError: Address already in use
[ubuntu-x230:16282] *** An error occurred in MPI_Group_free
[ubuntu-x230:16282] *** on communicator MPI_COMM_WORLD
[ubuntu-x230:16282] *** MPI_ERR_GROUP: invalid group
[ubuntu-x230:16282] *** MPI_ERRORS_ARE_FATAL: your MPI job will now abort
Traceback (most recent call last):
File "./zmq_proxy_node_py3.py", line 7, in <module>
ZMQProxyNode().main()
File "/home/dsalaj/Documents/CI_project/LTL-SPORE/spore/snn_utils/comm/music/node/__init__.py", line 75, in main
self._setup(self._music_setup)
File "/home/dsalaj/Documents/CI_project/LTL-SPORE/spore/zmq_proxy_node.py", line 57, in _setup
self._server = Publisher(music_zmq_proxy_config['communication']['port'])
File "/home/dsalaj/Documents/CI_project/LTL-SPORE/spore/snn_utils/comm/zmq/__init__.py", line 29, in __init__
self._sock.bind(address)
File "zmq/backend/cython/socket.pyx", line 495, in zmq.backend.cython.socket.Socket.bind (zmq/backend/cython/socket.c:5653)
File "zmq/backend/cython/checkrc.pxd", line 25, in zmq.backend.cython.checkrc._check_rc (zmq/backend/cython/socket.c:10014)
zmq.error.ZMQError: Address already in use
Traceback (most recent call last):
File "./zmq_proxy_node_py3.py", line 7, in <module>
ZMQProxyNode().main()
File "/home/dsalaj/Documents/CI_project/LTL-SPORE/spore/snn_utils/comm/music/node/__init__.py", line 75, in main
self._setup(self._music_setup)
File "/home/dsalaj/Documents/CI_project/LTL-SPORE/spore/zmq_proxy_node.py", line 57, in _setup
self._server = Publisher(music_zmq_proxy_config['communication']['port'])
File "/home/dsalaj/Documents/CI_project/LTL-SPORE/spore/snn_utils/comm/zmq/__init__.py", line 29, in __init__
self._sock.bind(address)
File "zmq/backend/cython/socket.pyx", line 495, in zmq.backend.cython.socket.Socket.bind (zmq/backend/cython/socket.c:5653)
File "zmq/backend/cython/checkrc.pxd", line 25, in zmq.backend.cython.checkrc._check_rc (zmq/backend/cython/socket.c:10014)
zmq.error.ZMQError: Address already in use
--------------------------------------------------------------------------
mpirun has exited due to process rank 2 with PID 16282 on
node ubuntu-x230 exiting improperly. There are two reasons this could occur:
1. this process did not call "init" before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.
2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"
This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------
[ubuntu-x230:16291] *** An error occurred in MPI_Group_free
[ubuntu-x230:16291] *** on communicator MPI_COMM_WORLD
[ubuntu-x230:16291] *** MPI_ERR_GROUP: invalid group
[ubuntu-x230:16291] *** MPI_ERRORS_ARE_FATAL: your MPI job will now abort
[ubuntu-x230:16287] *** An error occurred in MPI_Group_free
[ubuntu-x230:16287] *** on communicator MPI_COMM_WORLD
[ubuntu-x230:16287] *** MPI_ERR_GROUP: invalid group
[ubuntu-x230:16287] *** MPI_ERRORS_ARE_FATAL: your MPI job will now abort
--------------------------------------------------------------------------
mpirun has exited due to process rank 2 with PID 16287 on
node ubuntu-x230 exiting improperly. There are two reasons this could occur:
1. this process did not call "init" before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.
2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"
This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun has exited due to process rank 2 with PID 16291 on
node ubuntu-x230 exiting improperly. There are two reasons this could occur:
1. this process did not call "init" before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.
2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"
This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------