The main reason I used that Blueprint page as a location to download the SLAM files was that it was relatively simple to work out how to download, compared to other locations for the files I had seen. I remembered that I had seen the author's more detailed page for the files during my researches though, and tracked down the link for that page again. I hope it will be of use to you.
Thank you for contacting us. We reviewed the links you provided and the Github link leads to securewiki.ith.intel.com. There’s the information needed to install the SLAM library. I tried to access the website outside the Intel network and was unable to access it, probably finding the same message you found. Please allow us to check why this is happening and if there’s an alternative to download the SLAM library.
Thank you for your patience. We’ve found an alternative site with instructions to download the Linux SDK modules: https://software.intel.com/sites/products/realsense/intro/getting_started.html . Try to install SLAM using this information and let us know if you’re successful.
In regards to the issue on securewiki.ith.intel.com site, we’ve notified the right team.
We’ll be waiting for your response.
thanks for checking this - now I understand that
has indeed valid content - just directory listing is not allowed.
Why directory listing -> my systems here are not running ubuntu
nor debian so i wanted to download the packages manually and
try to use them this way. In the meantime I got access to a debian
system so I can at least see that there are packages. As far as I
can see from apt those are compiled libraries and headers,
no source packages.
Play along with:
apt-get download --print-uris $(apt-cache search realsense | cut -d' ' -f1)
to see the package urls
only contains the compiled library.
I will proceed with downloading the packages and unpacking them
manually. Hopefully the binaries will work on my system
(Opensuse leap 42.1/ x86_64).
Is access to the source code of the SLAM library possible in
the future or will this be closed source only? As I want to deploy
the camera on system where changing the hole operating system
is not possible, this can be a requirement. Even
if it is complex to compile, it would still help. I understand this is
Thanks a lot.
unpacking the .deb packages worked! The slam is running.
Basically downloaded the packages and then ran
wget $(cat realsense_pkg_uris.txt )
ls *.deb | xargs -n1 unpack_deb.sh
where unpack_deb.sh is
ar -x $1
tar -axf data.tar.xz
I was now able to compile my own slam_tutorial_1_gui. Just the
window does not appear, but I'm foremost interested in the pose
I will test the stability and performance of the camera pose next week.
For this it would also be interesting if the slam can also provide
* velocity data for the translation direction
* estimated imu offsets
However the slam.h does not expose those features. I think they would
be very valuable for robotic applications.
But also given that success I think it would still be preferable to have the
source of the slam module, if that is possible.
It’s great to know you managed to get SLAM working. Feel free to share with the community your tests and findings!
The source code of the SLAM library is already open source, you can find it here: https://software.intel.com/sites/products/realsense/slam/index.html .
Let us know if there’s something else we can assist you with.
We’ve continued to investigate about this case. We want to clarify that the source code for the driver and framework are provided, but not middleware (SLAM, person tracking, object recognition) which is Intel intellectual property.
Hopefully this helps clear any confusion of what’s available.
thanks for explaining this. I think the misunderstanding started with the word
middleware. From your perspective, i guess these libraries stand between the
camera and the application software and are thus middleware. For me the
term middleware was either associated with interprocess communication,
or with software which basically just forwards data. Even wikipedia shows
that i was a bit misled.
Maybe it would be helpful to add an illustration to the documentation which
shows the different components in relation to each other. Also it should
be clearly stated that not all of the code is open source.
Again I want to add here: From my point of view the success of these sensors
in the robotic community could be improved by one of:
1. Releasing not just .deb packages for Ubuntu but rather self contained
archives if binaries
2. Releasing the binaries also for other platforms (e.g. ARM). But I completely
understand that Intel wants to push it's platforms here.
3. Releasing the code as open source, still. Why? This is novel hardware, and
customer will buy your sensor for the hardware, not for the software.
Thank you for the feedback. We’ve brought your latest reply to the attention of the team in charge. They’ll take your inputs as consideration to help us improve our services.