On Mon, 3 Dec 2007, Benjamin Kirk wrote: > Specifically, the current mesh format provides no mechanism for > specifying the subdomain id, or the p level for a given element > (although the latter should probably be associated with an > EquationSystems object instead of the mesh).
I disagree - despite it's current status as "red headed stepchild that gets developed when Roy's attention wanders", in an ideal world p refinement would be seen as just another type of mesh refinement. Just because my code makes it possible to treat p refinement levels as separate from the Mesh doesn't make doing so a good idea in general. On the other hand, the proposal you've outlined for making these sorts of fields optionally separable from the mesh file sounds fantastic. Just make sure the default Mesh::write() behavior is to use "n/a" where possible and "." otherwise, so as to be the least surprising to the user. Writing separate auxilliary files should be a non-default option. Trying to imagine my own use, in fact, I'd probably only want to write integrated files, but then occasionally use meshtool (after it's been upgraded to understand them) to split out auxiliary files from what the application code wrote. --- Roy ------------------------------------------------------------------------- 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
