Re: [deal.II] help with set_material_id and set_boundary_id

Hi You can set boundary id to unsigned int in type.h and dof_tools.inst.in. I personally recommend this setup if you read in a gmsh file. Then you can treat it as unsigned int. Otherwise, you need to cast boundary id safely to get correct value. Another reason to configure deal.ii this way is

[deal.II] Re: Possibility to output stuffs on the integration points?

Hi I dont know if I understand your request correctly, but I guess you want to output vertices(Nodes) and its associated solution/result right? If this is correct, then following might help you: make sure you are using shared or general triangulation without refinement by deal.ii if you are us

[deal.II] Re: website petsc tutorial

an-Paul > > On Tuesday, July 25, 2017 at 5:02:00 PM UTC+2, Yi-Chung Chen wrote: >> >> Hi Jean-Paul, >> >> Thank you for explaining it. I have the question because the page shows >> deal.ii is compatible with petsc 3.6.0. As I may recall, 8.4.1 is >> compa

[deal.II] Re: website petsc tutorial

release, we take a snapshot of the > information on the developer site and it becomes "frozen" for that release. > > Does that make sense? > > Kind regards, > Jean-Paul > > On Tuesday, July 25, 2017 at 3:43:16 PM UTC+2, Yi-Chung Chen wrote: >> >&

[deal.II] Re: Parallel GridIn of large file - PETSC Error

Hi Mathias Would you mind to check the memory usage? I guess you have about 3M DOFs right (based on the file size of msh)? My experience told me that 32GB can handle 10M DOFs(roughly). Your case is about 10GB memory based on the calculation.If you are using distributed mesh, which means you has

[deal.II] website petsc tutorial

Hi all, one link errors of the website regarding PETSC installation (I assume) if visiting http://www.dealii.org/8.5.0/readme.html and click More information on configuring and building PETSc can be found here .<= this link it will redirect

Re: [deal.II] Fully distributed triangulation (level 0)

Thank you, Timo. I'm going to refingure my deal.ii to this. Hopefully I can migrate all my design to this asap. I'm sure I can report you some performance analysis etc later on. Regards YC Chen On Thursday, February 9, 2017 at 9:33:05 PM UTC, Timo Heister wrote: > > see > https://urldefense.

Re: [deal.II] Fully distributed triangulation (level 0)

Hi Wolfgang, Thank you for reply. Unfortunately, google does not allow me to attach large meshes here (file is too big? > 300MB for a 3D mesh with dofs 2.5M in .msh). Is there any other way? I would like to share it with you. Here I attach the website of our project here, MTA

Re: [deal.II] internal compiler error: Bus error

Hi Lev, I was wondering if you ran out of disk. In my experience, it looks like your previous compilation is only partially successful. Best YC Chen On Thursday, February 2, 2017 at 4:31:12 PM UTC, Lev Karatun wrote: > > Hi Matthias, > > It doesn't seem to be reproducible. In fact, when I ran t

Re: [deal.II] Fully distributed triangulation (level 0)

Hi Timo, Thank you for your information. On Wednesday, February 1, 2017 at 6:38:23 PM UTC, Timo Heister wrote: > > > I believe that it would not be impossible to develop this, but it will > probably not be a small exercise. You would have to develop a fair share of > code, and gain an understa

Re: [deal.II] Fully distributed triangulation (level 0)

Hi Wolfgang, On Tuesday, January 31, 2017 at 10:57:35 PM UTC, Wolfgang Bangerth wrote: > > > Yi-Chung, > > > Thank you for your prompt reply. I was wondeirng if I can integrate > > other partition tools, such as metis or parmetis to handle the fully > > distributed triangulation. I can develo

Re: [deal.II] Fully distributed triangulation (level 0)

Hi Wolfgang, Thank you for your prompt reply. I was wondeirng if I can integrate other partition tools, such as metis or parmetis to handle the fully distributed triangulation. I can develop that part by myself (or with some help from the community). Do you have any suggestions? My following

[deal.II] Fully distributed triangulation (level 0)

Hi all, I have a project requiring to read in a large coarse mesh from gmsh to deal.ii > 1M dofs. Most of cells have their own characteristics, which means I cannot combine them and create a coarse mesh. Currently, I implemented it by using shared memory triangulation for parallelization. S

Re: [deal.II] Re: Interfacing dealii-8.4.1 with trilinos-12.6.2 - make test failed

I have similar experience. I solved it is by installing a local MPICH or OPENMPI (you can only have one), then export it to PATH. BR YC Chen On Thursday, November 10, 2016 at 12:35:24 AM UTC, Joaquin wrote: > > Sorry for the late answer. I had to re-install dealii + trilinos. > > jomivalen@Nalia

[deal.II] issues of static executable in 8.4.1 (and latest one on github)

Hi I try to compile static libraries by enabling static executable, but it failed. Can anyone help me about this? Here are some issues (and possible way to work around) 8.4.1 always get some error (looks like template instantiation problem) here are examples of errors -- /home/ycc/tool_d