Thanks, David!
I have loaded in my local Paraview (v. 5.7.0) and I don't get any issues.
You are using v. 5.9.0; so my best guess would be that Paraview has
permuted the support points between the releases, what would be really
annoying. Maybe you could
check
https://github.com/dealii/dealii/
Hi Peter,
>David, could you try out the following PR:
https://github.com/dealii/dealii/pull/11784
I tried it and the PR doesn't fix it for me.
> Not sure if the issue there is related. If not, could you post a vtk/vtu
file and I'll read it with my Paraview version.
Very good idea. I attached an
David, could you try out the following
PR: https://github.com/dealii/dealii/pull/11784
Not sure if the issue there is related. If not, could you post a vtk/vtu
file and I'll read it with my Paraview version.
Peter
On Tuesday, 23 February 2021 at 09:07:57 UTC+1 daschn...@googlemail.com
wrote:
On 2/18/21 6:39 AM, 'David' via deal.II User Group wrote:
the problem here is independent of any data set. So, you can also see it in
paraView in the 'solid color' block. It seems to be an artificial curvature
within the element.
To my best knowledge it is not required to update any geometry
Hi Daniel,
the problem here is independent of any data set. So, you can also see it in
paraView in the 'solid color' block. It seems to be an artificial curvature
within the element.
To my best knowledge it is not required to update any geometry related data.
What do you think?
Regards,
David
David,
For me the most likely suspect without looking into the code at all is a
missing update_ghost_values.
Best,
Daniel
Am Di., 9. Feb. 2021 um 17:04 Uhr schrieb Alexander :
> David
> i believe that in order to proceed, one will have to simplify this further.
>
> What is the minimum number of
David
what is the minimum number of procs this issue remains? Is it there for 2
procs?
Also, can you reduce the mesh to an absolute minimum, say 4-8 cells -- is
it still there?
Alexander
On Monday, February 8, 2021 at 10:20:35 AM UTC+1 daschn...@googlemail.com
wrote:
> Hi Wolfgang,
>
> > Dav
David
i believe that in order to proceed, one will have to simplify this further.
What is the minimum number of processes this happens? Can you reproduce it
for 2 procs?
Additionally, can the mesh size be reduced to a minimum (ideally a handful
of cells, say 4-8)?
Alexander
On Monday, Februa
On 2/7/21 2:12 AM, 'David' via deal.II User Group wrote:
,
I'm running a 3D case using the 'write-higher-order-cells' flag and the
'write-vtu-in-parallel' function. The output writing is quite similar to the
way step-67 handles it. However, the output of my 3D data sets looks a bit odd
when r
