> On the other hand, it would be better if we could make the default > behavior more user-friendly. Instead of testing for the presence of a > --read_legacy command line switch, why can't we test for the absense > of that new version line at the beginning of the file?
Probably do-able... > > Otherwise, very nice work. We don't support writing the Mesh in > parallel yet, right; just the EquationSystems? It seems like you've > been doing the harder of the two tasks first! Yup. I'm gonna start parallel Mesh IO on Monday. >> Now, currently the hilbert indices are temporarily stored in the >> DofObject::id() locations. This requires overwriting the valid numbering >> with an invalid numbering > > Based on the changes I had to make for ParallelMesh, I don't think > any numbering counts as "invalid" anymore unless it's actually > non-contiguous, and even that only breaks on some of our output code. This is non-contiguous, which only breaks when using e.g mesh.elem(e) instead of iterators -- which isn't too bad of a restriction. ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
