Closed erikx50 closed 3 years ago
Hi @erikx50, The problem comes from loading the Aruco markers with the kinect_v1. For the moment, Kinect V1 does not support the markers. Use Kinect V2 or use a dummy sensor to start a dummy Aruco class. I recommend you to see the tutorial 00_calib_arucos.ipynb for the Aruco use and skip until the section titled: Use ArUco dummy Class - For KinectV1 and DummySensor.
On the other hand, the script "sandbox_server.py", starts a sandbox server that is not entirely stable. We are working on this. For the moment, use the Jupyter notebooks and go through the tutorials. Finally, you may run all the modules using the notebook Run_Sandbox_allFunctionalitie.ipynb
I hope these general recommendations can get you started. Please let me know if this helps you.
Thank you for the quick answer @danielsk78. Fixed the aruco problem using a dummy sensor and managed to run the modules with Run_Sandbox_allFunctionalitie.ipynb.
I currently have a problem projecting the countour lines where the lines are not at the correct spot. When calibrating the sensor the margin patches only cover 1/4 of the sandbox. Also with the vertical calibration i cant seem to get the bottom of my sandbox colored red. The projector i am using also flickers alot when projecting the contour lines into the sandbox.
Lastly, should i start Jupyter notebook in the Anaconda enviroment?
Hi @erikx50 We do recommend using an Anaconda environment with only the sandbox dependencies to avoid interference. Is the most comfortable option. Other ways have not been tested.
When is this flickering happening? Which module is loaded?
Is the sensor field-of-view covering the sandbox and extra margins? With the calibration notebook, the idea is to crop the margins of the depth image, so the frame is only getting the information from the sandbox surface. If this is not the case, try setting the sensor farther from the sandbox, so the image covers a broader range.
Remember to run the projector calibration notebook first, since this file is needed to calibrate the sensor.
Hi @danielsk78! The flickering happens when the contour module is loaded.
I will try to troubleshoot a little bit on monday. Will update you then.
Hi @erikx50,
Is the flickering appearing when a warning rises: AttributeError: 'NoneType' object has no attribute 'dpi' ? (issue #3) Please check in the Jupyter Notebook or in the Command Line if this error appears every time the projector flickers.
Thats correct! Everytime it flickers that warning appears in the console.
Hi @erikx50,
When you load another module (e.g. GempyModule, or TopoModule) this warning should disappear. But, until now, there is no ultimate solution for this [BUG].
So you have two options:
self._target_time
to a higher waiting (Default is 0.01 ms). Be careful with this because it may take too much time to plot the contour lines when the value is too high. My recommendation is to increase the variable by 0.005 until the flickering stops.Example:
from sandbox.projector import Projector
from sandbox import _calibration_dir
_calibprojector = _calibration_dir + "my_projector_calibration.json"
projector = Projector(calibprojector=_calibprojector)
projector._target_time=0.015
...
Please let me know if this is useful. Or if you have some ideas that help solving this issue #3
Hi @danielsk78! Look like the flickering only happens when using the CmapModule.
I just received a kinect v2 and will try to set up the sandbox in windows.
No problems using kinect v2.
Hi! I am trying to run open_AR_Sandbox on ubuntu with Kinect v1. I have calibrated the projector and sensor but when I start the sandbox_server it only shows two white pages. This is the output the console shows while trying to run the server:
What should i try to do to get the program up and running?