Boundary IDs in Salome?

227 views
Skip to first unread message

Andreas Krämer

unread,
Dec 17, 2014, 7:06:05 AM12/17/14
to dea...@googlegroups.com
Hi,

is there a way to set the boundary IDs in Salome and import them into Deal II?

Best
Andreas

Marc Secanell Gallart

unread,
Dec 19, 2014, 5:11:47 PM12/19/14
to dea...@googlegroups.com
Hi Andreas,

Yes, you can set both material IDs and boundary IDs in Salome and import them into deal.II. You set material ID and boundary ID in Salome by creating groups and then creating the mesh and exporting it to UNV. You can then read the UNV mesh. I would suggest you look at p 18 in the openFCST user guide application (www.openfcst.org) for an example.

I hope this helps,

Marc

--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en
---
You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dealii+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--

--------------------------------------------------------------------------------------------------------------------

Marc Secanell, Ph.D., P.Eng.

Associate Professor

Energy Systems Design Laboratory ( http://www.esdlab.mece.ualberta.ca/ )

Department of Mechanical Engineering

University of Alberta

4-31F Mechanical Engineering Building

Edmonton AB T6G 2G8 Canada

Phone: (780) 492 6961

E-mail: seca...@ualberta.ca

Confidentiality notice: Emails sent to seca...@ualberta.ca are forwarded to a Google-supported email account. Emails, attachments, documents and calendaring data, stored, received and sent through this University account may be transmitted to and stored on servers outside of the University, Alberta or Canada. The University of Alberta cannot and does not guarantee protection against the possible disclosure of your data including, without limitation, against possible secret disclosures of data to a foreign authority as a consequence of foreign laws.

--------------------------------------------------------------------------------------------------------------------

Andreas Krämer

unread,
Jan 27, 2015, 5:00:18 AM1/27/15
to dea...@googlegroups.com
Hi Marc,

thanks for your answer. The Salome tutorial in the openFCST user guide was really helpful.
However, after setting the boundary IDs, deal.II failed to import the boundary indicators.
Although I am pretty sure that there are no internal faces with IDs in the mesh, deal.II
throws the following error:

An error occurred in line <1835> of file </home/kraemer/NATriuM/deal.II/source/grid/tria.cc> in function
    static void dealii::internal::Triangulation::Implementation::create_triangulation(const std::vector<dealii::Point<dim, double> >&, const std::vector<dealii::CellData<2> >&, const dealii::SubCellData&, dealii::Triangulation<2, spacedim>&) [with int spacedim = 2]
The violated condition was: 
    ! (line->boundary_indicator() == numbers::internal_face_boundary_id)
The name and call sequence of the exception was:
    ExcInteriorLineCantBeBoundary()
Additional Information: 
(none)


The mesh I tried to import is attached to this post. Perhaps I should mention that 
I manually deleted two blocks of the unv file since they totally ruined the deal.II
import. (btw this was not mentioned by the openFCST user guide, but seems to
be a general problem). I'll also attach the original mesh (with the two blocks
that cannot be read in by deal.II (164 and 2420)).

Thank your for your support, so far.

Best Regards
Andreas
Mesh_1.unv
Original_Mesh_1.unv

Wolfgang Bangerth

unread,
Feb 21, 2015, 8:44:39 AM2/21/15
to dea...@googlegroups.com

Andreas,

> thanks for your answer. The Salome tutorial in the openFCST user guide was
> really helpful.
> However, after setting the boundary IDs, deal.II failed to import the boundary
> indicators.
> Although I am pretty sure that there are no internal faces with IDs in the
> mesh, deal.II
> throws the following error:
>
> An error occurred in line <1835> of file
> </home/kraemer/NATriuM/deal.II/source/grid/tria.cc> in function
> static void
> dealii::internal::Triangulation::Implementation::create_triangulation(const
> std::vector<dealii::Point<dim, double> >&, const
> std::vector<dealii::CellData<2> >&, const dealii::SubCellData&,
> dealii::Triangulation<2, spacedim>&) [with int spacedim = 2]
> The violated condition was:
> ! (line->boundary_indicator() == numbers::internal_face_boundary_id)
> The name and call sequence of the exception was:
> ExcInteriorLineCantBeBoundary()
> Additional Information:
> (none)

Someone asked essentially the same question again after you and my
understanding is that if you construct a geometry from individual parts, then
Salome puts an interface with a boundary indicator between the two parts. This
is what deal.II complains about: you have a face that sits between two cells,
but it does have a boundary indicator.

You need to delete these boundary indicators from the unv file. The other post
had a link to a script.

Best
W.

--
------------------------------------------------------------------------
Wolfgang Bangerth email: bang...@math.tamu.edu
www: http://www.math.tamu.edu/~bangerth/

Reply all
Reply to author
Forward
0 new messages