Re: [deal.II] Bugs by using candi

On 04/30/2018 02:04 PM, feap...@gmail.com wrote: -DCMAKE_C_COMPILER= -DCMAKE_CXX_COMPILER= -- The C compiler identification is unknown -- The CXX compiler identification is unknown CMake Error at CMakeLists.txt:2 (project): No CMAKE_C_COMPILER could be found. Tell CMake where to find the c

Re: [deal.II] Bugs by using candi

sorry, now I have attached the complete error infos: make[1]: Leaving directory '/home/yaakov/deal.ii-candi/tmp/build/parmetis-4.0.3/metis/build/Linux-x86_64' rm -rf build/Linux-x86_64 mkdir -p build/Linux-x86_64 cd build/Linux-x86_64 && cmake /home/yaakov/deal.ii-candi/tmp/build/parmetis-4.0.3

[deal.II] deal.II Newsletter #30

Hello everyone! This is deal.II newsletter #30. It automatically reports recently merged features and discussions about the deal.II finite element library. ## Below you find a list of recently proposed or merged features: #6405: Avoid accessing elements of a zero size vector in ParticleHandler

Re: [deal.II] confusing result when re-read a mesh in gmsh format

thanks! 在 2018年4月30日星期一 UTC+8下午10:56:45，Bruno Turcksin写道： > > > > On Monday, April 30, 2018 at 10:45:24 AM UTC-4, zeng wrote: >> >> Thank you so much for your reply. >> So in dealii we can't read a mesh with hanging nodes? Is there any other >> way to read an adaptively refined mesh? Since the r

Re: [deal.II] confusing result when re-read a mesh in gmsh format

On Monday, April 30, 2018 at 10:45:24 AM UTC-4, zeng wrote: > > Thank you so much for your reply. > So in dealii we can't read a mesh with hanging nodes? Is there any other > way to read an adaptively refined mesh? Since the refinement happend inside > dealii, I think it should have the abilit

Re: [deal.II] confusing result when re-read a mesh in gmsh format

Thank you so much for your reply. So in dealii we can't read a mesh with hanging nodes? Is there any other way to read an adaptively refined mesh? Since the refinement happend inside dealii, I think it should have the ability to output and recover the mesh correctly. 在 2018年4月30日星期一 UTC+8下午9:

Re: [deal.II] confusing result when re-read a mesh in gmsh format

The problem is that you cannot read a mesh with hanging nodes. If you have a mesh with hanging nodes, all faces with a hanging node are actually boundary faces, so in your picture, all faces that are between a refined and an unrefined cells, are actually boundary faces, i.e., they are topologica

[deal.II] confusing result when re-read a mesh in gmsh format

hi all, I tried to create a mesh as follws: 1. Generate the initial mesh using gmsh. Use 1, 2, 3 as boundary_indicator to denote three diffenrent boundary. Then I got the initial square.msh file. It looks like this:

[deal.II] confusing result when re-read a mesh in gmsh format

hi all, I tried to create a mesh as follws: 1. Generate the initial mesh using gmsh. Use 1, 2, 3 as boundary_indicator to denote three diffenrent boundary. Then I got the initial square.msh file. It looks like this:

[deal.II] Re: confusing result when read, refine, output, and re-read a mesh in gmsh format

I used the following code to test the resulting good mesh (the final picture above, which I used to think was good, but in fact not), the result is :"number of boundary_id = 0 faces: 24". So in the triangulation, there still exists 24 faces whose boundary_id is 0. I think when refine the triang

[deal.II] Re: confusing result when read, refine, output, and re-read a mesh in gmsh format

this phenomenon also happens if the line "if(cell->face(face)->boundary_id() == 0)" is replaced with "if(cell->at_boundary() == true)". -- 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 receiv

[deal.II] Re: confusing result when read, refine, output, and re-read a mesh in gmsh format

his phenomenon also happens if the line "if(cell->face(face)->boundary_id() == 0)" is replaced with "if(cell->at_boundary() == true)". -- 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

[deal.II] Re: confusing result when read, refine, output, and re-read a mesh in gmsh format

this phenomenon also happens if the line "if(cell->face(face)->boundary_id() == 3)" is replaced with "if(cell->at_boundary() == true)". -- 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 receiv

[deal.II] confusing result when read, refine, output, and re-read a mesh in gmsh format

hi all, I met a confusing problem when I try to create a mesh as follows: 1. I create a coarse mesh using gmsh. I used number 0, 1, 2 as boundary_indicators to denote three different boundary. The resulting square.msh looks good.

Re: [deal.II] Re: New step tutorial elastic wave equation with PMLs, complex-valued algebra

On Monday, April 30, 2018 at 7:13:26 AM UTC+2, Denis Davydov wrote: > > > > > On 30 Apr 2018, at 04:54, Wolfgang Bangerth > wrote: > > > > On 04/28/2018 10:36 PM, Denis Davydov wrote: > >> As far as as recall there just a few things left related to complex > numbers. > >> The biggest one is