jhu-saw / sawNDITracker

cisst/SAW component for NDI trackers with Qt and ROS interfaces

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

No such package/stack 'ndi_tracker_ros'

ChenLong-Cristian opened this issue · comments

roscd ndi_tracker_ros:

No such package/stack 'ndi_tracker_ros'

Hi guys,
I am a bit new to Linux. Obviously you already managed to run this repo to some extent.

My question is that how should I run this repo?
I think I need to install this repo first in order to be able to use it?
So I did:
mkdir build
cd build
cmake ../
make
sudo make install
sudo ldconfig

So now how can I run this? I don't know what I should type in terminal.
I am trying to communicate with a NDI Aurora tool tracker.

Cheers,
Jacob

First, make sure the binaries have been properly compiled and installed. Do you see anything that looks like sawNDITracker in /usr/local/bin?

My guess is that the code is not properly compiled as you didn't mention compiling the cisst libraries.

If you happen to use Ubuntu and ROS you can find some instructions here: https://github.com/jhu-cisst/cisst/wiki/Compiling-cisst-and-SAW-with-CMake#13-building-using-catkin-build-tools-for-ros -- we use ROS for most applications so it's the most supported approach, this will cover the cisst libraries as well as the programs for the NDI trackers. If you don't know ROS, I'd recommend you take a look.

If you don't use ROS, you will need to first get and compile the cisst libraries: https://github.com/jhu-cisst/cisst Make sure you have Qt installed (see in ROS section which apt-get install are recommended). Then run CMake on cisst and make sure Qt is found. You will need the libraries cisstCommon, cisstVector, cisstOSAbstraction and cisstMultiTask turned on (it should be the default). Then do make, make install. At that point, check that the cisst libraries are showing up in /usr/local/lib. With cisst installed, re-run CMake for sawNDITracker, make and make install.

First, make sure the binaries have been properly compiled and installed. Do you see anything that looks like sawNDITracker in /usr/local/bin?

My guess is that the code is not properly compiled as you didn't mention compiling the cisst libraries.

If you happen to use Ubuntu and ROS you can find some instructions here: https://github.com/jhu-cisst/cisst/wiki/Compiling-cisst-and-SAW-with-CMake#13-building-using-catkin-build-tools-for-ros -- we use ROS for most applications so it's the most supported approach, this will cover the cisst libraries as well as the programs for the NDI trackers. If you don't know ROS, I'd recommend you take a look.

If you don't use ROS, you will need to first get and compile the cisst libraries: https://github.com/jhu-cisst/cisst Make sure you have Qt installed (see in ROS section which apt-get install are recommended). Then run CMake on cisst and make sure Qt is found. You will need the libraries cisstCommon, cisstVector, cisstOSAbstraction and cisstMultiTask turned on (it should be the default). Then do make, make install. At that point, check that the cisst libraries are showing up in /usr/local/lib. With cisst installed, re-run CMake for sawNDITracker, make and make install.

Thank you very much for the steps.
I don't use ROS. I just need to track a robotic arm which is moving and I am not controlling it.
My next quetion is that does sawNDITracker toolbox provide time stamp for every sample? The NDI tracker software which comes with the Aurora sensor, does not give me the time stamp for every sample.

Regarding time stamps, the existing code creates a time stamps based on the time the PC receives the data (not when the devices performs the actual tracking). The timestamp is then passed along in the ROS messages.

Regarding building the code, we strongly recommend to use ROS and the catkin build tools. To get the code, use the .rosintall file with wstool. The process is similar to the one described in: https://github.com/jhu-dvrk/sawIntuitiveResearchKit/wiki/CatkinBuild#catkin-build-and-rosinstall

Finally, this code doesn't work with Ethernet based NDI devices, namely the Polaris Vega. We don't have such device handy so we can't really support it.