Derek, I agree that there are better ways to implement this and I can definitely see that it should not be burdened in the library itself. I have very limited usage of AMR currently in my work and so in an effort to make my code verification easy, I decided to use the existing data structures to propagate the information that is needed for the physics objects. I'll probably change this in the future but it is a low priority for me now. The topic came up again since I do store the surface id's and related data for each elem as I read the mesh file and was not sure if anyone else would be interested in this.
Anyway, thanks for the suggestion ! On Wed, Oct 28, 2009 at 11:45 AM, Derek Gaston <[email protected]> wrote: > Just to clarify my statement on arbitrary data per element. If you > understand the implications and think it makes sense for your > particular application... it might not be bad (although I still think > there is probably a better way). But it's not something we should put > into the library itself. My experience with a certain other LARGE > framework that had this capability has lead me to the belief that > libMesh's _lack_ of this capability is actually one of it's most > powerful assets.... > > Derek > > > On Oct 27, 2009, at 5:26 PM, Roy Stogner wrote: > >> >> On Wed, 28 Oct 2009, Arvind Ajoy wrote: >> >>> I am trying to read in a simple mesh created using Gmsh, which has >>> two Physical regions. I use the example programme ex1.cc to read >>> the .msh file, and write it out as another .msh file, i.e ./ex1 -d 2 >>> in.msh out.msh. >>> >>> I find that the output of ex1.cc mentions n_subdomains()=1, though >>> there are two physical regions. >> >> Interesting... >> >> MeshBase::n_subdomains() has been around since 2005, when Ben added >> it (presumably to Mesh, back then?). >> MeshBase::set_n_subdomains() appears to be an easy accessor that Derek >> added earlier this year... but other than a little overloading in the >> BoundaryInfo::sync() method, I can't find anywhere that subdomain >> counts are actually getting *set* rather than just copied around! >> >> I suppose a typical use case is for the user code to set subdomain >> ids, but we do support them in Exodus, GMSH, Nemesis, and XDR I/O... >> yet none of that code seems to update the total mesh id count. >> >> Ben, Derek, anyone else know what I'm missing? It seems as if >> updating MeshBase::_n_sbd ought to be a standard part of >> prepare_for_use(), but isn't... >> --- >> Roy >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart >> your >> developing skills, take BlackBerry mobile applications to market and >> stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> Libmesh-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/libmesh-devel > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Libmesh-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
