Re: [deal.II] Compilation error during the use of CellDataStorage datastructure

Hi Phani, Hmm… interesting. I think that you may be using the class in a way that we did not expect - I think that we intended it to store a struct/class rather than a primitive data type. I think that this should be an easy fix, namely that this assert (and perhaps others) need to be extended

Re: [deal.II] I installed deal.ii via spack and IDEs were unusable

Hi Drew, I also use Spack, and configure each project in the manner that Denis says - I use an external project with a Makefile, setup a build directory as a subdirectory of my project and run CMake once through the command line. After doing that I can happily build my project in eclipse. To sa

[deal.II] Compilation error during the use of CellDataStorage datastructure

Hi, I am trying to create a quadrature Point data in the form of CellDataStorage. My quadrature point data are of of type "double" and hence I do the following CellDataStorage::active_cell_iterator,double> rhoQuadData; typename DoFHandler<3>::active_cell_iterator cell_start = dofHandler.

Re: [deal.II] Test 4 failed, maybe different installation of MPI? then how to solve this?

Thanks for your reply. I did install mpich_3.2-7_amd64.deb before. When I tried your simple mpi example, I can not even compile it and the the error is: hello.c: In function ‘main’: hello.c:3:5: warning: implicit declaration of function ‘MPI_Init’ [-Wimplicit-function-declaration] MPI_Init

[deal.II] Re: I installed deal.ii via spack and IDEs were unusable

Hi, I use Eclipse only for writing the code and compile everything from the terminal, so I can't really comment. But I am quite certain that some of my colleagues setup Eclipse also to build/run their codes with deal.II being installed by Spack. Last time I was playing with building things fro

Re: [deal.II] refine_mesh get different number of active cells on different processes with parallel::shared::Triangulation

On 10/27/2017 02:13 PM, Yiyang Zhang wrote: Yes I think I am setting them in a way that is exactly same throughout all processes. Since I can check the n_active_cells() before the refinement, and also the refine_flags and coarsen_flags for each process. They are the same for each process. But

Re: [deal.II] Possible bug in the Jacobi preconditioner for MatrixFreeOperators::LaplaceOperator for vector fields

Dear Stephen, You are absolutely right, the value of dofs_per_cell is simply wrong in the vector-valued case. I have been hesitant to fix it because there are some downstream projects using it (mostly mine, though), but I guess it is better to switch to the correct notation now rather than cau

Re: [deal.II] refine_mesh get different number of active cells on different processes with parallel::shared::Triangulation

Hello Prof. Bangerth, Yes I think I am setting them in a way that is exactly same throughout all processes. Since I can check the n_active_cells() before the refinement, and also the refine_flags and coarsen_flags for each process. They are the same for each process. But after the refinement, t

Re: [deal.II] refine_mesh get different number of active cells on different processes with parallel::shared::Triangulation

Hello Prof. Bangerth, Yes I think I am setting them in a way that is exactly same throughout all processes. Since I can check the n_active_cells() before the refinement, and also the refine_flags and coarsen_flags for each process. They are the same for each process. But after the refinement, t

[deal.II] Possible bug in the Jacobi preconditioner for MatrixFreeOperators::LaplaceOperator for vector fields

Hello, I've been trying to refactor my code to use the new MatrixFreeOperators, but I've run into a problem trying to use the Jacobi preconditioner with the MatrixFreeOperators::LaplaceOperator with a vector-valued variable. In short, I wrote a short code to solve a simple 2D Poisson problem. F

Re: [deal.II] refine_mesh get different number of active cells on different processes with parallel::shared::Triangulation

On 10/27/2017 01:33 PM, Yiyang Zhang wrote: I am running with 2 MPI processes. It looks very weird that both processes have the same refine count and coarsen count, but end up with different number of active cells. Given a parallel::shared::Triangulation mesh, if the two processes have diff

[deal.II] refine_mesh get different number of active cells on different processes with parallel::shared::Triangulation

Hello, I am using parallel::shared::Triangulation, sometimes, but not always, I will get the following very strange behaviour when doing refine_mesh. This is the code. int refine_count = 0; int coarsen_count = 0; for(auto cell = this->tria.begin_active(); cell != this->tria.end(); ++cell){

Re: [deal.II] Test 4 failed, maybe different installation of MPI? then how to solve this?

Well, do you have more than one MPI library installed? If yes, you need to address that by removing one of them. You can check if a simple hello world MPI program compiles and runs correctly. See for example https://urldefense.proofpoint.com/v2/url?u=http-3A__mpitutorial.com_tutorials_mpi-2Dhello-

[deal.II] Test 4 failed after installation, no clue

Hi, Test 4 failed after make test. I make my research and find the following answer: https://groups.google.com/d/msg/dealii/mV-juFpnybA/DSBP4DArCQAJ And I get the following suggested commands with returns blow: ***

Re: [deal.II] deal.II on Mac OS Sierra

great to hear that this works. I am in the process to create a second installer for the newer xcode+sdk. On Fri, Oct 27, 2017 at 9:37 AM, Pawan Takhar wrote: > Alberto, > > Thanks for your reply. I installed 10.12 SDK as suggested in previous > discussion. I also set the project to use 10.12. Now

Re: [deal.II] CellDataStorage with mesh refinement

Hi Frederik, I’m being wildly presumptuous here (so feel free to say if I’ve presumed incorrectly), but unless you have a special set of data that needs to be considered then the ContinuousQuadratureDataTransfer

Re: [deal.II] deal.II on Mac OS Sierra

Alberto, Thanks for your reply. I installed 10.12 SDK as suggested in previous discussion. I also set the project to use 10.12. Now when I build from within Xcode, the project is compiling fine, but I get the following warning DEAL_II_DISABLE_EXTRA_DIAGNOSTICS "Unknown warning group '-Wunuse

Re: [deal.II] Non-homogeneus boundary conditions with-matrix-free not working

On 10/27/2017 06:44 AM, Bruno Turcksin wrote: Could you add this explanation to the documentation and/or to a tutorial. I think mentioning it step-37 would be great. Yes, I was actually thinking the same. Maybe in "Possibilities for extensions" in the results section of step-37, like we have

Re: [deal.II] Non-homogeneus boundary conditions with-matrix-free not working

Hi Bruno, I definitely agree - we should mention this in step-37. I will open an issue since I will not get to do it today. Best, Martin On 27.10.2017 14:44, Bruno Turcksin wrote: > Martin, > > Could you add this explanation to the documentation and/or to a > tutorial. I think mentioning it ste

Re: [deal.II] Non-homogeneus boundary conditions with-matrix-free not working

Martin, Could you add this explanation to the documentation and/or to a tutorial. I think mentioning it step-37 would be great. Best, Bruno On Friday, October 27, 2017 at 3:57:09 AM UTC-4, Martin Kronbichler wrote: > > Dear Michal, > > This is expected: the matrix-free operator evaluation cann

Re: [deal.II] Non-homogeneus boundary conditions with-matrix-free not working

Dear Michal, This is expected: the matrix-free operator evaluation cannot apply non-homogeneous boundary conditions while solving (at least I have never figured out how to do that). To solve such a problem, you need to bring the non-homogeneous part on the right hand side first. I often solve this