Question 1:
What does the following error mean?
ImportError: No module named DV_python
Answer 1:
This error means that Python cannot find the shared library DV_python.so. If VBM is installed in the directory /foo/VBM, this file can be found in a subdirectory of /foo/VBM/lib. The name of the subdirectory depends on the architecture and graphic library with which the shared library is compiled. For example, is the name of the architecture is "Linux" and you using the Mesa graphics library, then the path to DV_python.so is /foo/VBM/lib/Linux_Mesa/DV_python.so.
Now, finding this module is normally taken care of by the VBM.py script, so the user does not need to do anything. So, you should only get the error "ImportError: No module named DV_python" if VBM has not been compiled for your system. The one special case is that OpenGL is the default graphics library, and if you are using a different library you need to set the GRAPHIC_LIB environment variable. For example, if you try to run VBM in the above example (Linux architecture and Mesa graphics library), you will get the error "ImportError: No module named DV_python" unless you set the GRAPHIC_LIB environment variable to be "Mesa".
Question 2:
Why can't I run VBM on one machine and send the display to another?
Answer 2:
This is not a problem with VBM per se, but a subtlety of programs which use OpenGL. OpenGL programs CAN display remotely, but only to machines that are running an X server with the proper OpenGL extensions. I should even mention that not all X servers, even with the proper extension, are the same. There are certainly cases where an OpenGL program running machine 1 from vender A cannot display on machine 2 from vendor B, even though machine 2 can run OpenGL programs locally.
Question 3:
I have been using a Compute Engine which performs multidimensional continuation, but I am only getting lines in my Bifurcation Visualization module. What is the problem
Answer 3:
The VBM Core will not add connectivity to a VBM file which does not already have a "VBM_Connectivity" data block. Accordingly, if you are using a Compute Engine which returns connectivity you should ensure that the VBM file has a "VBM_Connectivity" data block in it before you start.