> On Apr 25, 2014, at 4:54 PM, Derek Gaston <notifications@github.com> wrote:
> 
> In framework/src/base/MooseApp.C:
> 
> > +  // If we're writing an Exodus file, write the Mesh using its logical
> > +  // element dimension rather than the spatial dimension, unless it's
> > +  // a 1D Mesh.  One reason to prefer this approach is that sidesets
> > +  // are displayed incorrectly for 2D triangular elements in both
> > +  // Paraview and Cubit if num_dim==3 in the Exodus file. We do the
> > +  // same thing in MOOSE's Exodus Output object, so we are mimicking
> > +  // that behavior here.
> > +  if (mesh_file_name.find(".e") + 2 == mesh_file_name.size())
> > +  {
> > +    ExodusII_IO exio(mesh->getMesh());
> > +    if (mesh->getMesh().mesh_dimension() != 1)
> > +      exio.use_mesh_dimension_instead_of_spatial_dimension(true);
> > +
> > +    exio.write(mesh_file_name);
> > +  }
> > +  else
> When would we hit this? I believe that meshOnly always only writes Exodus. Is that true?
> 

I think we support e.g.

 --mesh-only foo.xda

To write out xda files, etc.