This could be related to https://github.com/dealii/dealii/issues/14363. We
had a somewhat similar problem on our workstations in that deal.II ignored
the specified BOOST_DIR in the cmake call.
If you still have the build directory of the deal.II installation you could
check the summary.log whet
Hi everyone,
The last few weeks I've been working on improving my cmake skills.
One output of this is a cmake project that is able to build deal.II with
almost
all dependencies that can be found at:
https://github.com/jpthiele/dealii-cmake-superbuild
So far I could only test it on my workstation
If I remember my mechanics courses correctly they can be calculated in a
post-processing step after obtaining stresses and deformations
by solving the corresponding problem, right?
If so, there are multiple ways.
The maybe not so nice but quick way would be to just calculate the
quantities in V
Hello everybody,
Lately there have been a lot of github issues on Tpetra support and how it
can be achieved in an efficient way both in terms of coding hours and the
resulting implementation.
I feel that it could be beneficial to have some kind of roundtable
discussion(s) on how the interface sh
ldconfig told you that the deal.II 9.1.1 shared object library is in
/lib/x86_64-linux-gnu/
Additionally, there is an installation of deal.II 9.5.0-pre, which is the
current development branch of deal.II, in /usr/local
This second one actually fits to apt-get install libdeal.ii-dev, so I'm not
I have some experience with the direct solvers of Trilinos and it requires
very few modifications to change the assembly to a SparseMatrix instead of
a BlockSparseMatrix for vector valued problems.
Especially the assembly with distribute_local_to_global does not actually
care apart from the matr
Good to know it works now!
Out of curiosity:
Does the penalization in your jump terms include the edge size?
The formulation of SIP for Poisson that I know has a factor of $\eta/h_F$
with $\eta$ being the penalty parameter.
Consequently, smaller edges are penalized more which could be worth tryin
Hello Daniel,
for interpolate I know that it is between two different finite element
spaces on the same mesh,
e.g. from Q2 to Q1 elements, or in your case from Q1 to dG0.
What you will need to do is construct a Q1 DoFHandler on each mesh and use
`interpolate_to_different_mesh` to get a Q1 soluti
