bwrc / midas Goto Github PK

Try/except blocks should be made more specific in node.py. These are mostly related to unpacking requests

Currently you can make both info and status calls to a specific node. Because information conveyed by these calls are very similar they should be merged into a one single request.

If the LSL streams disappears during node runtime the request for new sample blocks indefinitely. This results in receiver process remaining in the background after shutdown.

Once generated with latest cloned midas repo, page loads forever:

Upon inspection of the console we find this error:

Apparently, a version mismatch caused some error in the webpage. Changing apidoc.json version field to 1.1.0 fixes the error.

Then re-generate the docs. Cheers 🍻

Currently invalid config-file entries are quietly ignored and replaced with default values making debugging harder. Better solution would be to throw a warning if invalid key values are found inside the file

I was doing setup for midas, but stuck with following error !!

msingh@svm-34:~/codes/midas$ python ./examples/midas_node_example_A.py config.ini node_A
Traceback (most recent call last):
File "./examples/midas_node_example_A.py", line 8, in
from midas.node import BaseNode
File "/usr/local/lib/python2.7/dist-packages/midas-0.1.1-py2.7.egg/midas/node.py", line 19, in
from . import utilities as mu
File "/usr/local/lib/python2.7/dist-packages/midas-0.1.1-py2.7.egg/midas/utilities.py", line 16, in
import configparser
ImportError: No module named configparser

msingh@svm-34:~/codes/midas$ python --version
Python 2.7.6

Looking forward - how to fix this !!

In some cases defining the dispatcher IP as 'localhost' in the configuration file causes the dispatcher to fail at startup. However, setting the IP to 127.0.0.1 seems to work.

In the ini-file: if node has publisher set to false but dispatcher has pubsub set to true dispatcher throws a zmq error at startup. Error below.

Exception in thread Thread-2083:
Traceback (most recent call last):
  File "/usr/lib/python3.4/threading.p^C
    socket_proxy_in.bind(publisher_url)
  File "zmq/backend/cython/socket.pyx", line 444, in zmq.backend.cython.socket.Socket.bind (zmq/backend/cython/socket.c:4089)
  File "zmq/backend/cython/checkrc.pxd", line 21, in zmq.backend.cython.checkrc._check_rc (zmq/backend/cython/socket.c:6248)
zmq.error.ZMQError: Invalid argument
Exception ignored in: <module 'threading' from '/usr/lib/python3.4/threading.py'>

Hi Midas Team

As per my observation, the step by step guide to run midas and do some test is missing in the documentation. I follows the example:

Start stream : midas_stream_example.py
Start Node A : midas_node_example_A.py config.ini node_A
Start Node B : midas_node_example_B.py config.ini node_B
Start Dispatcher : midas_dispatcher_example.py config.ini dispatcher

then what should be the next step ?

I created client as mention in wiki. I am getting following output :
$ python client.py
{'metric_a': 'unknown metric and/or channel', '3': 'unknown metric and/or channel', '1': 'unknown metric and/or channel', 'Ch1': 'unknown metric and/or channel'}

Kindly guide on how to proceed further.

Hi

I have few queries !!
As per LSL, they are organizing streaming data in specific file format.
Is Midas saving that streaming data in some file also ?
What is the location of file where data is saved Midas ?
If I started my stream 5 minute earlier than client, can we get all that data, as per my observation, it is streaming instant data stream only ?

Currently it is possible to start a node that contains no input arguments. Node responder will crash when the metric function is queried. Error should be thrown when the metric function gets added to the metric list.

When consulting the API documentation with intentions on getting the example running, one line says that one can request a metric as such:

However, the metric_a in the examples requires an extra argument which is: ,"channels":["Ch1"]. Only then it successfully returns the metric data. Cheers. ✌🏻

If a metric function has no docstring the node fails to launch. Should add checks for this.

Currently all node stream propreties (sampling rate, channel counts etc) must be declared in the configuration file. These parameters can easily be automatically read from StreamInfo. Stream discovery should be automated so that you only have to specify the stream name in configuration.