<div dir="ltr">Hi Utkarsh,<div><br></div><div>I finally had some time to look into this issue a bit further. I have a testcase for you of an Ahmed body that also shows the weird missing of the data.</div><div><br></div><div>The case with some intermediate result (approx 400 MB) can be found here:</div><div><a style="color:rgb(18,148,220);text-decoration-line:none" href="https://we.tl/ZZwy4ZGL1K">https://we.tl/ZZwy4ZGL1K</a><br></div><div><br></div><div>The case without that result (approx 125 MB) can be found here:</div><div><a style="color:rgb(18,148,220);text-decoration-line:none" href="https://we.tl/3dSqgyd4zG">https://we.tl/3dSqgyd4zG</a><br></div><div><br></div><div>Hope this helps in finding the issue. Please let me know if you need more information.</div><div><br></div><div>Best Regards,</div><div>Tom</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-16 13:25 GMT+01:00 Tom Fahner <span dir="ltr"><<a href="mailto:tom.fahner@gmail.com" target="_blank">tom.fahner@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>Let me check if that is possible, I do not think I can share this particular one. I will come back to you.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Tom</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2017-03-16 13:12 GMT+01:00 Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Tom,<br>
<br>
Do you have a dataset to reproduce this issue? There were changes in<br>
the reader in this past release, so it's conceivable that it<br>
introduced a bug.<br>
<br>
Utkarsh<br>
<div><div class="m_-2338284488487646490h5"><br>
On Thu, Mar 16, 2017 at 8:08 AM, Mark Olesen <<a href="mailto:Mark.Olesen@esi-group.com" target="_blank">Mark.Olesen@esi-group.com</a>> wrote:<br>
> Hi Tom,<br>
><br>
> So if foamToVTK works, it sounds like a reader bug. Maybe somewhere where the prism order is getting swapped - or something else where the reader's cell modeller is getting into trouble.<br>
> It may not work, but if you try to export from paraview to VTK format (ie, use the OpenFOAM reader for reading). Then with some effort it might be able to identify which cells are different. Presumably the cell ordering will be preserved in both cases, but still not 100% trivial. Either way, we need to figure out which cell types are causing the issue, or an off-by-one of whatever.<br>
><br>
> /mark<br>
> ______________________________<wbr>__________<br>
> From: Tom Fahner <<a href="mailto:tom.fahner@gmail.com" target="_blank">tom.fahner@gmail.com</a>><br>
> Sent: Thursday, March 16, 2017 12:47:05 PM<br>
> To: Mark Olesen<br>
> Cc: ParaView<br>
> Subject: Re: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues.<br>
><br>
> Hi Mark,<br>
><br>
> I have no polyhedral cells (hybrid tetrahedron/prism mesh), so I guess changing "decompose polyhedral on/off" does not make sense. In fact the smaller mesh that I tested with before did show the correct visualization and that mesh had polyhedral/hexagonal cells. It did not matter whether I used decompose polyhedral on/off. I also have experienced the slicing issues from time to time with various paraview versions with polyhedral meshes, but the effect was typically much less severe than in the current situation.<br>
><br>
> Using foamToVTK (with and without the -poly option) does indeed work and provides the correct visualization. So yes this can be a workaround for now, but I than rather go back to 5.1.2.<br>
><br>
> Regards,<br>
> Tom<br>
><br>
> 2017-03-16 11:44 GMT+01:00 Mark Olesen <<a href="mailto:Mark.Olesen@esi-group.com" target="_blank">Mark.Olesen@esi-group.com</a><mai<wbr>lto:<a href="mailto:Mark.Olesen@esi-group.com" target="_blank">Mark.Olesen@esi-group.com</a>><wbr>>:<br>
> Hi Tom,<br>
><br>
> Sorry, no answers - only questions/ideas:<br>
><br>
> Is decompose polyhedral on or off? How do things look using the other setting?<br>
> If the number of cells corresponds to checkMesh - then you either have no polyhedra, or decompose polyhedral is off.<br>
> If you use foamToVTK (with and without -poly) and then read the VTK file back in, how does that compare?<br>
> Using foamToEnsight could be yet another check, but without the option to decompose polyhedra.<br>
><br>
> In most paraview versions I've had issues with slicing through polyhedron (eg, from the motorBike tutorial).<br>
> The symptoms are either holes in the visual (like you have) or crashing the program. I haven't checked if this is better/worse in 5.3.0.<br>
><br>
> Cheers,<br>
> /mark<br>
> ______________________________<wbr>__________<br>
> From: ParaView <<a href="mailto:paraview-bounces@paraview.org" target="_blank">paraview-bounces@paraview.org</a><wbr><mailto:<a href="mailto:paraview-bounces@paraview.org" target="_blank">paraview-bounces@parav<wbr>iew.org</a>>> on behalf of Tom Fahner <<a href="mailto:tom.fahner@gmail.com" target="_blank">tom.fahner@gmail.com</a><mailto:<a href="mailto:tom.fahner@gmail.com" target="_blank">t<wbr>om.fahner@gmail.com</a>>><br>
> Sent: Thursday, March 16, 2017 9:39:49 AM<br>
> To: ParaView<br>
> Subject: [Paraview] Native OpenFOAM reader for ParaView 5.3.0 has some weird visualization issues.<br>
><br>
> Dear all,<br>
><br>
> Please find attached two images that show my OpenFOAM model in ParaView 5.3.0. It was the standard Binary Installers package downloaded from the website for 64 bit linux (OpenSUSE Leap 42.1).<br>
><br>
> The correct number of cells is reported in the information tab (when compared to OpenFOAM's checkMesh result). The patches are<br>
> all rendered nicely, but it looks like some cells are missing in the domain/volume.<br>
><br>
> Is there some setting that I need to apply?<br>
><br>
> Please note that the mesh has about 25.8 million cells, for smaller meshes this was not a problem. A colleague had similar issues.<br>
> ParaView version 5.1.2 did not have this problem, ParaView 5.2 was not able to open the OpenFOAM files at all.<br>
><br>
> Best regards,<br>
> Tom<br>
><br>
> --<br>
> T.C. Fahner<br>
> e: <a href="mailto:tom.fahner@gmail.com" target="_blank">tom.fahner@gmail.com</a><mailto:<a href="mailto:tom.fahner@gmail.com" target="_blank">to<wbr>m.fahner@gmail.com</a>><mailto:<a href="mailto:tom.fahner@gmail.com" target="_blank">tom<wbr>.fahner@gmail.com</a><mailto:<a href="mailto:tom.fahner@gmail.com" target="_blank">tom.f<wbr>ahner@gmail.com</a>>><br>
><br>
><br>
><br>
><br>
> --<br>
> T.C. Fahner<br>
> e: <a href="mailto:tom.fahner@gmail.com" target="_blank">tom.fahner@gmail.com</a><mailto:<a href="mailto:tom.fahner@gmail.com" target="_blank">to<wbr>m.fahner@gmail.com</a>><br>
> t: <a href="tel:%2B31-6-52642814" value="+31652642814" target="_blank">+31-6-52642814</a><br>
> a: Groene Woud 48<br>
> 4834 BC Delft<br>
> Netherlands<br>
</div></div>> ______________________________<wbr>_________________<br>
> Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensou<wbr>rce/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/ParaV<wbr>iew</a><br>
><br>
> Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>ParaView</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/paraview</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="m_-2338284488487646490gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>T.C. Fahner<br>e: <a href="mailto:tom.fahner@gmail.com" target="_blank">tom.fahner@gmail.com</a><br>t: <a href="tel:+31%206%2052642814" value="+31652642814" target="_blank">+31-6-52642814</a><br>a: Groene Woud 48<br> 4834 BC Delft<br> Netherlands</div></div></div>
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>T.C. Fahner<br>e: <a href="mailto:tom.fahner@gmail.com" target="_blank">tom.fahner@gmail.com</a><br>t: +31-6-52642814<br>a: Groene Woud 48<br> 4834 BC Delft<br> Netherlands</div></div></div>
</div>