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 readily available visualization software to use for flow field visualization.  Most of the codes in Cart3D produce tecplot "*.dat" output files for quick visualization, in most cases these can also be read into Paraview or Fieldview as well. You should note that Cart3D's extended tri file format is actually a subset of the VTK unstructured format, and is written in XML. Tecplot, Paraview and Fieldview can read these files without translation. Thery're also readable by any other vtk-compatible viewer. Dont know if your *tri file is *.trix or not? Just type % file myfile.tri. If it tells you that the file is XML, its trix formatted.

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.
$__Post_Processing:        # <- 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.