On 2/28/20 12:49 AM, 'Maxi Miller' via deal.II User Group wrote:
After additional tests I noticed that I'm not only overwriting the
target_component-component with the new values, but also the other
components, but with 0 instead. But instead I do not want to touch them.
How can I do that (if p
Here is a slight modification to example step-12 that fails. This is the
same sample (steady state) as step-12. The only difference is that I made
the system periodic in the x direction by adding these lines:
GridGenerator::hyper_cube(triangulation, 0.0, 1.0, true);
//
The commit that I am using is: 489c9d198d4ff0654f7d1f69f09404a2613b7954
I will work on a minimal example, but in the mean time here are the
functions I use to create the sparsity pattern and assemble the system. The
code works perfectly if either I turn off mesh refinement but keep periodic
BCs
Andrew,
Still hard to say what the problem is. Which commit are you using?
We have quite a number of tests that make sure that adaptive grid
refinement also works with periodic boundary conditions.
Can you provide a full minimal example that shows the problem you need your
workaround for?
How are
I just say a slight problem and changed this line the declaration of
periodicityVector to:
std::vector::cell_iterator>
> periodicityVector;
But I'm getting the same behavior.
On Friday, February 28, 2020 at 8:08:19 AM UTC-5, Andrew Davis wrote:
>
> Yes, here is the code I used to tell the tria
Yes, here is the code I used to tell the triangulation about the periodic
boundaries:
// create a mesh on [0,1] with colorized boundaries
GridGenerator::hyper_cube(triangulation, 0.0, 1.0, true);
// collect the periodic boundary pairs
std::vector::cell_iterator> >
periodicityVector;
