Dear Praveen

Thank you for your help. I assigned Physical Surface tags to all the
exterior surfaces, I leave without tag the interior adjacent surfaces
(the problematic ones). Then I assigned a Physical Volume tag to both
volumes (otherwise gmsh would only save the mesh generated in the
surfaces and deal.ii will complain). 

However the problem persist. Deal.ii still assigns boundary indicator 0
to the cell faces on these adjacent surfaces. I have exactly the double
of boundary faces with indicator 0 in relation to the number of faces in
each adjacent surface (both have the same number of faces and the nodes
are in the same position).

Maybe I shouldn't assign the Physical Volume tag? If so, is there any
additional step I'm missing? because I tried to do this and I received
an error:

The violated condition was: 
    cells.size() > 0
The name and call sequence of the exception was:
    ExcGmshNoCellInformation()
Additional Information: 
(none)



Best Regards
Javier

On Thu, 2012-05-24 at 07:47 +0530, Praveen C wrote:
> Hi
> 
> 
> You can set Physical Surface tag for only the outer boundary surfaces
> and then save the mesh. If Physical tag is not set then gmsh saves all
> surfaces.
> 
> 
> praveen
> 
> On Thu, May 24, 2012 at 4:31 AM, Javier Muñoz
> <[email protected]> wrote:
>         Dear Praveen
>         
>         Thanks for your answer. I tried to fix it in Gmsh, I save the
>         volumes as
>         a physical volume:
>         
>         e.g.
>         Physical Volume (1000) = {1,2};
>         
>         where 1 and 2 are the numbers that gmsh assigns to the
>         generated volumes
>         from the extrude command. Does this assign physical labels to
>         the
>         surfaces as well? If so, how do I avoid it? The mesh generated
>         only have
>         one label, 1000 in this case, that is the one assigned to the
>         physical
>         volume.
>         
>         
>         Regards
>         Javier 
>         
>         
>         On Wed, 2012-05-23 at 13:17 +0530, Praveen C wrote:
>         > You can probably fix this within gmsh. Gmsh will save all
>         faces for
>         > which "Physical Line/Surface/Volume" has been assigned. Just
>         dont
>         > assign a physical tag to the interior adjacent faces.
>         >
>         >
>         > praveen
>         >
>         > On Mon, May 21, 2012 at 7:33 PM, Javier Muñoz
>         > <[email protected]> wrote:
>         >         Dear all
>         >
>         >         I'm trying to import a mesh generated with Gmsh. It
>         is
>         >         composed by two
>         >         volumes with adjacent faces. Deal.ii imports the
>         mesh without
>         >         problem
>         >         but then I realize that it has assigned a boundary
>         indicator
>         >         of 0 to the
>         >         cell faces between the volumes. So, deal.ii is not
>         recognizing
>         >         them as
>         >         interior faces. I have search for a solution using
>         Gmsh, but
>         >         apparently
>         >         it is still an issue. In deal.ii I found this
>         command for
>         >         deleting
>         >         duplicated nodes
>         >
>         >         void GridTools::delete_duplicated_vertices
>         ( std::vector<
>         >         Point<
>         >         spacedim > > &  all_vertices,std::vector< CellData<
>         dim > > &
>         >         cells,SubCellData &subcelldata,std::vector< unsigned
>         int > &
>         >         considered_vertices, const double tol = 1e-12)
>         >
>         >         that I think could help me solve the problem (as I
>         have read
>         >         that
>         >         duplicated interfaces in Gmsh might be the cause).
>         >         Unfortunately I
>         >         haven't found any example of usage in the tutorials
>         or in the
>         >         mailing
>         >         list. It says that the function can be called by
>         some
>         >         GridIn::read_*
>         >         functions, how is it called? and the parameters, I'm
>         not sure
>         >         how to
>         >         define them, I found something similar in step 14:
>         >
>         >         std::vector<Point<3> > vertices
>         >         (triangulation_3d.get_vertices());
>         >         std::vector<CellData<3> > cells
>         (triangulation_3d.n_cells(),
>         >         CellData<3>());
>         >         std::vector< unsigned int > considered_vertices();
>         >
>         >         and then maybe I can pass them as:
>         >
>         >
>         
> GridTools::delete_duplicated_vertices(vertices,cells,SubCellData(),considered_vertices,1e-12);
>         >
>         >         As you can see, I'm a bit lost. Any help would be
>         highly
>         >         appreciated.
>         >
>         >
>         >         Regards
>         >         Javier
>         >
>         >         _______________________________________________
>         >         dealii mailing list
>         >         http://poisson.dealii.org/mailman/listinfo/dealii
>         >
>         >
>         
>         
>         
> 
> 


_______________________________________________
dealii mailing list http://poisson.dealii.org/mailman/listinfo/dealii

Reply via email to