Source code for zdrive is in the driver and ch directories of the Zoltan distribution. The source code for zCPPdrive is also in driver, and uses some of the same C source files (in driver and ch) that zdrive uses. Source code for zfdrive is in the fdriver directory.
The C and C++ test drivers are built automatically in the Autotools build system. The F90 driver is built when the configure option "--enable-f90interface" is provided. The drivers are placed in BUILD_DIR/src/driver and BUILD_DIR/src/fdriver, for build directory BUILD_DIR.
The C and C++ test drivers are built in the CMake build system when option "-D Zoltan_ENABLE_Tests:BOOL=ON" is provided. The F90 driver is built when option "-D Zoltan_ENABLE_F90INTERFACE:BOOL=ON" is also provided. The drivers are placed in BUILD_DIR/packages/zoltan/src/driver and BUILD_DIR/packages/zoltan/src/fdriver; they are also copied to BUILD_DIR/packages/zoltan/test.
For an example of a simple input file, see the figure
below. In this problem, the method being used for dynamic load balancing
is RCB. Input data is read from Chaco
input files simple.graph and simple.coords. Zoltan's
is set to 3; default values of all other parameters are used.
(Note: zfdrive can read only a simplified version of the input file.
See the zfdrive notes in zdrive.inp for more details.)
Decomposition method = rcb
Zoltan Parameters = Debug_Level=3
File Type = Chaco
File Name = simple
Parallel Disk Info = number=0
The zdrive programs creates ascii files named "file_name.out.p.n", where file_name is the file name specified in zdrive.inp, p is the number of processors on which zdrive was run, and n=0,1,...,p-1 is the processor by which the file was created. (For zfdrive, the files are named "file_name.fout.p.n".) These files are in the same directory where the input graph file was located for that processor. Each file contains a list of global ids for the elements that are assigned to that processor after running Zoltan. The input decomposition can also be written in this format to files "file_name.in.p.n"; see "zdrive debug level" in zdrive.inp for more details.
Decompositions for 2D problems can be written to files that can be plotted by gnuplot. See "gnuplot output" in zdrive.inp for more information. Decompositions for 3D problems can be viewed after the test driver has finished by running the graphical tools vtk_view or vtk_write described next.