> Not quite. I'd rather fix this once and for all, not just fix it in > Gmsh now, then in XDR after that, then in Exodus after that, etc. We > ought to have something that gets called by MeshBase itself, probably > in prepare_for_use, to keep the id count consistent after a file is > loaded. >
That should work if you want to go over all elements again and then create a simple list of the subdomain id's to update the n_subdomains variable. If you just want to abstract this out, it looks like you would be wasting time doing an extra loop over the mesh when you can update this information as and when you read the mesh. Eventhough it sounds bad, it still might be the right way to go since the mesh reader already knows this information. Just my 2 cents. > If you want to take charge of MeshData, which currently doesn't have > any active developers, and which we go so far as to disable in > parallel in ex12, I'd appreciate it. But until MeshData is actively > maintained and up to date I'd rather avoid making anything else depend > on it. I remember from previous emails that no one uses mesh_data anymore. That's one of the reasons I moved away from the usage of this object. Unless more people are interested, I'll keep it this way since there is no point in just dragging around an object with limited support just so that one user benefits from it. I'll send you something regarding this tomorrow. We can go over the patch before you update it to the trunk. On Tue, Oct 27, 2009 at 7:31 PM, Roy Stogner <[email protected]> wrote: > > On Tue, 27 Oct 2009, Vijay S. Mahadevan wrote: > >> Roy, I do update the n_subdomains as part of my code. In fact after >> all elems has been updated with the right subdomain ids, I have a call >> that looks like >> >> unsigned int& nsubdms = mesh.set_n_subdomains() ; >> nsubdms = sbd_ids.size() ; >> >> in GmshIO. Is this what you were looking for ? > > Not quite. I'd rather fix this once and for all, not just fix it in > Gmsh now, then in XDR after that, then in Exodus after that, etc. We > ought to have something that gets called by MeshBase itself, probably > in prepare_for_use, to keep the id count consistent after a file is > loaded. > >> I optionally can add the information about subdomain_id and other >> attributes in .msh file to a mesh_data object. I have not used this >> feature in a while but never went back and removed this support >> either. Do you want this support in the patch too or do you still want >> to keep Gmsh to not use mesh_data as it originally was implemented. Do >> let me know about this before I create a patch tomorrow. > > If you want to take charge of MeshData, which currently doesn't have > any active developers, and which we go so far as to disable in > parallel in ex12, I'd appreciate it. But until MeshData is actively > maintained and up to date I'd rather avoid making anything else depend > on it. > --- > 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-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
