Hello everyone!
I am using a Raspberry Pi with an Intel Realsense to send images to 3D Slicer over a socket connection to create a point cloud out of them. Now sometimes it takes a very long time until the image is received in Slicer, it is irregular in between 2 seconds and 20 seconds.
The thing is that on the Pi’s case I mounted a tracking tool, that is additionally tracked by a NDI camera, because I want to have the real life position of the point cloud that is created afterwards. Now the problem is if I move the tracked camera in between transmission, the position of the camera is different than to the time I took the image. That is why I send beforehand just a single Triggerbyte to capture the transformation. But even just receiving the trigger byte takes sometimes up to 10 seconds.
I also tested the same receiving code outside of Slicer, just with a VSC code and the triggerbyte is received instantly.
Also I tried using “my own” socket connection, as well as a pyigtl implementation, there was no difference in transmission speed.
Another interesting thing I noticed was that I feel like if I click into the 3D Slicer scene the byte comes as I click. It feels like Slicer only updates when clicked into the scene (and also after an irregular amount of time)
Did anyone have a similar issue?
I am glad for every help received.
. So my first steps were obviously to connect it to the computer and test everything from there. With that setup everything worked smoothly and as you said withing a fraction of a second I get the data. But now I would like the setup to be wireless, so I build a device including a Raspberry Pi, which sends the depth image of the Realsense over a socket connection to Slicer every button press. And here comes the issue I described.