Ethan, Excellent.
I have the matlab programs in a subdirectory called matlab. Will there be several of these? So should we have a bin/python subdirectory for them? Barry On Jul 14, 2011, at 2:22 PM, Ethan Coon wrote: > Attached patch takes Lisandro's matio.py and puts it in a > PetscBinaryRead.py that reads a binary with (potentially) multiple Petsc > objects, deciphers the contents of the file from the header, and returns > numpy objects. It's basically the same as the PetscBinaryRead.m > > I've tested this on Vecs, but not Mats or ISs, and I haven't thoroughly > tested degenerate cases. Will do some testing, but I wanted Lisandro to > take a look at it as well... > > Thanks, > > Ethan > > On Wed, 2011-07-06 at 12:24 -0300, Lisandro Dalcin wrote: >> On 6 July 2011 11:41, Ethan Coon <ecoon at lanl.gov> wrote: >>> Both Paraview and Visit generally make ugly axes/colorbars/keys/etc. In my >>> opinion they both look fine for presentations and my own viewing, but are >>> not really acceptable for publication-quality. For things run on a >>> reasonably-sized problem, matplotlib (using either h5py to read hdf5, pyvtk >>> to read vtk, or petsc4py to read PETSc's binary format) makes publishable >>> plots. >>> >> >> Using petsc4py for reading PETSc binary formats is overkill. All this >> can be done with just NumPy. Should PETSc ship some Python code to >> read IS's, Vec's, Mat's in binary format? Can any of you suggest an >> appropriate location in the source tree? >> >> >> >> > > -- > ------------------------------------ > Ethan Coon > Post-Doctoral Researcher > Applied Mathematics - T-5 > Los Alamos National Laboratory > 505-665-8289 > > http://www.ldeo.columbia.edu/~ecoon/ > ------------------------------------ > <PetscBinaryRead.py>