[deal.II] Re: Getting error during cmake configuration step and later during make run

Hi Everyone, I started the upgrade to deal.ii 8.5 today because I wanted to use the new Physics libraries. However, the OSX binary does not run "out the box" as I do not have homebrew installed and instead use macports. Is there a .app bundle that is configured in a similar manner to the prev

[deal.II] Re: mesh generation in step-6 in parallel::distributed::Triangulation and Trilinos

Hi, On Wednesday, October 18, 2017 at 4:42:03 PM UTC-4, Yiyang Zhang wrote: > > i) the signal.post_refinement_connect() need to be set only when the grid > is generated initially, then throughout the problem (even if we have AMR in > the code), we don't need to set it again. Right? > No you stil

[deal.II] Re: mesh generation in step-6 in parallel::distributed::Triangulation and Trilinos

Hello Bruno, Thank you for your reply! i) I checked this page. I am a little confused. As soon as signal.post_refinement.connect() is called, I assume set_boundary_ids() is always attached to the Triangulation object, and it will always refresh the boundary IDs when a refinement is done. Right

[deal.II] deal.II Newsletter #8

Hello everyone! This is deal.II newsletter #8. 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: #5267: extend example of user projects testsuite to contain header files

Re: [deal.II] Re: mesh generation in step-6 in parallel::distributed::Triangulation and Trilinos

Yiang, 2017-10-19 13:53 GMT-04:00 Yiyang Zhang : > > i) I checked this page. I am a little confused. As soon as > signal.post_refinement.connect() is called, I assume set_boundary_ids() > is always attached to the Triangulation object, and it will always refresh > the boundary IDs when a refineme

Re: [deal.II] Re: mesh generation in step-6 in parallel::distributed::Triangulation and Trilinos

Hello Bruno, Thank you for your answer! Also thank you for the URL, those tests are really a good place to learn deal.II. Best, Yiyang On Thursday, October 19, 2017 at 1:46:55 PM UTC-5, Bruno Turcksin wrote: > > Yiang, > > 2017-10-19 13:53 GMT-04:00 Yiyang Zhang > > : > >> >> i) I checked this

[deal.II] Signal: Segmentation fault in parallel::distributed::Triangulation

Hello, I am having the following code to generate a mesh (code at the end). It crashes if I use more than 1 MPI processes (-np 1 works fine, but still have the WARNING message), with the following error message: -- WARNIN

[deal.II] Re: Signal: Segmentation fault in parallel::distributed::Triangulation

Yiyang, what do you see if you run this in a debugger on a interactive node, i.e. something like mpiexec -np 2 xterm -e gdb ./your_program ? Since this is a segmentation fault I would expect that you should be able to find the exact failing statement this way without too much problems. I have

[deal.II] Re: Calculating lift and drag

Hi Lucas > I am trying to replicate the results here > > > of the benchmark problem of flow around a cylinder (circle in 2D). Here is > my code so far: > It's been a long time since you posted this ques

[deal.II] Re: Signal: Segmentation fault in parallel::distributed::Triangulation

Hello Daniel, I am using the following code on my macbook. mpirun -n 1 xterm -e lldb ./test : -n 1 ./test This is the debug information I get from lldb. Is it useful? (lldb) run Process 99662 launched: './test' (x86_64) Process 99662 stopped * thread #1, queue = 'com.apple.main-thread', stop

[deal.II] Re: Signal: Segmentation fault in parallel::distributed::Triangulation

some more context 0x00010232685d │ movl %r13d, %esi││ │ │ 0x000102326860 │ andl $0x7fff, %esi ; imm││ │ │ 0x000102326866 │ movl (%rcx,%rsi,8), %esi││ │ │ 0x000102326869 │ movq

[deal.II] Re: Signal: Segmentation fault in parallel::distributed::Triangulation

This may be a useful information: the last line in the function: tria.global(refine); if I use tria.global(1); this function will complete successfully. However if I use tria.global(2); it will produce the error mentioned above. -- The deal.II project is located at http://www.dealii.org/ For

[deal.II] Re: Signal: Segmentation fault in parallel::distributed::Triangulation

I am not sure if this fully solves the problem, but if I do not use the Triangulation::maximum_smoothing flag, this part of the code will successfully proceed. (Previously I was using this flag for the Triangulation object.) -- The deal.II project is located at http://www.dealii.org/ For mail

Re: [deal.II] Petrov-Galerkin stabilization approach to solve Navier-Stoke equations

Hi Wolfgang > but if you treat the nonlinearity implicitly, and time discretized model > will remain > nonlinear and needs to be solved with a Newton scheme or similar. The > appropriate solver for that system then remains FGMRES. > Thank you for your hints on my previous question. Now I