These files contain meta information about the mesh and the command line flags used in creating the meshes which can be accessed by downstream programs. These files are ascii, so that you can look into them to jog your memory about how you ran cubes, but you shoud NOT edit any Mesh.c3d.Info file.

We needed to choose some easilly availible (and inexpensive!) visualization software to use for flow field visualization, and since it has the required set of capabilities, and is (relatively) inexpensive,  Most of the codes in Cart3D produce tecplottable output files for quick visualization. In the long run we have 2 plans for modifiying this approach. (1) we are working with MIT to produce a custom visualization system for Cart3D and (2) with increased support for the CGNS system in third-party visualization software it makes sence to output cutting-planes and annotated surface triangulation output files using the CGNS system.

The "-Xcut %d", "-Ycut %d" and "-Zcut %d" command line arguments are intended for quick on-the-fly plotting, but are not very pretty. They display views of the cell-by-cell reconstructed solution on a partition-by-partition basis.  This means that if you have 8 partitions, and ask for 3 cutting planes, you'll probably get 24 zones in your "cutPlanes.dat" file. In additon, there is no reason to expect contour lines to be continuous between a cell and its neighbor (since the reconstruction permits jumps between cells). To get pretty plots which display a node-based view of the discrete solution use the $__PostProcessing category ID with the Xslices, Yslices or Zslices tokens in your input control file. e.g.
$__PostProcessing:        # <- category ID
Xslices    0.001 1.2 2.0   # <- get X-slices at x = 0.001, 1.2 and 2.0.
Zslices    7.    9.2 20.0  # <- get Z-slices at z = 7, 9.2 and 20.

We had several requests to support Fieldview, so one of our users wrote tiger2fv and now we support it.