Running LidarView with ParaView CAVE Interaction plugin

LidarView, Lidar, and SLAM
1

Hello,

We are interested in lidar data visualization and LidarView appears to be a good option. We have been leveraging CAVE Interaction Plugin in ParaView and would like to also use CAVE Interaction plugin in LidarView for immersive visualization of lidar data. CAVE Interaction Plugin is enabled through -DENABLE_vrpn:BOOL=ON cmake option with ParaView Superbuild process. However, the same cmake option is not available when configuring LidarView superbuild. Is there a way that I can manually add CAVE Interaction Plugin to make the ParaView plugin available in LidarView?

We are planning to use CAVE Interaction Plugin in LidarView through python shell. Using same version pre-build ParaView binary plugin dll in pre-build LidarView binary python shell, I am not able to find the CAVE Interaction plugin using the following python command LoadDistributedPlugin(“CAVEInteraction”, remote=False) even when the CAVE Interaction ParaView binary plugin is copied to LidarView binary plugin directory. LidarView is also not finding the plugin when location of the prebuild binary CAVE Interaction Plugin file is specified.

Any help is greatly appreciated.

thanks
-simon

2

Hello @simonmssu,

The ParaView CAVE plugin was disabled lidarview-superbuild as it was causing an error during LidarView packaging. I tried to re-enabled it by default in this MR and it seems that the issue is gone!
For the vrpn option I added the project in this MR, so you should be able to use the -DENABLE_vrpn:BOOL=ON cmake option on the master branch.

Hope this helps, let me know if that solve your issue.
Timothée Couble

1 Like
3

Hello @Timothee_Couble ,

Thank you for your help. I was able to add -DENABLE_vrpn:BOOL=ON and -DENABLE_openxrsdk:BOOL=ON to LidarView superbuild on linux to get a version of LidarView with both CAVE Interaction and XR Interface plugin enabled.

Not on any critical path and just wanted to let you know, the binary type for vrpn library generated on windows does not match the expected type.

vrpn.lib(vrpn_Analog.C.obj) : error LNK2038: mismatch detected for ‘RuntimeLibrary’: value ‘MT_StaticRelease’ doesn’t match value ‘MD_DynamicRelease’ in mocs_compilation.cpp.obj

However, I am not seeing the error with my ParaView superbuild on windows.

thanks
-simon

4

However, another round of compilation with LidarView superbuild process, CAVE Interaction Plugin is enabled by default without vrpn.lib mismatch error mentioned above.