Dear Roberto,

I think the problem is that you are using GridTools::transform (via 
GridTools::rotate), in a distributed triangulation. This should not be 
done, as noted 

If this is indeed the root of the issue, I see two options:

1. Rotate your problem, rather than your triangulation, 90 degrees. 
2. You can create a temporary local normal triangulation, rotate it, and 
finally copy into the distributed triangulation. That is, something in the 
lines of

>> Triangulation<2> tri_tmp;
> GridGenerator::hyper_cube_slit(tri_tmp, -1, 1, false);
> GridTools::rotate(-M_PI/2, tri_tmp);
>> triangultion.copy_triangulation(tri_tmp);
> triangulation.refine_global (6);
> Bests,
On Thursday, 12 April 2018 00:54:05 UTC+2, Roberto Porcù wrote:
> Dear all,
>   in the reply to my first post I forgot the code.
> I attach it to this reply.
> Best
> Roberto P.
> On Tuesday, February 20, 2018 at 7:27:37 PM UTC-5, Roberto Porcù wrote:
>> Dear all,
>> I'm solving a linear elasticity problem on a cracked domain created by 
>> means
>> of the  GridGenerator::hyper_cube_slit  function.
>> When I solve it in serial everything works fine.
>> When I solve it in parallel I get a problem on a node which is on one
>> of the slit boundaries as it is possible to see from the attached 
>> pictures.
>> I don't understand why that is happening because I wrote other parallel 
>> codes in deal.II
>> and everything was always working fine. I've checked my code many times, 
>> also comparing It to the tutorials.
>> I am supposing there is something related to the slit.
>> Thanks in advance,
>> Roberto

The deal.II project is located at
For mailing list/forum options, see
You received this message because you are subscribed to the Google Groups 
"deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to