Thanks a lot everyone! I am happy and relieved that I can use Gmsh meshes
with libmesh.
Regards
Arvind
On Wed, Oct 28, 2009 at 10:08 PM, Vijay S. Mahadevan wrote:
> Arvind, If you are interested in storing the surface/volume ids for
> each element, you need to create additional data in Elem clas
On Wed, 28 Oct 2009, Vijay S. Mahadevan wrote:
> David, Yes that looks short and crisp. It should be enough to
> serialize the physical data to a .msh file. I initially thought that
> there was more to the n_subdomains functionality than just to let the
> user know the count, when you print the E
David, Yes that looks short and crisp. It should be enough to
serialize the physical data to a .msh file. I initially thought that
there was more to the n_subdomains functionality than just to let the
user know the count, when you print the EquationSystems. But
apparently not and so I don't think i
Vijay S. Mahadevan wrote:
Arvind, If you are interested in storing the surface/volume ids for
each element, you need to create additional data in Elem class. This
would be very similar to the subdomain_id() method. And you could also
set the partition while reading the mesh but I do not know how
Arvind, If you are interested in storing the surface/volume ids for
each element, you need to create additional data in Elem class. This
would be very similar to the subdomain_id() method. And you could also
set the partition while reading the mesh but I do not know how this
would affect the mesh t
@Dave : Thank you for your effort! I am happy to see that the subdomain_ids
are indeed
different for different physical regions.
Regards
Arvind
On Wed, Oct 28, 2009 at 6:35 PM, David Knezevic wrote:
>
> @Dave : I am using r3510. Could the problem arise from the fact that ex1.C
>> uses the fun
> @Dave : I am using r3510. Could the problem arise from the fact that
> ex1.C uses the function mesh.read( ) is there something special
> that needs to be done for Gmsh
> meshes?
I did a loop over the elements in the mesh you provided and the element
subdomain IDs are set correctly, so y
Thanks for the immediate replies.
@Vijay : I look forward to the functionality in your patch! My work involves
setting
bound charges between dielectrics. I was in fact thinking about how I could
handle these interfaces ... I guess having surface_ids in a 3D mesh will
allow me to solve the problem.
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 e
Dear Users and Developers
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
> I'm not sure if anyone else already responded to you, but no, I don't
> believe we currently write subdomain IDs to xda/r files. One could
> either append the subdomain ID to the end of each element connectivity
> list, or make a separate section of subdomain IDs somewhere after the
> boundary c
I'm not sure if anyone else already responded to you, but no, I don't
believe we currently write subdomain IDs to xda/r files. One could
either append the subdomain ID to the end of each element connectivity
list, or make a separate section of subdomain IDs somewhere after the
boundary conditions.
Dear libMesh team,
Another question: Does writing a mesh to an .xdr file (and re-reading
it of course) nowadays preserve the values of Elem::_sbd_id? It used
not to do this, but I would be very happy if it did.
Best Regards,
Tim
--
Dr. Tim KroegerPhon
13 matches
Mail list logo
