Usage information

General philosophy

The API is handles object instanced using the standard C++11 smart pointer std::shared_ptr.

All data are stored in instances of vtkfig::DataSet which in fact just wrap vtkDataSet instances describing a grid with all its attached scalar and vector functions.

Create such a DataSet:

auto data=vtkfig::DataSet::New();
data->SetRectilinearGrid(x,y);
data->SetPointScalar(v ,"v");

Similar to the VTK library, the ::New() methods are static class methods which return smart pointers to objects, effectively just wrapping std::make_shared

A data set can have multiple functions attached, which can be shown in different figures, which share one instance of grid information.

A particular visualization of data from a data set is done via a subclass of vtkfig::Figure. Create a Figure and add the scalar named "v" from the dataset:

auto contour=vtkfig::ScalarView::New();
contour->SetData(data,"v");

To be seen on the screen, put the figure into an instance of vtkfig::Frame:

auto frame=vtkfig::Frame::New();
frame->AddFigure(contour);
frame->Interact()

Each frame corresponts to a window on the screen. A vtkfig::Frame can have subframes (similar to subplots in matplotlib), allowing to have multiple figures in a frame. The implementation for multiple frames has performance issues. The Interact() method handles blocking interaction.

If instead of blocking interaction you want to render data evolving during time, you can do this in a loop:

while(...)
{
 ... calculate new values for v ...

  // update data in data set 
  data->SetPointScalar(v ,"v");

  // non-blocking
  frame->Show()
}

In the default mode, rendering in the frame is running in a separate thread, so the UI is responsive also during calculation.

Keyboard and mouse interaction

Currently, there is no proper GUI, and due to lack of resources, no plan to develop one. Nevertheless, the visualization can be influenced interactively. Besides of the standard mouse interaction from VTK, a number of keyboard commands is available, see vtkfig::Frame::KeyboardHelp.

Environment variables

The module can be influenced by a number of environment variables

Variable	Default	Semantics
VTKFIG_PORT_NUMBER	35000	Port number passed from vtkfig-exec to client
VTKFIG_WAIT_SECONDS	10	Waiting time before abandoning connection attempt
VTKFIG_DEBUG	0	Toggle debug output
VTKFIG_MULTITHREADED	1	Render from extra thread
VTKFIG_DOUBLEBUFFER	1	Use double buffering.

Server-client communication

This feature is still quite experimental.

The file src/vtkfig-exec.cxx builds to an experimental visualization client for server-client communication. Most examples are equipped with this feature. Here is how to use it (we assume working from the build directory, port is an optional port number, vtkfigpath is the path to the vtkfig source directory on the remote host ):

• Run example locally

$ examples/example-surf2d

• Run example in client server mode on localhost

$ src/vtkfig-exec -p port  localhost examples/example-surf2d

• Run example on remote host remote

$ src/vtkfig-exec -p port -ssh  remote vtkfigpath/build/examples/example-surf2d

• Run example on remote host remote with ssh tunnel via gateway gate

$ src/vtkfig-exec -p port -via gate -ssh  remote vtkfigpath/build/examples/example-surf2d