deboliveira / mocaprasp Goto Github PK

There should be an empty directory named "data" in central - serverv2Test.py crashes if it does not find it.

Starting any kind of capture with the clients is very inconvenient. It requires VNC viewer open, and you have to manually hit the run.sh in each rasp.

It would be convenient if there was an automated process, controlled just by the server terminal that could start all processes. That would speed up testing and debugging.

I suggest creating a folder for homebrewed modules and separate "myLib.py" into smaller, themed modules.

There is a drop in the interpolated picture numbers when there are more than 6 markers on the scene.

For $2\leq N \leq 6$ markers in a 10 seconds capture, the number of interpolated pics is 995 constantly.

For 7 markers, this drops down to roughly ~570 interpolated pics.

For 8 markers, this drops even further to ~65 interpolated pics!

"capture.py" and "debugOnline.ipynb" are not supporting 1 marker captures.

When ran more than once data gets scrambled. If you want it to run again you need to re-run the notebook debugOnline.ipynb from the beginning.

It's crucial for debugging to it correctly resets after re-running it!

The serverv2Test.py and debugOnline.ipynb in central only allows 4 markers in the test capture - anything different than that will crash the program.

It's essencial for the test captures to allow any number of markers for further studies.

Plotly seems to be a fast, interactive and intuitive module for plotting. I personally find matplotlib's syntax not really intuitive and kinda hard to start getting on it.

I think a general rename would be more beneficial for a more intuitive labeling to directories and files - shorter and direct names would be appreciated.

This will require a throughout modification in the program files and documentation to make everything functional.

I suggest too deleting the "old" directory since it's not been used anymore.

Hello,

Thanks for your nice project, i looking for a replacement system about vives trackers (without tracker and hand controller to be more free on body movements on steamvr)

Do you have a video demo sample to see the accuracy details and rate capture ?

Other idea, later might use a server (connect to all RPI) version for PC with GPU (that manage all stream and optimise with IA process the capture to improove the system)

Best regards.

Describe the bug
Every time the calibCapture.py code is run, a long error pops up with the end of it saying "picamera.exc.PiCameraMMALError: Failed to enable connection: Out of resources". We tried many solutions and weren't able to fix the error. Not sure if its a software or hardware issue. Could indicate a problem with the system while trying to establish a connection.

To Reproduce

1. Go to MoCapRasp repository
2. Click on the calib file
3. Scroll down to calibCapture.py
4. Run the code
5. See error

Expected behavior
The expected behavior of the code is to initialize the Raspberry Pi camera, start the camera preview in a specified window, set up camera settings (shutter speed, exposure mode, color effects, etc), and continuously capture images every 5 seconds.

(this is the complete error that is shown)

mmal: mmal_vc_port_enable: failed to enable port vc.null_sink:in:0(OPQV): ENOSPC
mmal: mmal_port_enable: failed to enable connected port (vc.null_sink:in:0(OPQV))0x255aea0 (ENOSPC)
mmal: mmal_connection_enable: output port couldn't be enabled
Traceback (most recent call last):
File "/home/pi/MoCapRasp/calib/calibCapture.py", line 8, in
with picamera.PiCamera(resolution=(4608,2592), framerate=15,
File "/usr/lib/python3/dist-packages/picamera/camera.py", line 433, in init
self._init_preview()
File "/usr/lib/python3/dist-packages/picamera/camera.py", line 512, in _init_preview
self._preview = PiNullSink(
File "/usr/lib/python3/dist-packages/picamera/renderers.py", line 558, in init
self.renderer.inputs[0].connect(source).enable()
File "/usr/lib/python3/dist-packages/picamera/mmalobj.py", line 2210, in enable
mmal_check(
File "/usr/lib/python3/dist-packages/picamera/exc.py", line 184, in mmal_check
raise PiCameraMMALError(status, prefix)
picamera.exc.PiCameraMMALError: Failed to enable connection: Out of resources

The watch.py script in collect sends messages to the Server via a fixed IP adress (192.168.0.104) in lines 59, 87, and 91.

However, this adress can change when restarting the router or modifying settings on the local network!

Then i suggest changing the code so that it can locate the Server's IP via it's hostname, since it won't change frequently.

As it is right now, it's tiresome installing all the packages and modules necessary to setup python correctly to start using the code on new machines.

Maybe a preset Virtual Enviroment would be a good start to solve this!